NVIDIA G-Sync Pulsar monitor - Asus ROG Strix XG27AQNGV

[mango87]

I finally made the plunge to purchase this monitor. It seems the firmware has matured enough for console and high fps gameplay.

[pablo v2]

Rocket League has never looked better at 1440p with 360 Hz Pulsar, RTSS VRR cap 342 FPS, after updating to the latest firmware. It’s hard to put into words, but as someone who’s been playing this game for 10+ years on just about every panel imaginable, there’s something special brewing here.

[Discorz]

You wanted sharper motion, you got it! High Hz ULMB used to be limited to ~>1ms minimum, now it can go lower. This does come at the cost of more inconsistent top-bottom crosstalk as Hz goes up, because the strobe method has been changed. Kind of a 1 step forward, 1 step back situation. But I'm sure many will appreciate the update.

I do wonder if the 240 and 360hz modes still didn't change the same way as the 120hz mode did.
On firmware 1.1.8 the changelog specifically said "Improved 120Hz ULMB2 quality (Global flash instead of rolling scan)"
This patch it only says "Improved moving image sharpness for 240 and 360 ULMB2 and Pulsar"

Could be a typo, or this is how they refer to boosted backlight scanning speeds. I don't see why use plain global flash if rolling provides better results crosstalk wise - it catches slightly larger portion of complete GtG. So I think ULMB 360 and 240 is now using the same method as 120 and 60 Hz. Just a reasonable assumption! Pulse Width now probably follows ULMB1 2.5–25% duty rule more closely, just like 60Hz did at release.

What about Pulsar? How much did they manage to improve MPRT? Someone should test whole VRR range in Smooth Frog. Eg. 360-240-144-100 fps or similar. Do it with Rtings pattern please. It has a neat MPRT indicator. And we already have Rtings pursuits from old firmware to compare against. If anyone needs help with instructions, let me know.

[hammelgammler]

Okay fuck it, got the Asus XG27AQNGV for effectively 400€ now, let’s hope it doesn’t have much backlight bleeding or dead pixels.

I want to see if the improved motion clarity is worth the trade-off compared to OLED and also want to compare it to my Sony FW900/W900 CRTs.

On paper, I think I might actually prefer it to my CRTs, because phosphor trailing, the not as razor sharp of an image, not as perfect geometry and fear of it breaking. Maybe I can live with the IPS downsides better.

Because on the pro side, this monitor should have the same great motion clarity (maybe even better) at 60Hz, but in addition 120Hz and even up to 360Hz, which might be great for older SDR games that I can run at those FPS. Also 2560x1440p is a good step up from 1920x1200.

I would have also more space on my limited desk, allowing me to use mouse/keyboard games. With my CRTs in my current home, there’s simply no space for it.

All in all, I’m looking forward to it. Also I feel the need to somehow “support the cause” in a way, as with everything, if no one is buying it, they will simply discontinue the tech, which would be a shame.

Also I just found out, that the Switch 2 actually supports 1440p120! If most games will consistently run at 120 FPS, then to me this seems like the best experience you can get. If I like the monitor, I might actually buy a Switch 2 after all.

Only thing I’m not looking forward to, is the announced 5k144 pulsar monitor, which could be my SDR gaming monitor of choice. But given the not as available 5k panels in general, maybe the response times are simply not good enough to allow such a great motion clarity. I just don’t want to gamble on that monitor to be a straight upgrade for gaming, which is why I pulled the trigger now.

[liquidshadowfox]

You wanted sharper motion, you got it! High Hz ULMB used to be limited to ~>1ms minimum, now it can go lower. This does come at the cost of more inconsistent top-bottom crosstalk as Hz goes up, because the strobe method has been changed. Kind of a 1 step forward, 1 step back situation. But I'm sure many will appreciate the update.

I do wonder if the 240 and 360hz modes still didn't change the same way as the 120hz mode did.
On firmware 1.1.8 the changelog specifically said "Improved 120Hz ULMB2 quality (Global flash instead of rolling scan)"
This patch it only says "Improved moving image sharpness for 240 and 360 ULMB2 and Pulsar"

Could be a typo, or this is how they refer to boosted backlight scanning speeds. I don't see why use plain global flash if rolling provides better results crosstalk wise - it catches slightly larger portion of complete GtG. So I think ULMB 360 and 240 is now using the same method as 120 and 60 Hz. Just a reasonable assumption! Pulse Width now probably follows ULMB1 2.5–25% duty rule more closely, just like 60Hz did at release.

What about Pulsar? How much did they manage to improve MPRT? Someone should test whole VRR range in Smooth Frog. Eg. 360-240-144-100 fps or similar. Do it with Rtings pattern please. It has a neat MPRT indicator. And we already have Rtings pursuits from old firmware to compare against. If anyone needs help with instructions, let me know.

So I have it activated in smooth frog, what exactly am I looking for? what should I set the pan speed to? Currently have px/sec set to 3840 atm

[liquidshadowfox]

Here are the amateur pursuit shots with my samsung fold 7 + Settings I used

XG27AQNGV 350 fps firmware 1.10 camera settings 1/350 iso 3200


XG27AQNGV 250 fps firmware 1.10 camera settings 1/250 iso 1600


XG27AQNGV 180 fps firmware 1.10 camera settings 1/180 iso 1600


XG27AQNGV 125 fps firmware 1.10 camera settings 1/125 iso 800


XG27AQNGV 90 fps firmware 1.10 camera settings 1/90 iso 640



I tried to get the shots as close as possible to what I visually see but without a rail or better camera it's difficult for me I do notice there is the SLIGHTEST faint crosstalk but I don't see that in game, not sure if it's got to do with the grey background, my PC, or otherwise. I'm using my monitor with contrast set to 80.

[kyube]

Press middle mouse button to spawn the sync track, it's required for validity.
Use px/fr, not px/s.
See this explanation

[hammelgammler]

Maybe a dumb question, but does the monitor work properly with a Switch / Switch 2 and ULMB2?

1. I know the Switch 2 generally supports outputting 1440p120, but most games still only run at 60. So I guess I should set the output to 1440p60.
2. How does the Switch 2 (or other consoles) prevent tearing? Are they using VSync and therefore also have the large VSync input lag? Because of strobing I would of course need a perfect 60 FPS output.

[mawi]

Maybe a dumb question, but does the monitor work properly with a Switch / Switch 2 and ULMB2?

1. I know the Switch 2 generally supports outputting 1440p120, but most games still only run at 60. So I guess I should set the output to 1440p60.
2. How does the Switch 2 (or other consoles) prevent tearing? Are they using VSync and therefore also have the large VSync input lag? Because of strobing I would of course need a perfect 60 FPS output.

Since the latest Switch 2 OS update from a few days ago vrr is also possible on TVs, Not just in handheld Mode. But i have no idea if that works on a pulsar Monitor. Probably not

[hammelgammler]

With the latest 1.1.10 update, is Pulsar@240FPS the same as ULMB2 PW=100 240Hz in terms of MPRT?

Edit: Given those two tables from drG-SYNC on the NVIDIA forum, it seems like yes:

IMG_5626.png (62.27 KiB) Viewed 75 times

IMG_5627.png (26.12 KiB) Viewed 75 times

That would be pretty neat, to have an easier time with no tearing. I didn’t get Scanline Sync (Special-K or RTSS) to work properly, but I really don’t want to have neither tearing nor the high V-Sync input lag.

I will likely use ULMB2 @ 60Hz, 120Hz and Pulsar for everything around >200 FPS, as a fully stable 240 FPS for ULMB2 240Hz is rather hard to achieve.