Bug #1832
Vsync inconsistently applied in different games
Description
Vsync seems inconsistently applied.
If one toggles Vsync in Ring Zero, that setting is carried over into all games that don't yet have a game config created. Otherwise Vsync is set per game and toggling Vsync in Ring Zero only affects Ring Zero.
Unloading a game and returning to Ring Zero, appears to apply the unloaded games Vsync setting to that Ring Zero session, regardless of what the users Ring Zero Vsync setting is.
Naturally, Snowberry by default bypasses Ring Zero, meaning I imagine most users exposure to the Vsync menu option will be in game. Thus why I believe there are so many users reporting the black screen bug in Dday, when Dday has to automatically toggle Vsync between games/Ring Zero; they are creating game configs before ever going to Ring Zero.
Associated revisions
History
#1
Updated by skyjake over 10 years ago
Updated by - Tags set to OpenGL
- Category set to Defect
- Assignee set to skyjake
- Target version set to 1.15
#2
Updated by skyjake about 10 years ago
- Status changed from New to In Progress
#3
Updated by skyjake about 10 years ago
I will remove any remaining game-specific vsync config and only use de::Config for this setting.
#4
Updated by skyjake about 10 years ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
#5
Updated by skyjake almost 10 years ago
- Subject changed from Vsync seems inconsistently applied to Vsync inconsistently applied in different games
Refactor|Client|libappfw|libgui: Replaced 'vid-fsaa' and 'vid-vsync' with Config variables
Console variables are game-specific, however the user most likely
prefers to use the same FSAA/vsync settings for all games as their
appropriate values depend on the available hardware.
Now the FSAA and vsync settings are configured persistently using
Config.window.main.fsaa and Config.window.main.vsync. The old cvars
were removed, however they can still be accessed via the console
command line using a mapping.
IssueID #1832