flightlessmango
[Feature Request] add "base_fps_limit=" (so it can be used with LSFG)
"fps_limit=" limits the FPS to the multiplied FPS achieved through LSFG.
Unfortunately, this leads to heavy VRR flickering (in Helldivers 2 e.g.), if the base FPS is limited below the monitors minimum required FPS for VRR.
To avoid this, "base_fps_limit=" could be introduced as a solution.
what would
base_fps_limitdo exactly?
Basically what "fps_limit=" does without LSFG, limiting the real FPS. But with LSFG, "fps_limit=" only sets the maximum limit for the total FPS achieved by the fake frames of LSFG.
E.g., if I use LSFG with 2x multiplier and limit my FPS to 97 using MangoHud, then the real base FPS are limited to 48,5.
The idea is that with "base_fps_limit" the multiplied FPS are ignored and the limit is set only for the real FPS.
I tested this by using the in-game FPS limiter of Helldivers 2 & disabling MangoHud's "fps_limit=". It fixed my heavy VRR flickering because apparently VRR relies on real FPS and not on fake FPS to function properly?
This issue arises when mangohud is loaded before lsfg in the vulkan loader. Then mangohud is not aware of any extra frames being produced
This issue arises when mangohud is loaded before lsfg in the vulkan loader. Then mangohud is not aware of any extra frames being produced
I see. How can I change the load order? I changed the order of the commands in the Steam launch settings, but it didn't make a difference. Had still VRR flickering.
I don't know that you can reliably change the vulkan loader order
Didn't think of it before, but an easy workaround I could use is to multiply my normal FPS limit value with the same value I set the multiplier in LSFG at.
E.g. if I wanna limit my FPS at 97 and the multiplier in LSFG is set to 2, I can just 97 * 2 = 194 and use the command "fps_limit=194" to limit my FPS.
Now with DXVK removing the DXVK_FRAME_RATE env, MangoHUD becomes the only alternative and it still doesn't work well with LSFG-VK :/
