(BUG) (NOT SOLVED) WGC's fg works, but vsync doesn't work correctly in some of its options. | Lossless Scaling | Page 1

warm python Apr 14, 2024, 5:46 PM

#

altho if the game can't get 120 native , you can't achieve 240

#

just stay at 60 and FG to 120

#

it will also keep yre gpu cooler

#

also setting yre refresh to 120 is another option , especialy if you dont play high fps games like CS2

#

and consider staying on DXGI

#

this is why DXGI is recommended

#

if you can do 120 native , and you have the headroom too , 240 shoudn't be any problem

#

but you still need to cap the game at 120

#

and instead vsync from ls , you can use rtss to lock LS to 240 (only for WGC)

#

please , just try

#

ty

#

also if you use rtss , disable any other vsyinc , includeing the game and ls one

#

im playing with wgc too , i know what im saying

#

you can set either global or add yre game , just make sure you set ls.exe to 240 ( some overlays mess up with wgc so this is for safety )

warm python Apr 14, 2024, 6:29 PM

#

how is it so far?

#

no biggy , take yre time

#

altho i strongly advise you to stay on 60 to 120 except if you don't mind changeing the LS cap when the game doesn't reach 120

warm python Apr 14, 2024, 7:07 PM

#

try DXGI

#

altho im preety sure yre gpu limmited

#

also are you sure yre monitor refresh rate is set to 240?

warm python Apr 14, 2024, 7:40 PM

#

anyway , just set yre game to 60 in rtss

#

no need to use global

#

yes , because the gpu has enough headroom to framegen

#

exactly , generateing 120 frames is not easy

#

DXGI can trottle

#

but not by much

#

the base is the problem , you cant framegen without headroom

#

if the game is useing 100% to run at 120 fps , there is no place for LSFG to work

#

thats the lock for LS , not for the game

#

rtss has built in stats , use them

#

go to setting , enable frametime graph

#

and in the main menu you have the 'show own stats' , enable that too

#

why is so hard to understand that you are gpu limmited?

#

thats why 80 to 160 works , but 120 to 240 doesnt

#

and also thats why i keep saying to do 60 to 120 , to not kill the poor bastard whos rendering frames

#

youtube is 60 , and most games barely reach 60

#

and running a monitor on 240hZ is pointless if none of the games can reach it

#

ok , how much does yre gpu use to render 120fps native?

#

exactly my point

#

ignore wgc , stay on dxgi

#

on what resolution you run yre game?

#

go to 720p window mode

#

as a test

#

i wanna prove you that yre limmited

#

good

#

cap the game to 120

#

then use ls

#

dxgi?

#

go dxgi

#

headroom is the left free procentile

#

20% free is aloot

#

with 99% usage on gpu without ls is imposible to framegen

#

thats why it worked on 80

#

native frames are expensive

#

its not

#

keep it 240

#

and use ls on the game , but with dxgi

#

if you dont record yre game then there is no reason to use wgc

#

do you record with obs?

#

because yre so focused on wgc and i dont know why

#

so im saying this for the last time

#

go to rtss , set yre game refresh to whatever you want

#

ignore global and ls.exe

#

go to ls and disable vsync and set api to dxgi

#

whyyyy

#

you cap it with rtss , thats why i said disable ALL vsync

#

rtss is the cap

#

he does the limmitations

#

hes the vsync

#

DXGI is simple , it doubles the curent framerate if the resource is avaible

#

you overcomplicate a simple matter for no reason

#

i keep saying 'stop hammering yre hand' and you reply 'how about my feet'

#

yes

#

my monitor is 60hz , and dxgi shows 120

#

even if i set my game framerate to 100 , dxgi will still show 120

#

then use dxgi

#

also you mentioned that you have more monitors right?

#

why whould you record over 120 fps?

#

no streaming service uses 120fps

#

and recording 240fps makes 0 sense

#

and i asked you like 4 times if you record

#

its beyond me , maybe soneone else can help you with this 'particular' one

#

120fps is more then enough for recording , why you wanna go beyond? i realy dont know

#

1440p recording already is a demanding task

#

use over 120 fps + the insane amount of bitrate to mentain quality

#

its a no go

#

im out , good luck

mystic atlas Apr 15, 2024, 3:25 PM

#

(NOT SOLVED) WGC's fg works, but vsync doesn't work correctly in some of its options.

warm python Apr 15, 2024, 7:08 PM

#

You can't even record at 240fps , not to mention at the same time playing the game at 1440p is already useing 100% gpu , enableing recording will ad at least a 30-40% extra usage and on top of that you wanna add scaleing and framegen ...
Continueing this is pointless , there is no reasoning here

warm python Apr 15, 2024, 7:51 PM

#

Im not angry , only ths could answer you , it cannot get more official then that

mystic atlas Apr 18, 2024, 6:31 PM

#

(BUG) (NOT SOLVED) WGC's fg works, but vsync doesn't work correctly in some of its options.

dire ore Apr 18, 2024, 10:24 PM

#

Is this a laptop?

dire ore Apr 19, 2024, 4:18 PM

#

On laptops, everything is a little more complicated, because there is communication between GPUs. Usually, the final image of the game is in the iGPU memory, then, depending on which GPU the LS is running on, it is either copied to the dGPU memory and then back to the iGPU, or everything remains in the iGPU memory. In the first option, the weak point may be the speed of copying between GPUs, and your FPS may be limited even if both GPUs are not fully loaded, in the second option, the iGPU may not be powerful enough to process all the LS frames and your FPS may also be throttled. At the same time, the operation of WGC and DXGI may differ, as WGC API is quite high-level and makes copying between GPUs on its own. What exactly and how it does it is hidden from the developers.

#

Now back on the topic. Use what works best for you. If something works worse, don't use it. Both WGC and DXGI should work perfectly fine without vsync if you follow all the conditions (such as locking the game's framerate to half the monitor's refresh rate for WGC). If it doesn't work flawlessly without vsync for you, this is where your issue. Start by looking for a problem in your setup.

#

That’s why it requires game fps locking

#

Because cursor in LS is not a system cursor

#

It’s impossible for LS to track the game fps when using WGC capture. This is how this api is implemented by Microsoft. In fact, when we have DXGI capture WGC is obsolete

#

I can't confirm the behavior you observing. Just tried locking the cs2 to 72 fps and LS stays at 144 when using WGC. This game uses system cursor

#

#

Yes

#

WGC requires half refresh rate lock

#

This is why app requires game framerate lock. This is not a recommendation, requirement

#

If you don't want to do it, use DXGI, it's recommended in this case

#

Yes you have to have a steady locked framerate.

dire ore Apr 19, 2024, 6:16 PM

#

I think there is a placebo effect present as the vsync and tearing are opposite things, so enabling tearing has no effect when vsync is enabled.

#

Also, what is the purpose of all these tests?

#

There are no any explicit limitations. Also, I don't think it's a bug, it's rather specific to your hardware because I don't have this behavior

#

Why are you using WGC over DXGI again?

#

What do you mean by image quality?

#

It should have identical image quality unless improperly used

#

Like when you have less FPS than half refresh rate and using WGC

#

Also I hope you're not serious about 1% usage advantage

#

Either way WGC works as it is and won't get any updates. I suggest you to accept its limitations and to use it properly or switch to DXGI

dire ore Apr 19, 2024, 6:51 PM

#

No, it captures the frame at game resolution

#

It just returns frames at dwm rate, it has nothing do to with resolution

#

It will capture 720p

warm python Apr 19, 2024, 6:55 PM

#

This is yre problem , the gpu cannot handle it

#

so please , stop this nonsense

#

and accept yre gpu limmitation

#

im done

#

there is no reasoning with you

dire ore Apr 19, 2024, 6:58 PM

#

I don’t need this weird test as I developed this app and know what I’m talking about

#

You can check it with any graphics debugger you have

#

Even so, doesn’t mean it has better quality

#

When using vsync 1/4, LS will run at 60 FPS, capturing 30 frames and generating 30 frames more.

#

People saying it looks better indeed having less artifacts because they misuse it and ignore the half refresh rate lock requirement. This way, saying they have 30 fps game and a 120 hz screen, they see 3 duplicates and 1 generated frames, each 4 frames. They see 120 FPS on counter, but this is not real FPS.

#

This way there is no any difference. WGC just captures a frame, same as DXGI.

#

Both WGC and DXGI capture frames from DWM, only DXGI can report the frame timestamp while WGC cannot

#

They both should capture 60 frames. LS has a different capture-rendering pipeline for each, DXGI mode is driven by game frame rate, while WGC by LS frame rate. As the LS will have 120 FPS, it will capture a frame, present generated, wait one frame and present original. This way it captures at 60 frame rate.

#

Np. I hope I made it more clear to you

#(BUG) (NOT SOLVED) WGC's fg works, but vsync doesn't work correctly in some of its options.