For instance, that could be (and should be) NVIDIA's "Power management mode" set to "Adaptive" instead of "Maximum performance". Would love to have this specific issue detection backported to stable version of osu!, too.
Not everybody wants to kill their laptop's battery with osu!. I think this is out of scope.
And you can do this manually or automatically in windows
Adaptive mode is generally there for a reason and doesn’t affect performance beyond core (“turbo boost”) clock adjustment curves, right?
@HoLLy-HaCKeR we can just implement a caution rather than automatically set it.
It took me a while to know that my fps is locked down due to AMD power management plan also
A good start would be to identify if there is a reliable way to detect this via code. It will likely be per hardware api (NV/AMD/Intel) but hopefully also cross-platform.
I am against it because, as far as I understand, this feature is not cross platform. I think it will make framework code base more cumbersome.
See above comment. You can't be against it without first investigating.
Adaptive mode is generally there for a reason and doesn’t affect performance beyond core (“turbo boost”) clock adjustment curves, right?
At least for NVIDIA, there's actually three options, as far as I can remember: low power consumption, adaptive mode, and full performance. A friend of mine had a hard time starting and minimizing/restoring osu! running in fullscreen; took us both a while to find the cause.
What I'm suggesting is not to force the best performance but show a warning, like that for f.lux running simultaneously with osu!.
Closing as out of scope. We shouldn't be looking to change settings that a user has set (and lazer should be optimised to a point any of the power modes should be enough to run it).
Most helpful comment
At least for NVIDIA, there's actually three options, as far as I can remember: low power consumption, adaptive mode, and full performance. A friend of mine had a hard time starting and minimizing/restoring osu! running in fullscreen; took us both a while to find the cause.
What I'm suggesting is not to force the best performance but show a warning, like that for f.lux running simultaneously with osu!.