Blur Busters Forums

TakenZ wrote: ↑

27 Dec 2020, 03:08

G-Sync adds input lag and makes frames appear at the same time (so I’ve read), but when your FPS is over the refresh rate constantly, why would you want the extra input lag?

G-SYNC does not "add" input lag, it prevents tearing, and tearing reduces input lag further by being present at the cost of the artifact itself.

For framerate within the refresh rate, the input lag difference between G-SYNC and no-sync is negligible at higher refresh rates, and is solely due to the lack (or presence of) of tearing. For framerate above the refresh rate, there can be a bigger input lag difference between G-SYNC and no-sync (due to an increase of tearlines in a single scanout cycle with the latter), but the framerate has to be very high above the refresh rate for the reduction to be appreciable, and once you hit 240+ Hz, this difference between the two becomes less and less.

The higher the refresh rate, the shorter the scanout duration, and the shorter the scanout duration, the less time there is for the screen to tear. Once we hit 1000Hz, syncing methods will effectively become obsolete.

G-SYNC is a stopgap to native tear-free monitor operation, much like strobing is to motion blur.

TakenZ wrote: ↑

27 Dec 2020, 03:08

So not the secret overdrive setting of 120?

Don't use it until your PC can handle constant 100fps+.

jorimt wrote: ↑

27 Dec 2020, 10:19

TakenZ wrote: ↑

27 Dec 2020, 03:08

G-Sync adds input lag and makes frames appear at the same time (so I’ve read), but when your FPS is over the refresh rate constantly, why would you want the extra input lag?

G-SYNC does not "add" input lag, it prevents tearing, and tearing reduces input lag further by being present at the cost of the artifact itself.

For framerate within the refresh rate, the input lag difference between G-SYNC and no-sync is negligible at higher refresh rates, and is solely due to the lack (or presence of) of tearing. For framerate above the refresh rate, there can be a bigger input lag difference between G-SYNC and no-sync (due to an increase of tearlines in a single scanout cycle with the latter), but the framerate has to be very high above the refresh rate for the reduction to be appreciable, and once you hit 240+ Hz, this difference between the two becomes less and less.

The higher the refresh rate, the shorter the scanout duration, and the shorter the scanout duration, the less time there is for the screen to tear. Once we hit 1000Hz, syncing methods will effectively become obsolete.

G-SYNC is a stopgap to native tear-free monitor operation, much like strobing is to motion blur.

Oh okay that makes a lot of sense. I see no reason to not have it enabled 24/7 then. Thanks for the help!

DukeDice929 wrote: ↑

27 Dec 2020, 15:37

TakenZ wrote: ↑

27 Dec 2020, 03:08

So not the secret overdrive setting of 120?

Don't use it until your PC can handle constant 100fps+.

Okay gotcha so if I wanted to be “optimal” I’d enable 120 OD for games like Valorant and Overwatch (where I get over 100 FPS easily) and use 60 OD for Warzone. So much optimizing can be done with PC gaming !

This monitor does seem fantastic so far. Fast IPS, fast response times, and G-Sync has made me feel like upgrading my PC is not something that’s necessary atm. Thank you all so much for the help! This forum has been a fantastic resource

Has anyone found a way to fix the deep sleep glitch for this monitor, it is driving me nuts and i really need help.

Chief Blur Buster wrote: ↑

12 Dec 2020, 22:27

The 1079 trick is a general trick with some monitor-specific quirks. Please note, the 1079 trick is used with some different monitors (it was successfully used on a few models, mainly non-HDR models) -- so it may not be compatible with all models (VG259QM may be having problems with this).

Your assumption is right. MAG251RX has HDR so you need to delete HDR data in CEA-861 "data blocks" field to make it works but 1079 is not necessary, you can just delete all the other hz, for example if your monitor is 1080p 240 hz like mine, you should delete 1080p 60 hz, 1080p 120 hz and so on, no need to use 1920x1079. But the problem is HDR is pretty nice in my opinion so if you have any suggestions to keep HDR and keep lightspeed alt-tabbing, you are welcome to share it.

pusep wrote: ↑

29 Dec 2020, 07:21

Your assumption is right. MAG251RX has HDR so you need to delete HDR data in CEA-861 "data blocks" field to make it works but 1079 is not necessary, you can just delete all the other hz, for example if your monitor is 1080p 240 hz like mine, you should delete 1080p 60 hz, 1080p 120 hz and so on, no need to use 1920x1079. But the problem is HDR is pretty nice in my opinion so if you have any suggestions to keep HDR and keep lightspeed alt-tabbing, you are welcome to share it.

This definitely works too. I've made this recommendation before.

However, a lot of us don't want to delete Hz.

Yeah, there are pros/cons of each method.

Whats the "1079 Trick"?

Chief Blur Buster wrote: ↑

29 Dec 2020, 15:03

pusep wrote: ↑

29 Dec 2020, 07:21

Your assumption is right. MAG251RX has HDR so you need to delete HDR data in CEA-861 "data blocks" field to make it works but 1079 is not necessary, you can just delete all the other hz, for example if your monitor is 1080p 240 hz like mine, you should delete 1080p 60 hz, 1080p 120 hz and so on, no need to use 1920x1079. But the problem is HDR is pretty nice in my opinion so if you have any suggestions to keep HDR and keep lightspeed alt-tabbing, you are welcome to share it.

This definitely works too. I've made this recommendation before.

However, a lot of us don't want to delete Hz.

Yeah, there are pros/cons of each method.

What are the cons of pusep's method? been using it for a week so far and it's been fine except one time my screen flickered and the Night Light turned off and on that I use in Windows 10 but that could be anything, also sometimes my monitor turns on after the bios at start up which is a good 10 second instead of 2-3 seconds

Blxze3 wrote: ↑

27 Dec 2020, 21:44

Has anyone found a way to fix the deep sleep glitch for this monitor, it is driving me nuts and i really need help.

ToastyX CRU restart64.exe sometimes fixes things for me, if the glitch is GPU-side or a glitch on VRR enable/disable. I keep a desktop shortcut to restart64.exe if I'm getting problems.

However, not all monitor bugs won't get fixed.

davidm71 wrote: ↑

29 Dec 2020, 16:01

Whats the "1079 Trick"?

The idea is a custom resolution with only one refresh rate, to prevent mode switches.

1. Create a custom resolution of 1920x1079 with only ONE refresh rate.
2. Either disable VRR completely, or enable VRR for everything (including windowed) to keep sync tech the same in game+windows
3. Configure Windows to that resolution
4. Configure Game to that resolution
5. Disable monitor scaling (set to "Aspect" or "1:1")
6. Configure GPU scaling to 1:1 so GPU does not scale

This gains some advantages:
1. Mode switches are eliminated. No more refresh-rate-change or VRR-change blackouts.
2. Game is forced to use the max refresh rate
3. Alt+Tab becomes instantaneous from FSE. No 1-second blackout behavior anymore (even for FSE)
4. You only lose one pixel row (less than 0.1% of screen) for the improved convenience

However, compatibility can be inconsistent
- Not all monitors work well with 1920x1079 without scaling (blurry text flaw on some models)
- You may lose features such as HDR

Alternative option instead of 1920x1079:
- Other off-by-a-few modes, such as 1920x1078 or 1919x1080 or 1918x1080, which may work better with zero-scaling.
- Via ToastyX CRU, delete all refresh rates except the max Hz. (use reset-all.exe to restore deleted refresh rates).