Framerate limit not working when frame generation is active

[FakeMichau]

AntiLag 2 nicely reduces the input latency with FG but it seems like it ignores the maxFPS setting when used in that case. It could be an implementation issue on my end (even though the latency is getting reduced) so I would like to at least get a confirmation that this is an issue with the SDK.
I'm setting SetFrameGenFrameType and MarkEndOfFrameRendering.

[gareththomasamd]

It seems to work on my Cauldron sample. This will be released soon as part of a FidelityFX SDK update so maybe worth comparing against that.

[artur-graniszewski]

Unfortunately, just like FakeMichau mentioned, the FPS limit seems to not to work at all.

You can check this by using BETA5 of DLSS Enabler in any game that supports DLSS Frame Generation. As far as I understand, the FPS limit provided by AL2 starts to work as soon as the user disables Frame Generation feature in game settings.

[gareththomasamd]

Do you see the same behaviour in the new FSR 3.1.1 Cauldron sample?

[FakeMichau]

Do you see the same behaviour in the new FSR 3.1.1 Cauldron sample?

Yes.
The easiest method I found to reproduce it there is to:

1. Disable the FPS Limiter in the General tab
2. Set the fps limit in the AntiLag 2 tab to 50fps
3. Disable both imgui menus (by pressing F1 and F2)
4. Quickly moving the camera around.

The fps will jump from the set 50fps (100fps after frame generation) up to my monitor's refresh rate and stay there.
Might be worth mentioning that I can get that fps limit sometimes working in my use case as long as an imgui menu is visible.

[gareththomasamd]

thanks for reporting. We are working on a driver fix now.

[TheRazerMD]

thanks for reporting. We are working on a driver fix now.

Hey Gareth, any update on this? It's been a while since November, still doesn't seem to work.