Just bought LS but it doesn't seem to work.

[devout roost]

So I installed it from Steam and trying to enable Frame Gen. in Farcry 6 doesn't seem to work. The program itself seems to work, at least it does show me its FPS counter in game but the frame rates are 115-120 and I want to have 141 through LS Frame Generation feature but it doesn't seem to work. In LS options under the "Preferred GPU" tab I only can select "auto" option, my GPU isn't showing, so I'm wondering if anyone has a similar issue like me and if there is some help available.

I already have a decent PC but would like to use Lossless Scaling to get those extra few frames to have a constant high FPS for games that don't natively support Nvidia's Frame Gen. tech. be those new or older games.

[serene spoke]

Can you share your windows version? If you dont know you can write winver in search bar. Also ls settings if possible (screenshot of all settings)

[devout roost]

MS Windows 11 V. 23H2

And in regards to settings I wasn't clear which you were referring to but I assume you mean Lossless Scaling's settings? Which I shall provide for shortly.

pt1.

pt2.

[serene spoke]

Do you have one monitor and one gpu? I dont see any problem in the settings btw. Can you tell me, exactly what lossless scaling indicator shows in game fps wise? Also i dont recommend using fsr as a default setting if you have kind of a decent pc. It is always best to use in game upscaling solution when possible.

[devout roost]

okay, understood about the upscaling seeing as I'd really love to use LS just for the frame gen feature but so

when I run it with steam overlay on for instance as an example it, LS fps counter shows me what steam fps counter is showing too, so it's for instance like:

115 on steam fps counter and in LS counter it goes like: 115 / 140

when I turn overlay off for instance LS still shows me 115 out of 140 where I would expect LS to go somewhere like sometimes to 140 /140

but it never does basically it just stays around 115 frames in LS weather I have Steam overlay on or off

and I don't notice a change like the framerate increases when I have LS turned on

where I would expect LS enabled to give me 140 / 140 constantly like on its LS fps counter and in the feeling I have in game, but my feeling stays the same with LS on or off because in essence it doesn't seem to turn frame gen on like I would expect it

feeling is noticeable because for instance running Cyberpunk2077 with upscaling and frame gen off, everything is slow and when I turn upscaling (DLSS) and frame gen on I get a constant 141 fps in my case in the game and the feeling is just very good and everything's smooth and reactive

[serene spoke]

Your monitor refresh rate 140? This is not how lossless scaling works. You need to cap your fps half of the refresh rate, you will want like 70 (fps cap) for 140 fps frame gen and it will show 70/140 (70 base fps, 140 frame gen fps). Lets assume you have 144 hz monitor. In this case maximum fps cap you will use with frame gen is 72 for x2 48 for x3 (they both get you 144 fps). If you globally cap your fps, it also caps lossless scaling so we dont want that (Probably you are capping your fps globally to 140)

Also disable all overlays like steam nvidia app etc.

Can you tell me your monitor refresh rate?

[devout roost]

right now it's set to 144 Hz

and I could try to cap the framerate to half my monitor's refresh rate through VSync maybe

[serene spoke]

Maximum?

[devout roost]

maximum is 180

[serene spoke]

why not 180 then?

[devout roost]

well just a preference because I was used to having 144 in relation to my old PC

or previous PC

[serene spoke]

I dont think it is preference though. You can just cap fps whatever you want

Assuming you have gsync

[devout roost]

yes I do

where would you suggest me cap the frames then?

in NVCP?

[serene spoke]

Nvcp or rtss

[devout roost]

also then not in global but for the game?

[serene spoke]

What settings you use in nvcp?

I recommend leaving settings on default ones if possible

[devout roost]

Um global I got frame rate cap manual at 141 fps and vsync is off

[serene spoke]

You will continue using 144 hz? I dont just get why though

[devout roost]

well

[serene spoke]

You know you can cap fps at any fps and not get any tearing

lower than refresh rate

[devout roost]

I can revert global settings to default in NVCP and I can change the monitor's refresh rate at 180 in windows

[serene spoke]

with 144 you just limit your options

i would love to get 180 hz monitor lol

[devout roost]

one day you might

😉

[serene spoke]

I can now but unnecessary for now that is why

[devout roost]

I see, that is viable a reason as any

but

personally I think 144 Hz is fine really

[serene spoke]

mine is kind of new

that is why actually

[devout roost]

but they are making like 500 Hz + monitors these days

sure

be happy with what you have 😛

[serene spoke]

With 180 fps difference will be huge for you

especially with ls

[devout roost]

I will try that

[serene spoke]

since

you can use 90x2 or 60x3

or 45x4 even

[devout roost]

what do you mean by that you mean resolution scaling

and then the frame gen option

x3 or x4

[serene spoke]

x values?

[devout roost]

yeah

[serene spoke]

framegen x

double triple quadruple

[devout roost]

yep

I see

I will tinker more with the settings then

[serene spoke]

and it will look great

any game just 180 fps you can play

that is amazing

and there is res scale option added

which reduces load even more

so it is even easier to achieve

If you want less input lag and gsync i recommend using 88x2 (instead of 90 like when you go for -3 fps than max refresh which is 141) and other frame x values according to that logic

for 180 hz

And allow tearing option in lossless scaling (means vsync off)

88 (base fps you cap at) x2 (frame gen value)

these are maximum you should use.

You can go for any value lower than this. Or 59x3 etc

[devout roost]

I found my issue, is because Windows 11's 24H2 update, I had to switch "Capture API" in LS to: "WGC" instead of its default "DXGI" because Windows update broke DXGI because of changes to the "MPO". Thank you for your support!