ELK wrote: ↑01 Feb 2020, 17:44People wire an led into their mouse and use expensive high speed cameras to see how low a change occurs on screen.
I DID NOT CHANGE ANY AUDIO DRIVERS TO MSI. I tested my nvidia audio and it works. The card is made to support MSI, anything that isn't won't function at all.
Use RTSS as an fps limiter because NVCP is a driver level fps limit that will give you more fps lag than a cpu level limiter like RTSS. It's unfortunate the in-game limiter isn't a good option as they usually have the lowest input lag.
The difference between 144 and 140 is about 0.2ms. You could use RTSS fps limiter and get the extra 0.2ms without tearing if your fps wasn't 144 stable.
I am wrong. Vsync off is slightly better, by 1-3ms according to that page.
https://blurbusters.com/gsync/gsync101- ... ettings/9/
"So, for competitive players, V-SYNC OFF still reigns supreme in the input lag realm, especially if sustained framerates can exceed the refresh rate by 5x or more. However, while at higher refresh rates, visible tearing artifacts are all but eliminated at these ratios, it can instead manifest as microstutter, and thus, even at its best, V-SYNC OFF still can’t match the consistency of G-SYNC frame delivery."
Consistency is very important when it comes to aim. The current best option in my opinion would be RTSS's SSYNC so that you have no tearing without the input lag of vsync, but you will have the input lag of a cpu level fps limiter. It's the best option because the in-game fps limiter doesn't work. If it did work the best option would be to set it to 140 or even 120 and use gsync + vsync NVCP, in-game vsync disabled. The difference between 140 and 144 is only about 0.2ms.
I only recommend using fast sync if you're using RTSS's SSYNCx2 because a game's fps limiter isn't working or isn't good, but this requires you to have a stable FPS twice that of your refresh rate. which would be 288 stable on your 144hz screen.
You will have the lowest input lag with vsync/gsync disabled by a hair, but how it effects your aim isn't worth it.
edit: cpu based fps limiters add 1 frame of input lag so you're looking at ~7ms extra input lag for the perfect consistency.
Alright I have turned MSI to GPU (only) and restart my PC, dont feel any change for now, but will keep using/testing it.
if it comes to RTSS vs NVCP i heard NVCP gives you more stable framerate... But if RTSS is better so I will use it.
Now... the Scanline... how do I set it? It can't be run with any form of g-sync/v-sync
https://www.reddit.com/r/nvidia/comment ... is_a_game/
I found we need to use -30?? or how do I setup it?
"2a. FPS at the image refresh level -> set "Scanline sync" to a value between 1060-1120 for a 1080p monitor, for other resolutions -50."
I suppose to set scanlince sync at 1080?? or what? i dont get from where we got this huge number
Im kind of confused now...
So for now what I know (correct me If am wrong)
1) FPS limiter in game is the best for low input lag, if it doesnt work corecctly we should use RTSS
2) FPS Limit should be always bellow HZ of monitor (unless it can only 5x double refresh rate) ->> no matter we dont use VSYNC?????????????? (because then I could just dont use any form of g-sync/v-sync, use Ultra low latency + 0 fps in RTSS, so i could have even 200+ fps
3) Optimal option, a little bit bigger input lag but best visibility -> free sync (g sync compatible) + vsync in NVCP + null + RTSS cap at 140 fps.
4) Scanline is still a "?" to me