NVIDIA G-Sync Pulsar monitor - Asus ROG Strix XG27AQNGV

[RonsonPL]

The image retention is terrible. This can't be used as a crt replacement unless you only play 240p games. If you try to play 480i games with retrotink's crt simulation it will have image retention in less than a minute. Apparently this is common with IPS panels. Maybe they could have the next pulsar on a good VA panel.

What? It's my first IPS monitor and I never heard about it. Why would nobody talk about it? Could you post a link to source of this info?
BTW. IPS panels are not exactly 100% fast enough, but VA panels will never, ever reach the point where they're suitable for anything other than a static image. There's no VA panel fast enough and there will never be. I've been saying that for past 15 years on various forums and was told "just wait, the tech will advance". Well? It didn't. And it surely won't now when OLEDs are slowly approaching "cheap" price zones.

Bonus annoyance points on Linux, as Nvidia drivers on Wayland can only disable/ignore VRR for ULMB by using a nvidia-modeset parameter (Meaning a reboot is required every time you want to change it ). A simple OSD toggle bypasses this issue.

That's a downer. I'm planning to abandon Windows entirely to play on Linux.

Given that you used a FW900 before, how would you say does it compare to the current pulsar monitors in terms of effective motion clarity?

Apologies, but I couldn't test it. We had to pack everything back up after just a brief moment and real life will prevent me from testing it properly anytime soon, so I won't be able to provide any of promised opinions, sorry


So far: 360Hz mode in Battlefield 6 looks OK. I enabled NVidia's frame gen on RTX 5070 and I was not annoyed by blur when flying a jet (the mouse is only 1000Hz so this was a better test idea) - but that's far from demanding scenario.
UFOtest came out visibly worse than on my XL2411Z if I'd compare to Benq set to very short strobe time, but it's OK. It was 360Hz, Pulsar ON, browser's ufotest showing it synced correctly to 360 and I'm sure there were no issues.

I'd say it's well within "OK" for me. Not a razor sharp CRT-like, but I can see moving object, not a blurry soup, which is nice For people who never had one of those TN panels with superb low persistence mode or any CRTs, it's what they'll call "crystal clear". For us - just OK.


Blacks are visibly worse than on my Benq XL2411Z
The contrast and colors so far are a big disappointment, although I didn't tinker with it too much and maybe set brightness too low (I set it to what I liked in a room, day time, but with shades on windows closed)
I honestly expected more from "crappy old TN" vs. "most modern IPS".

I didn't even had time to enable ULMB
Basically I unpacked it to see if I wasn't unlucky to get a bad one with horrible backlight bleed.
And yes. Whoever designed the bay for video ports at the back, should be fired. You cannot plug anything without damaging the cables. Brilliant. :/
And despite it not being 4K 480Hz DP 2.1 monitor, the cable is too short for how I have my PC placed. If your PC doesn't stand next to your monitor, you may need to buy a separate cable. For a monitor that launched at 700-750€ for 27" 1440p IPS LCD, it's a slap in the face, but hey, at least Nvidia doesn't force us into G-sync monthly subscriptions...

...yet

If there's anything left to be said about this monitor by the time I finally can test it properly and most importantly PLAY anything on it, I'll post here, but don't hold your breath. Might be December for all I know.

[mawi]

If it hasn't been mentioned already, the OSD lacking a VRR toggle is annoying for me. My much cheaper VG27AQM1A has a toggle that you can use without having to open NVCP every time.

hehe... most folks (me included) want the pulsar switch on NVCP, you want VRR toggle on OSD. I agree having both on both would make sense.

[kyube]

If it hasn't been mentioned already, the OSD lacking a VRR toggle is annoying for me. My much cheaper VG27AQM1A has a toggle that you can use without having to open NVCP every time.

Bonus annoyance points on Linux, as Nvidia drivers on Wayland can only disable/ignore VRR for ULMB by using a nvidia-modeset parameter (Meaning a reboot is required every time you want to change it ). A simple OSD toggle bypasses this issue.

I've mentioned it at the start of my rants in here already.
It's OK, Nvidia is just a small indie dev company, they have no resources to implement the exact same feature set every single monitor on the market has

What? It's my first IPS monitor and I never heard about it. Why would nobody talk about it? Could you post a link to source of this info?
BTW. IPS panels are not exactly 100% fast enough, but VA panels will never, ever reach the point where they're suitable for anything other than a static image. There's no VA panel fast enough and there will never be. I've been saying that for past 15 years on various forums and was told "just wait, the tech will advance". Well? It didn't. And it surely won't now when OLEDs are slowly approaching "cheap" price zones.

...except that this Pulsar AUO panel (M270DAN10.6) & the PG27AQN are fast enough for 240Hz operation
The INNOCN 27G1S (QHD 240Hz VA) has shown that VA's are capable of achieving good compliance.
I do agree that, from a purely sample & hold perspective, OLED dominates >360Hz market due to it's relatively uniform 0,5 ms G2G RT's.

So far: 360Hz mode in Battlefield 6 looks OK. I enabled NVidia's frame gen on RTX 5070 and I was not annoyed by blur when flying a jet (the mouse is only 1000Hz so this was a better test idea) - but that's far from demanding scenario.
UFOtest came out visibly worse than on my XL2411Z if I'd compare to Benq set to very short strobe time, but it's OK. It was 360Hz, Pulsar ON, browser's ufotest showing it synced correctly to 360 and I'm sure there were no issues.

I'd say it's well within "OK" for me. Not a razor sharp CRT-like, but I can see moving object, not a blurry soup, which is nice For people who never had one of those TN panels with superb low persistence mode or any CRTs, it's what they'll call "crystal clear". For us - just OK.

Pulsar is tested by using games which run below the maximum refresh rate
This means that, TestUFO (which runs FPS=Hz at all times), is incapable of showcasing how Pulsar works in action.
What you should be experiencing is standard ULMB2 @ 360Hz when using the TestUFO pursuit.

To test out Pulsar (VRR+Strobe), you either use SmoothFrog or in-game testing.
Ideally, you'd run GSYNC+VSYNC+Reflex or GSYNC+VSYNC & in-game limiter set to X≤327 (where X is the frame rate limiter value you've chosen)
Why 327? Because Nvidia decided that their autocap works best with that specific value.
You can manually decide what frame rate limiter value you can get away with in your specific games by using RTSS moving (or colored) bar