#LSFG underperforming

74 messages · Page 1 of 1 (latest)

glossy wasp
#

I recently reinstalled Windows and a new issue has appeared with LSFG. I always use it on older Call of Duty titles like Black Ops / MW3 etc because they tend to have issues above 200fps. So I just lock them with RTSS to 180, and 2x FG for 360hz. But since reinstalling windows, LSFG struggles to keep up with 180hz capture even if there are more than enough resources. This wasn't a problem before so I'm not sure why it broke. Losing a handful of frames isn't a huge deal but the issue manifests as inconsistent frame pacing which makes LSFG unusable.

#

I have a 5080 and 9800x3D, you can see in this screenshot that neither are remotely overworked in this scenario. Capturing games at 200+ fps was previously never an issue. If I up the game's FPS cap to 200, it captures roughly 195-ish fps so something odd is going on.

#

I used to have the GPU in LS directly set to the 5080 instead of Auto, but that option is no longer available for some reason. I disabled the iGPU on my CPU in the BIOS and Task Manager reveals it's not active so idk why the option is gone. Maybe that is related.

shell falcon
#

Your game overlay is breaking the detection of when frames are happening, turn it off and it will be fixed. I monitor stats with HWinfo on second screen.

#

the GPU selection doesn't have options because you only have 1 gpu turned on, so it's just working on that gpu (the 5080)

glossy wasp
#

Do I just need to toggle it off with the hotkey, or do I need to disable detection for games I use LSFG with?

vital ravine
#

Also, just to be sure, uninstall LS and delete the folder in - win+r > %localappdata%

#

And install from steam

glossy wasp
vital ravine
glossy wasp
#

Would be nice if the profiles were a seprate file or something then. I have a ton of profiles :(

#

Could RTSS be related?

vital ravine
vital ravine
glossy wasp
#

Do I need to completely disable detection in RTSS, or just turn off "On-Screen Display support" for the game?

#

Low to detect the game, OSD support on, is what I always use in pretty much every single game I play. I like watching my usage and temperatures.

vital ravine
#

Without closing the game

glossy wasp
#

Just removing the folder and deleting the settings.xml seems to have improved stability a lot

#

My favorite use case for LS is when a game is able to hit 120+ fps and I can just multiply it to match my 360hz monitor. This is especially useful in older Call of Duty zombies which break above 200fps. Usually that means the GPU is not even remotely overwhelmed

#

I don't use HDR or VRR and I'm on the latest version of Windows 11. Should I be using WGC or DXGI?

vital ravine
#

WGC

glossy wasp
#

It seems to waver more as I shake the mouse around. I don't think that was a problem before.

glossy wasp
vital ravine
vital ravine
glossy wasp
#

If anything enabling VRR support makes it a little worse

vital ravine
#

Same with DXGI right?

glossy wasp
#

Yar

vital ravine
#

Can you try it with other programs/games?

#

To check the LS capture and output, odd behaviour

glossy wasp
#

Just locking MW3 to 120fps and multiplying by 3 actually does improve the consistency. But the latency increase is not very nice for an fps game

glossy wasp
#

Not rock solid, but definitely more stable than 180.

vital ravine
#

Then the issue is still there

#

Check with x2 FG 120 capped base

#

Or... Just for testing cap to 60 and x2fg

glossy wasp
#

120 / 240 is rock solid

vital ravine
#

Ohh

glossy wasp
#

Oh?

vital ravine
#

I didn't expect that

#

Increase the cap by 10 incrementally

#

To see at which point it starts not being rock solid

glossy wasp
#

I guess Rock Solid is SLIGHTLY overselling it. It sometimes briefly hits 120 / 239, but I am not noticing any visible frame pacing problems. With the RTSS frametime graph enabled, I can see the game is not stuttering so that wouldn't be the cause

vital ravine
#

239-240 is fine due to decimal value variations in frames timestamps

#

But it shouldn't vary any more than that

glossy wasp
#

Importantly flicking the mouse around like crazy doesn't seem to affect the stability at all. Unlike 180 x2

vital ravine
vital ravine
glossy wasp
#

150fps is becoming less stable a tiny bit

#

Dropping the render res massively, I can attempt 200 / 400 without any GPU usage worries, but it can't capture 200. it's always 198 / 396 or less... Until I tabbed out.

#

For some reason lots of movement makes it much less stable. I don't know why

vital ravine
#

Okay, can you try this, (not sure how much it'll help, still worth a try)...
Restart the PC, open only RTSS for capping fps (no overlay) and then use LS to scale. Try to close everything that you can, just in case.

#

I am out of factual ideas for the reason behind this odd behaviour

#

That's why I suggested this

glossy wasp
#

Just trying 180 / 360 with the render res very low to give it more GPU room, I can feel the mouse sorta jumping as I sweep side to side. Whatever is happening is definitely causing frametime issues.

vital ravine
#

Yes, it is not GPU usage

#

You were only at 50s in that initial SS

#

A LOT of headroom

glossy wasp
#

My GPU drivers are not the VERY latest, a new one came out like yesterday. I can update real quick? Unless that causes more problems cuz I know sometimes Nvidia has problems with regression. Especially for the 50 series for some reason...

vital ravine
glossy wasp
#

Also, I am ALWAYS capturing in OBS. I use the Replay Buffer feature for high quality clips with separate audio tracks so I can make videos.

#

Again, wasn't a problem before lol.

glossy wasp
vital ravine
vital ravine
glossy wasp
#

Installing drivers, disabled OSD, will restart in a hot sec.

#

Idk why the 50's have had so many issues with performance regression, encoding problems, and some specific monitors not working. Every driver update for like a year after release was a dice roll if it would break something lol.

vital ravine
#

I'm going to bed for now. Hope your issue gets fixed when I come back 🫠

glossy wasp
#

Alright lol. Thanks for your help so far!