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
How to reproduce:
With Fullscreen/Fullscreen set, the lobby will open with the wrong size and position at next startup if you open the lobby and close Zero-K without loading into a mission.
Once you load into a mission with the borked graphics mode, the graphics will fix themselves to proper fullscreen after exiting from the mission and continue to work fine on the next startup after that.
So if you load into a mission every time Zero-K is launched, the bug does not appear to happen. But once you load the lobby and exit without getting into a game, the next time Zero-K is started, incorrect (or incomplete?) settings appear to be applied.
Tested on Steam Deck plus Windows+Nvidia
The text was updated successfully, but these errors were encountered:
Porkch0p
changed the title
Game Randomly Does Not Start in Fullscreen
Game launches in Windowed instead of Fullscreen mode
Feb 4, 2024
I was able to track this issue down to something adding Fullscreen = 0 to the springsettings.cfg at boot time.
An older fix for borderless windowed mode appears to be the culprit. I couldn't find documentation back that far for more details, but once removed, it fixed the fullscreen amnesia my lobby was experiencing and at least on modern systems, borderless still appears to work fine.
I've only tested this with a single monitor, so multi-monitor support may be worth testing, but the screen resolution setting seems much more reliable with this code path removed.
How to reproduce:
With Fullscreen/Fullscreen set, the lobby will open with the wrong size and position at next startup if you open the lobby and close Zero-K without loading into a mission.
Once you load into a mission with the borked graphics mode, the graphics will fix themselves to proper fullscreen after exiting from the mission and continue to work fine on the next startup after that.
So if you load into a mission every time Zero-K is launched, the bug does not appear to happen. But once you load the lobby and exit without getting into a game, the next time Zero-K is started, incorrect (or incomplete?) settings appear to be applied.
Tested on Steam Deck plus Windows+Nvidia
The text was updated successfully, but these errors were encountered: