how hard is it to just notify people of vsync. why do people keep making the mistake of deciding they're geniuses who can hide vsync from you
Conversation
do you want to know when the actual refresh rate on the panel changes or when the framerate that you should be targeting changes? if you're a 30Hz game and the panel is bouncing between 60 and 120 because of some other app, does that matter?
1
2
I think, in general, I would consider "what is the refresh rate" and "what is the target framerate to hit" two unrelated pieces of information which I would use for different purposes.
3
2
what are you even using the refresh rate for?
Super annoying case: what's the refresh rate to use when your window is half way dragged between a 120hz and a 50hz panel?
2
2
this is already handled for mixed dpi, the compositor decides which monitor the majority of your window is on and you swap to that display for vsync and dpi
1
2
That sounds awful. Why do we still have the mechanism of "wait for vsync" rather than submitting finished frames that will be displayed at the next refresh?
2
1
Because you want to minimize input to output latency otherwise your interface is unusual jank
1
1
No disagreement there but I don't see why my preferred way of doing it necessitates any latency. It's just having the display driver/controller do the flip for you rather than doing your own wait then hoping you have sufficient priority to blit in time.
1
