You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
displayScale config option resets to 150 when the game launches if it was previously set higher.
To Reproduce
Steps to reproduce the behavior:
Launch game from fresh install.
Navigate to Options > Video Options
Set Graphics Mode to Desktop Full.
The prompt "Increase Game Display Scale?" appears.
Select "Increase Display Scale" from within the prompt. Display scale is set to 200%.
Exit game.
Check config file in Configuration Directory. displayScale=150
Change displayScale back to 200 manually, save config file.
Launch Game.
The display scale has reverted to 150 and the game again displays the "Increase Display Scale" prompt.
Expected behavior
I assume the configuration that I select would not be changed automatically.
Screenshots or Videos
If applicable, add screenshots to help explain your problem.
Your System:
OS: Windows 10
Game version: 4.4.2 Built: 2023-11-29
Screen Resolution: 2560x1440
Additional context
I've tried a number of different settings for displayScale in increments of 50 (since that is what the UI lets you select). Any value above 150 gets reverted to 150 when the game launches. If I set it to 100 the value does not change.
It also seems that while I can select a displayScale higher than 150 from the game's UI and it will use that option. It never gets written to the config file. When the game exits 150 is written to the file and when the game launches it ignores any value that I manually save to the file and sets the scale to 150.
I noticed in the config file a setting called "autoAdjustDisplayScale". I tried setting it to false instead of true to see if that would fix the issue but it does not seem to have an effect. Setting it to false also doesn't seem to disable the "Increase Display Scale" prompt either so I guess I don't know what this setting actually does.
If I had to guess I think there's some weird edge case with the screen resolution where some logic thinks the scale should be 150 and is ignoring the value read from config.
I have attached a copy of my config file (extension changed to .txt in order to be able to attach). Let me know if there's any other information you need. config.txt
The text was updated successfully, but these errors were encountered:
Describe the bug
displayScale config option resets to 150 when the game launches if it was previously set higher.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I assume the configuration that I select would not be changed automatically.
Screenshots or Videos
If applicable, add screenshots to help explain your problem.
Your System:
Additional context
I've tried a number of different settings for displayScale in increments of 50 (since that is what the UI lets you select). Any value above 150 gets reverted to 150 when the game launches. If I set it to 100 the value does not change.
It also seems that while I can select a displayScale higher than 150 from the game's UI and it will use that option. It never gets written to the config file. When the game exits 150 is written to the file and when the game launches it ignores any value that I manually save to the file and sets the scale to 150.
I noticed in the config file a setting called "autoAdjustDisplayScale". I tried setting it to false instead of true to see if that would fix the issue but it does not seem to have an effect. Setting it to false also doesn't seem to disable the "Increase Display Scale" prompt either so I guess I don't know what this setting actually does.
If I had to guess I think there's some weird edge case with the screen resolution where some logic thinks the scale should be 150 and is ignoring the value read from config.
I have attached a copy of my config file (extension changed to .txt in order to be able to attach). Let me know if there's any other information you need.
config.txt
The text was updated successfully, but these errors were encountered: