Thread 713912659

This shit is literally placebo
vsync too

>>713912659 (OP)
>eyesight so bad he cannot see screen tearing
...k

For some reason it just flat out doesn't work with some games and I still get tearing even if I force it.

I've not seen screen tearing for about 15 years. lol

>>713912954
Because most games have vsync on by default and you don't change it or your monitor has g-sync

>>713912869
you understand that it will do basically nothing if the game is running at higher fps than what your monitor supports right?
if you are getting 140 fps and your monitor is 160 hz, it works.
if you are getting 140 fps and your monitor is 120 hz, it won't work, or at best it will perform like vsync.
you are supposed to lock your fps to 5/10 fps less than your monitor refresh rate to make sure it's always properly engaged

>>713912659 (OP)
>i dont know how it works so its dumb
k keep us posted based retard.

>>713914437
because I don't buy underpowered hardware

>>713914508
Nah, didn't know that, I hate messing with all this shit.

>>713915042
>>713914508
Wouldn't locking it to anything that isn't a variable of 60fps look like shit though?

>>713914508
partially true

v/free sync work via division of your fps against the refresh rate of your monitor. as long as the FPS = a number that can equally divide by your mhz you gucci mang. no tearing, looks smooth. the number can dynamically change as fps goes up or down.
normal vsync is just a flat rate lock, it cannot adapt to changes in fps...thats why it sucks dick and causes input latency

>>713912659 (OP)
Poorfag cope

>>713915325
>as long as the FPS = a number that can equally divide by your mhz
What the fuck does this even mean? Equally divide by what amount? 5? 10?

this is what happens when you don't go to your optometrist annually fellas. keep it in mind. soon this dude is gonna say that fps is a meme because motion perception doesn't exist.

>>713914508
You don't have to do this anymore. It just works.

>>713916169
But it doesn't, at least not with some games. There is still tearing in Signal Simulator.

>>713915325
Your fucking retarded mate. Free sync and g sync work because it's changing your monitors hz to match the frame rate. If your outputting 67 fps then your monitor is doing 67hz.

V sync needs to be divisible. If you have a 120 hz monitor then you need to do either 30,60, or 90 fps and even then it's just holding frames which is what creates the input lag and the disconnect from what's showing on screen and what's happening in engine, which is why people shit on v sync.

>>713915193
>>713914508
G-Sync/freesync fix the problem of vsync only operating on "halves" where 120Hz with a dropped frame becomes 60, then 30, then 15... By presenting the frames as they arrive even if it's late, it creates a much smoother experience.
However you should NOT be "locking your FPS to 5/10 below to keep it engaged." That's crazy talk cargo cult nonsense. The only time you should be messing with framerate caps is because your GPU is making too much noise doing 300fps and you don't like the driver's method of reducing GPU usage. Or if the game you're playing is programmed like trash and the physics breaks at high FPS or something.
You don't WANT g-sync engaged more than it has to, but you DO want it to work when it needs to.

>>713916239
Unity engine does not play well with syncing tech at all, that's an engine issue

>>713912659 (OP)
>V-sync too
With v sync on I miss shots while playing fps, turning it off stops the delay and I go back to being good
But it looks like shit
But G Sync ruins my PC, everytime I wake it up it starts flickering until I turn gay sync off
And my non gsync monitor runs games at like 55 fps if I enable the g sync compatible shit

>>713916543
...you want g-sync engaged at absolutely all times, because otherwise you get screen tearing, and you want your framerate capped below your refresh rate so it never disengages

>>713916559
Unity unfortunately taught a generation of wannabe game devs a pack of lies about deltaTime and the end result is broken as shit games that can't cope with any framerate deviation beyond the devs own hardware. Sad truth that. You can't fix stupid and Unity brought a lot of stupid to the world.

>>713916543
This. You should just cap to your monitors limit. Going over is just a waste of energy. Technically input lag goes down but let's be real, your not some esport champion that needs that .01 ms to feed his family.

>>713912659 (OP)
if i have this on at all my games randomly change my monitor refresh rate while playing causing my monitor to turn off and on again so i never have it on.

>>713916689
G sync will engage and disengage when it needs too. You don't need to do anything. If your above your monitors limit it doesn't matter.

>>713916689
You're misunderstanding the technology. When g-sync is implemented as most people expect it to you should never get screen tearing. G-sync operates like vsync, only ever presenting the next frame when the monitor is ready to present a frame.
Unfortunately retardation about "muh vsync input lag" as if that meant anything at >120Hz has caused retarded game devs to STOP sync'ing if the detected FPS is higher than the monitor refresh. That's a completely separate issue to g-sync and that's a "this game is programmed shit so we have to fix it with out of band hacks." If a game implements g-sync correctly, such hacks are not only not necessary, but they are actively detrimental to the experience, so don't do it unless the game you're playing is BROKEN without them. And don't tell people it's a universal flaw in the technology when it isn't. That's why there's so much cargo cult nonsense in PC gaming.

because this isnt issue anymore
monitor leave actual performance behind now days
there is no longer issue where your monitor hz is too low unlike in 2002
1440p 160hz monitor is dirt cheap these days compare to GPU

>>713914508
? The whole point is that it syncs the FPS to your refresh rate. If you have a 120hz freesync monitor and you run a game with the framerate unlocked it will not exceed 120FPS. Gsync is supposed to be a superior premium solution so if it doesn't do the same... lmao.

Its not placebo, your monitor is likely just defective or you got le scammed. I'd know because I got a freesync monitor that claimed to be gsync compatible and that shit absolutely does not do anything at all even though I'm extremely confident it worked beautifully on my older 1080p gsync display and I never experienced tearing of any kind in any game with vsync disabled.

I liked it, but then I got a freesync monitor

>>713914508
>you understand that it will do basically nothing if the game is running at higher fps than what your monitor supports right?
So just lock your FPS and Gsync works fine. This isn't hard at all if you've been using a computer for longer than 10 minutes.

what about frame stuttering?
I have this problem way more often than screen tearing which I dont think I ever seen it ever
game would run smooth 144 fps but then for one second it will drop to 30 and basically freeze the game for 1 sec before returning to 144fps

>>713917153
Likely a cpu bottleneck or your maxing out your vram.

>>713912659 (OP)
You have to switch it on

>>713916768
>Technically input lag goes down
I assume you meant up, but yeah, I agree completely. We're talking single digit ms of lag at most because it's only a whole frame of lag on the WORST CASE, the average case being half that and the typical case being microseconds.
What's really retarded is people talking about "input lag" in games that have so much frame pacing compensation that the whole game has 10-30ms of input lag baked in. If people didn't bitch so hard about these things devs could just present the frames raw and reduce the total input lag by far more meaningful margin than any "pro gamer" can affect with driver tweaks on their overclocked monitors playing with that last 1ms they have control over.

God this thread gives me brain damage just reading it. Here's what you stupid fucks should do:

>Vsync off in-game
>Vsync on in driver
>Gsync/Freesync on in your OS and monitors OSD
>Cap your fps 1-3fps below your monitors maximum hz (order of preference: in-game > RTSS > driver)

If you're confused or have any questions please ask.

>>713917153
Download framecapx or presentmon. It will tell you what's bottlenecking you either CPU/GPU/Process.

>>713917086
many "g-sync compatible" monitors are not as good as the old g-sync. Old g-sync was an expensive module nvidia made that operated on specs they set themselves. freesync was a much looser standard. But nvidia, scared of losing the market to the vesa standard because monitor manufacturers were annoyed at having to pay Jensen for this g-sync tumor decided to start "certifying" freesync monitors for g-sync use. This largely meant adopting the lesser standard as g-sync but not informing the customer of the downgrade. That's why you should never pay attention to bullshit labels. Only look at the specs. What's the frequency range? 48-120Hz being the standard is why PS5s on TVs stutter like a mofo because it can't accommodate the common case of a console dropping to 30-40fps, where a g-sync one could have.

>>713916543
>However you should NOT be "locking your FPS to 5/10 below to keep it engaged." That's crazy talk cargo cult nonsense.
This is a thing, it's part of what Reflex does.

>>713912659 (OP)
its placebo on consoles because its gay generic vrr. ps5 disables it when the fps dips below 48.

>>713917091
same, with a cheap vrr monitor and nvidia gpu

>>713917769
I just ordered a 9070 xt
Very exciting

>>713917335
Why would ever turn on Vsync in driver? Even if it's to remove screen tearing in case Gsync somehow fails, you are getting input lag, which is much worse.

Why cap your fps below maximum hz?

>stupid fucks
There is so much misinformation and a lack of hard concrete EXPLICIT instructions being provided by manufacturers for a stupid issue that shouldn't even exist. Screen tearing should not be possible with consumer technology, we should have never moved on from CRT's.

>>713915325
>..thats why it sucks dick and causes input latency
it causes latency because it holds extra frames in a buffer. this buffer can be disabled with "low lag vsync", by setting a framecap of 0.01 below the vsync refresh rate

>>713914508
dont quote me on this but i think nvidia does this automatically with the later drivers

>>713916485
if you have a 120hz screen you can most likely set a custom hz of anything between 60 and 120, you could set it to 78hz for example. in nvidia control panel or that other software i cant remember the name of

>>713917335
Cap your fps 1-3fps below your monitors maximum hz (order of preference: in-game > RTSS > driver)
Why do you need to cap your frames when you have a PC that can max that without problems or stress it?

>>713916993
dont listen to this guy, he cant notice vsync buffer lag and gives bad angry autistic advice based on that

>>713917813
nice buy, hope to switch to amd at some point in the future

>>713917335
>all of this information becomes worthless if you factor in frame generation
i love technology :3

it's pointless because all monitors are 120-240hz now. tearing only shows up on 60hz screens

>>713918181
why? i just got one because i've never tried amd

>buy gsync/freesync 144hz 4k gaming monitor
i'm not setting any FPS limits unless the poorly written game engine insists upon itself (FromSoft, Team Ninja, etc.).

if my current system can't push 144+ FPS at 4k to keep up with my stupid monitor i lower the resolution until it does. works for me.

>>713917912
>>713917981
Sorry for the late response. Please read this.

https://help.steampowered.com/en/faqs/view/418E-7A04-B0DA-9032

>>713918223
This applies to frame generation as well.

>>713912659 (OP)
You just can't tell because every monitor today comes with some form of freesync (this is not v-sync). Gsync is just the "premium" version of the same thing.

>>713919820
>if you're confused or have questions feel free to ask
>links a fucking steam guide
>a steam guide that STILL doesn't explain why you would have Vsync enabled ever

your mom loves hobo cum

It works okay for most games, I usually just cap to 160 on a 165 hz monitor
But even when its a solid 160 I'll check the hz on the display and it's going all over the place from like 120 all the way back up to 165 and just changing numbers all the time. Looks smooth but wtf is up with hz being all over

>>713912659 (OP)
recently for the first time i got a monitor that said freesync compatible but i have no idea how you are supposed to set it up or anything

>>713912659 (OP)
I have no idea what most of the options for Nvidia even do.

>>713917652
165hz

>>713912659 (OP)
This. FreeSync is the REAL shit.

What are actually the best ways to minimize input lag?

>>713917652
They don't sell g-sync moduled monitors anymore huh?

>>713920369
frame delivery. the hz being all over is the intended effect of the technology.

>>713920941
Being better player is the biggest one.

>>713920941
avoid texas

>>713920968
They do, but they're now labeled G-Sync Ultimate, which denotes they have a real module and support HDR, and are few and far between: https://www.nvidia.com/en-us/geforce/products/g-sync-monitors/

>>713920941
>fast single core speed and RAM
>fast GPU and VRAM
>PS/2 keyboard and mouse
>v-sync off
>frame-limit off
that's about the best you can do.

>>713921143
no they're just labeled 'G-sync', and the non-ones are 'G-sync compatible'

>>713912659 (OP)
Does GaySync work by default or do you need any configuration for it?

>>713912781
fpbp

>>713912659 (OP)
I had to disable it because I kept getting issues and the popup telling me g-sync was available was extremely annoying

>>713921821
>the popup telling me g-sync was available was extremely annoying
This. I got rid of my g-sync monitor because of this shit. Bought a nice Freesync monitor instead. Way better. No popups.

>>713921821
popup? do you have nvidia bloatware installed or something?

>>713922064
oh and I remembered why I got rid of most of this shit: even windows 11 start menu kept triggering this crap

>>713921007
Ah I see

>>713922165
I've always found the Windowed mode version just doesn't work. Anything with any sort of graphics acceleration (most stuff in modern OSs and browsers) triggers it. Changed it to fullscreen only and it doesn't give any problems.

>>713922319
I guess that's a solution but I play stuff in borderless fullscreen because it's easier to tab out with multi monitor and I recall it not triggering properly or something

>>713922418
Fullscreen mode works for borderless fullscreen games, at least in Windows 11. Most modern games don't support exclusive fullscreen anymore. DX12 can't even do it.

>>713922551
neat

>>713916559
yeah, it turns out Unity is actual really a shitty engine. Indie devs hyped it up because Unity was much, much cheaper than the million dollar Unreal Engine licensing fee...but after Tim stopped being such a greedy prick with the UE licenses every Indie dev is abandoning Unity.
>memory leaks that become pronounced as fuck in any game more complex than gacha games
>games that take your graphic settings as an opinion sheet instead of actually using the values you set

>>713919820
nope

process for frame generation is totally different annnnnnnddd also depends on the make of your gpu and which frame generation you are planning to use

anyway its extremely autistic and u need 7 overlays open to actually verify the best method for each game and it fucking sucks

what i know is that rtss limiter when fg is active will not decrease input lag so u never want to use it

>>713922064
cant you just turn off the notification pop up?
Im sure there is 3 dots button or something that let you turn it off

>>713923645
>>713920245
those are official instructions from valve creators of your RADV driver and esports. You think you're more smart than them? Fucking jits.

>>713924792
Yeah those anons are retarded.

screen tearing is a r*ddit complaint
never noticed it. always turn off vsync on 144 hz monitor

>>713925034
Vsync. ALWAYS off.

>>713924792
retard its a cs2 article from some blogposter

those who write documentations are literally janitor types

where does it mention anything about frame generation? did u even see the shit u linked? spastic fuck

>>713922138
I get it . it's on the monitor. When you have an actual G-Sync monitor a small pop up appears with the Nvidia logo telling you it's connected.
it doesn't happen on a G-sync compatible screen because it's not real G sync.

>>713926860
Doesn't happen on my G-Sync monitor (Dell S2417DG). I did get a Windows pop-up the first time, but you can disable notifications for the Nvidia Control Panel. although I've never seen it since the first time and I disable it a lot when switching to ULMB.

People have all the amazing material from Blur Busters and Battlenonsense at their finger tips, and yet their understanding of variable refresh rate and how it interacts with vertical sync is so fucking poor. How long has this tech been out, a fucking decade? I get an aneurysm reading these fucking threads.

probably a skill issue of not knowing how to set it up

>>713912659 (OP)
It's bullhit to inflate the price of monitors. Meanwhile Freesync exists.

>>713929492
Monitors depreciate very quickly in value, but they don't really fail often. I got my G-Sync monitor in 2018 for $200 used, just a year after it released for $600.
Just take advantage of retards who always have to have the latest thing.