#LS reaches more FPS than the framerate cap

17 messages · Page 1 of 1 (latest)

terse siren
#

So here's some weird problem I currently face on Sword Art Online Alicization Lycoris. I tried capping the framerate both through RTSS and Nvidia App and in both cases while the capped ingame FPS shows 50 (trying to x2 FG while my screen is set to 100 Hz), when activating LSFG my base framerate heavily flactuates above the capped framerate (sometimes showing 50 but sometimes it flactuates between 52-57) though the generated framerate is 100 (so working as intended).

I'm using DXGI Api, have scaling mode set to Automated Full Screen, scaling type I've tried out none, FSR and LS1 and I've FG 2.1 set to Performance. I'm also playing with a DLDSR resolution of 2880x1620.
Any idea what the issue could be?

#

This also happens at 1440p btw

inland pawn
#

I had this issue, I solved it as there was some program interfering with the capture. In my case, it was FancyWM a tiling manager

#

Does it only affect SAO? Or other games as well. If it's not replicable then I'm not sure what could be the issue.

terse siren
#

So far only SAO. I have to try in other games too but for example Test Drive Unlimited Solar Crown had it working perfectly too with 48/144

inland pawn
#

Yeah I'd try other games too, because for mine, it was affecting all games until I killed FancyWM

terse siren
#

This behaviour does not occur in 1080p

#

Oh now it works in 1440p too

#

Okay so:
I tried launching the game in 1080p and did the same thing again (this time in 144 Hz) - first tried putting the game on monitor 2 and output to monitor 1 - worked with 50/100 FPS like it should
Then I moved the game to my first monitor and tried the same - worked again
Then I set my desktop res to 1440p and changed that ingame too @144 Hz - works
Then changed my Hz to 100 - works

So I don't really know why it works now and before it didn't

terse siren
#

Just tried Frame Gen now on High on Life in Xbox Game Pass and there it happens too
Monitor Hz set to 120, playing the game at capped 60 FPS via RTSS with x2 frame gen and while it mostly says 60/120, sometimes the base FPS go slightly up to 63-67 for some odd reason

terse siren
#

I tried disabling the Nvidia App overlay and that seemed to do the trick. I knew that overlays can mess up the experience of Lossless but that never has been an issue before

#

Now my Framerate stays at 60/120

terse siren
#

So yeah I can confirm:
Disabling Nvidia App and enabling Multi Monitor Mode fixed the flactuating framerate in my games
And also clicking on the Windows desktop icon in the bottom right corner and then clicking on the game icon in the taskbar fixes Lossless Scaling not detecting the game's FPS right. I know this may be different on other systems but for me that does the trick. Sucks a bit that this has to be done pretty much every time I tab out of games but at least it works

terse siren
#

Funnily enough what also works for me:
Just opening up the task manager while the game is open in the background and Lossless is enabled
Then Lossless will also detect the game's FPS instead of the desktop

terse siren
#

Just tried it on GTA V and I had more trouble on here for it to get it right. What helped this time:
Open game -> click on the desktop icon in the bottom right corner -> open game by using the task icon again -> then activate LS

On One Piece World Seeker I had LS enabled the whole time and it worked. For GTA V I had to enable it after the process for it to recognize it right

terse siren
#

I just played Need for Speed Unbound capped at 47 FPS using x3 Frame Gen and had the issue with flactuating FPS again (base FPS is 47 but the generated one mostly shows 141 but can change to 139-140 for a short while)
Even with Nvidia Overlay disabled and Multi-screen mode enabled in Lossless

terse siren
#

Sadly even by disabling the EA ingame overlay + RTSS overlay it still happens

It's different than with the other games though because there the main FPS constantly changed but now it mostly seems to be the generated one.
Maybe it's the game's fault. I'm not sure