Lossless Scaling Frame Gen sticking to monitor's refresh rate rather than the application

[ZedSui]

I cannot pinpoint what cauese it, but lossless scaling is reading my minor refresh rate rather than the application (144->248), I tried restarting the driver CTRL+SHIFT+WIN+B which doesn't work. I also tried to reinstall the GPU driver, it still doesn't work

[Gizzmoe]

Probably an overlay problem, try disabling all of them in Steam/Nvidia/AMD/Discord and any recording feature like Shadowplay/Instant Replay, disable Discord hardware acceleration

[Hillbrane]

Originally posted by ZedSui:

I cannot pinpoint what cauese it, but lossless scaling is reading my minor refresh rate rather than the application (144->248), I tried restarting the driver CTRL+SHIFT+WIN+B which doesn't work. I also tried to reinstall the GPU driver, it still doesn't work

Not an overlay problem, for everyone I know who's had or who's having this issue. They have NONE active.

In my case (I opened a thread here on the 7th of March), the problem went away TODAY.

A friend of mine re-installed or repaired his Windows 11 24H2. This deleted his external monitor's profile from Windows....and coincidentally this did it for him. So, we contacted another Win 11 24H2 pal of ours, he repaired his 24H2 install as well...and same thing, problem with LS solved.

So, I did a comprehensive, deep search [yeah, AI based] on the risks associated with 24H2 in March 2025. MS solved several issues lately. It re-offered to upgrade my 23H2 to 24H2. So, I took the plunge.

External Monitor flickered once. Then, Windows changed to monitor 1 (ie, internal).

I chose monitor 2 again, checked its profiles...only the default ones remained.

So, same Nvidia drivers, no overlays active but RTSS, as always. Launched LS FG 3, Fixed, x2.

Problem solved: base fps at 65 (as set in RTSS), generated fps at 132 or so).

Absolutely rocksolid performance, no hickups, framepacing is flawless as always.

So:

Gizzmoe suggested several times to upgrade to 24H2. which I refused given the never ending problems my friends had with it just a few weeks ago [and it didn't seem like the solution to this, given the fact that my team mates with 24H2 also started having problems on the 7th of March].

Gizzmoe's suggestion plus repairing/reinstalling 24H2 seems to be the way to go, which means this is a Windows issue.