Conversation
peppy's current take is "whatever". let users do what they want because they know best (or don't, but that's not for us to make a call on because we are just out-of-touch devs). read into that however you want. we've also discussed elsewhere that the 2x 4x draw limit may not be the best defaults. if we're adding this, it may make sense to allow user customisation over those values rather than add a new "custom" value. but if we just want to get this is, adding "custom" is easiest to accept at face value. as you say it should probably not be a cycle option, or if it is, only show up when configured to anything non-zero. alternative angle: most games these days have a draggable "maximum fps" limit, which i'd actually be okay with as a game setting if the UX is correct. but that will take some non-rudimentary changes to make work. |
Sorry for the cluelessness, but either of these changes would need to happen in the main ppy/osu codebase, correct? |
|
Would likely require changes at both ends, and due consideration. Don't have the bandwidth for that this instant. |
|
I would suggest a "VRR Limiter" to the FPS dropdown using something like the Special K formula: Fps Cap = RefreshRate - (RefreshRate^2 / 4096) # the 4096 can be changed to have tighter timings a static −3 FPS offset works for 144hz but not necessarily for higher refresh rates. The scaling gives a proper frametime buffer to prevent G-Sync/FreeSync deactivation for higher refresh rate displays |
In case you want to limit fps to 2-3 frames below monitor refresh rate for vrr.