Project

General

Profile

Bug #21431

[1.4.x -> 1.6.1] Game forces resolution reset on scene change

Added by Gameslinx about 5 years ago. Updated about 5 years ago.

Status:
Confirmed
Severity:
Low
Assignee:
-
Category:
Camera
Target version:
-
Start date:
03/02/2019
% Done:

10%

Version:
Platform:
Windows
Expansion:
Core Game
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

I use a 4k monitor and I lower the resolution to 2560 X 1440 to run the game faster. KSP does not maintain this resolution and regularly forces it back up to 4k during a scene change if playing at full screen.
This is a 100% reproducable bug. Run the game in full screen, lower resolution in graphics settings and do a few scene changes to flight and back.

This is an incredibly high priority bug for myself and others included because this bug has existed since 1.4.0 and for it to be unfixed for all this time is abysmal and downright disappointing, that's all I have to say.

No images or media attached because this has a 100% reproduce rate and it's difficult to capture the issue. Best experience it yourself, only takes a few minutes.

settings.cfg (31.3 KB) settings.cfg Gameslinx, 03/03/2019 08:17 AM
KSP.log (388 KB) KSP.log Gameslinx, 03/03/2019 08:17 AM
Verify Integrity.png (22.9 KB) Verify Integrity.png Anth12, 03/03/2019 11:15 PM
44137

History

#1 Updated by Anth12 about 5 years ago

Ive seen this reported before.

The one thing countering this being fixed is if its modded...

I have tried to reproduce this bug and cant and its not one that has just popped up for 4K monitors, others have done this with other resolutions as well.

Are you using mods?
can you supply a ksp.log for when it happens
can you supply a settings.cfg file.

I cant reproduce this.

#2 Updated by Gameslinx about 5 years ago

Anth12 wrote:

Ive seen this reported before.

The one thing countering this being fixed is if its modded...

I have tried to reproduce this bug and cant and its not one that has just popped up for 4K monitors, others have done this with other resolutions as well.

Are you using mods?
can you supply a ksp.log for when it happens
can you supply a settings.cfg file.

I cant reproduce this.

No mods are being used - this is the stock game. Log files have been attached below.

Note - Settings.cfg does not get changed when the resolution resets itself, it stays at the res i defined but the game reverts back to 4k.

#3 Updated by Anth12 about 5 years ago

44137

You log file indicates some issues.

The log file shows you are running 1.6.0 instead of 1.6.1
The log file shows issues relating to the steam aspect of the game.
The log file also seems to show issues with parts in the game

I recommend you do the following:
1. If you can first backup your saves to somewhere other than the KSP game folder,
2. delete the entire contents of the KSP folder
3. Then right click on Kerbal Space Program in the steam menu and get the window I have on the screenshot
and click on Verify Integrity of Game Files.
4. Dont do any of the above if you havent backed up the game

This will create a clean install of the game.

Then copy the back up and put it into the save folder.

Then try the game again.

Note I am not employed by squad, but this an interesting bug to figure out, because others have had it too, even without 4K monitors

#4 Updated by Anth12 about 5 years ago

Create...I mean Steam will download the entire game again

#5 Updated by Gameslinx about 5 years ago

Anth12 wrote:

Create...I mean Steam will download the entire game again

Yep. Redownloaded the game, changed resolution and it gets reverted back again. I'm not attaching a log. I've looked myself and there's no exceptions.
If Squad feels like they NEED a log for something as stupidly simple as this I honestly wonder why on earth they're even being paid to do this. This is just pathetic and should be fixed ASAP since this issue affects EVERYONE.

#6 Updated by Anth12 about 5 years ago

Heres what I have found out about this issue from other bug reports and others who I have seen play KSP:

1. Squad did try to reproduce this in a previous bug report even though the bug report in question had mods added to the game and couldn't reproduce it
2. The bug report was done by someone with mods which means the issue could have been caused by one
3. Not everyone gets the bug or a lot more people would be complaining about it
4. I have a feeling most people use the native resolution so this issue wouldn't occur for them
5. A bug that doesn't affect everyone is frustrating to find at times and takes a LOT of testing to figure out and for Squad time is money.

Thanks for redownloading KSP and getting back to me.

Let me see if I can figure this bug out.
Whatever the cause is feels like an easy fix to me.

I will need to move my computer out into the livingroom to test this on the 4K TV. I will report my findings in a few hours

#7 Updated by Anth12 about 5 years ago

  • Status changed from New to Confirmed
  • % Done changed from 0 to 10

OK....so lets see what I did to try to replicate the bug

1. I moved my computer to the livingroom and hooked it up to the 4K screen.
2. I tested for the bug using your settings.cfg file and I couldnt replicate the problem
3. I tried different things like launching a rover onto the runway. going to the tracking station and then back. Going from the rover (flight) to the Space Center. Tried launching a rocket into orbit and then going to the tracking station and back...etc etc etc. I couldnt get the bug you reported to work.
4. I went into the Nvidia control panel and changed the resolution and then went into KSP which resolution had been changed. Then I changed it back to 2560 X 1440 and then did more testing which didnt give any evidence of your bug
5. I looked at the ksp.log file to see what video driver version you were using. I uninstalled the video drivers I had and installed the version you had been using + Nvidia Experience which can change the settings of KSP...
6. At some point I realised I am playing KSP 1.6.1 and Making History 1.6.1...perhaps the bug isnt happening because it only happens without the expansion. So I removed the expansion
6. I found an old career save file that was compatible with 1.6.1 which didnt have any of the parts the expansion had and then went and took my mining ship from my ike station and landed it on Ike, then I went to the tracking station and back to the miner landed on Ike and nothing happened.
7. I refueled the mining ship on Ike and used time warp (of course) and then went back up to the ike station. Then I went to the map view....then I went to the tracking station where...Guess what...? The resolution changed to 3840 x 2160!!! BUG FOUND!. I then exited KSP and looked at the settings file and it said 2560 X 1440.
8. I restarted KSP and repeated the steps I had taken before and the problem didnt happen.....

So...technically I can confirm the bug, but a piece of advice. Dont insult Squad or get annoyed with people on the bug trackers when they are the ones who
want to help or can help. Insulting can have the opposite affect on people.

I have spent more than 4 hours on trying to confirm this bug. I spend hours on others at times and cant replicate them with enough information to even respond to their reports.

My pet project for over 2 months has been trying to figure out why the rover wheels have been getting damaged on decoupling, Its 100s of hours of testing and most of what I found out came down
to simple reasons in the end, so the report seems like I spent a few hours and found a problem when it took a long time...and right now more than anything I want to play Subnautica!! But I like figuring out bugs too.

I am not even paid...just a hobbie. but thats 4 hours I spent on this bug. Squad already have tried to find the cause and failed because they dont have enough information and they just dont have 4 hours to work on this.

So...Confirmed. However. Now I have to figure out what the EXACT trigger is. so...another 2 hours maybe.

#8 Updated by Anth12 about 5 years ago

The problem is too complicated to carry it on in this bug report. Making a new one and will give credit to this one.

Also available in: Atom PDF