NVIDIA G-Sync Pulsar monitor - Asus ROG Strix XG27AQNGV

[Angel Soler]

3000px/sec looks clear to me at 60hz on the ULMB2 mode, at 18 PW. 0 trails or crosstalk.

I forgot to clarify, I was commenting for higher hz/pulsar modes since I'm comparing to my CRT@120hz. The comments about resolution still apply though even for the 60hz mode. CRT can remain clear to the point that the time for my brain to react and my eyes to physically track are the bottleneck. We aren't quite at that point for higher resolutions, however I still consider the 60hz mode to be very good if not the best 60hz motion on a flat panel money can buy currently.

How good the 60hz mode is for someone depends on usecase alot. 60hz locked content on consoles I feel makes the ULMB mode much more appealing as the massive clarity gains probably offset the 10ms lag for most people. However for PC, even on 60hz locked content you have to eat lag for giving up VRR/higher hz and then you have to add the strobe lag, so it's more like +20ms which is way too much for me personally. The lag difference gets worse when comparing games that do not have locked framerates and can be played higher into the VRR range.

Anything higher than that (3840px/sec) is just too fast to track easily.

7860px/sec looks funny because its so fast it looks like its going in slow motion.

I find it's much easier to eyetrack faster speeds if you reduce the amount of UFOs by increasing separation as that's more like eyetracking a singular target ingame. The link below spaces them 2560px apart so there should only be one on screen at a time with 1440p resolution. I feel I already eyetrack much faster than 3840 when whipping a camera and lining up a target in first person games. Mind you that's at higher hz, but even at 60 I can eyetrack 4000px/sec and the text is only really legible at 10PW.

https://testufo.com/ghosting#separation=2560&pps=4000

Edgintheledge, I think the delay is probably even higher on consoles.
With strobing enabled and PW set to 30, I measured about 25 ms of lag with Leo Bodnar Test

I agree with you , that it is the best 60 Hz mode I have ever seen on a display that is not a CRT .
That is why it is such a shame that it has that amount of lag. If it only had input lag somewhere around one frame, roughly 16 ms, like the ViewSonic XG2431, it would be the ultimate display for consoles.

If future updates manage to reduce that lag, I would buy the monitor again without hesitation.

[pgz]

I'm new to pulsar montiors. Do you need to lock your ingame framerate to 360fps or 359fps? for the technology to work properly? What exactly happens if you have pulsar running, but your framerate is higher than 360fps? Does Nvidia provide an article how to properly use a pulsar monitor?

[RealNC]

I'm new to pulsar montiors. Do you need to lock your ingame framerate to 360fps or 359fps? for the technology to work properly? What exactly happens if you have pulsar running, but your framerate is higher than 360fps? Does Nvidia provide an article how to properly use a pulsar monitor?

You should follow the g-sync recommendations. And the nvidia driver I believe does the correct thing if you enable vsync and Reflex (or in games that don't have Reflex if you enable "Ultra" low-latency mode in the nvidia panel), then it will cap to somewhere around 327FPS.

If you don't enable v-sync and don't cap your FPS, when FPS exceeds refresh rate, pulsing will be 360Hz.

[Nglorius]

Is the ULMB 2 60hz mode on the monitor available and compatible with the Xbox Series X?

[El-Vi-Riachi]

6. The latest issue is after the monitor wakes from sleep, and you launch a game set for fullscreen display, the game will not display. You will instead see a black screen, and the bottom most light strip will blink once. It will repeat this slowly as if it's trying to go into full screen repeatedly. I have to ALT-F4 the game, and then power off the monitor and power it back on. Then full screen games will launch with no issues until the monitor sleeps again.

Hi, I'm new and this is the only place I have found with someone that has had the exact same issue as me with this monitor. I love the monitor but this issue is irritating. I have PC monitor set to sleep after 5 minutes, the PC itself i have set to "never" for sleeping. But once the monitor turns back on I have the same issue as above. I doesn't matter if its a full screen game, windowed fullscreen, it simply goes black but I can hear the sound.

On my second monitor if I hover over the toolbar (I have them showing on both screens) and hover over the application I am running, it will then show the game on the main screen. Its a very odd issue, only solution I found is to do the keyboard shortcut to reset the display drivers. A quick fix maybe but something is not right and I'm wondering if its a firmware issue. Has anything been said of this issue?

[Discorz]

Small update on the ULMB Pulse Width scaling at 60Hz! Maybe someone finds it interesting.

Recent theories and calculations led me to conclusion that Pulse Width setting is controlling backlight scan speed. More precisely, I believe it's doing a standard fixed ~62,5% pulse, scanned at ~2.5-25x or ~150-1500Hz speeds (Pulse Width 100-10). This is stricly for 60Hz mode, other refresh rates work differently!

For 60Hz or 16.7 ms frame that means:

• Scanning a 62.5% pulse at 1x speed results in 10.4 ms MPRT (standard speed example)
• Scanning a 62.5% pulse at 2.5x speed results in 4.2 ms MPRT (PW 100)
• Scanning a 62.5% pulse at 5x speed results in 2.1 ms MPRT (PW 50)
• Scanning a 62.5% pulse at 25x speed results in 0.4 ms MPRT (PW 10)

It closely aligns with MPRT indicator measurements from RTINGS pursuit shots, with previous gen ULMB scaling, with slow-mo footage, with TFTCentral's oscillographs, and with theory.

Same goes for brightness, for simplicity, roughly for ~2000 nits tall pulse that it uses:

• Scanning a 62.5% pulse at 1x speed results in 1250 nits (standard speed example)
• Scanning a 62.5% pulse at 2.5x speed results in 500 nits (PW 100)
• Scanning a 62.5% pulse at 5x speed results in 250 nits (PW 50)
• Scanning a 62.5% pulse at 25x speed results in 50 nits (PW 10)

It closely aligns with reviewers measurements and theory.

If anyone needs formulas, these are the ones I was going with:

• Scan Speed Factor = 250 / Pulse Width Setting → e.g. 250 / 30 = 8.3x
  Scan Speed Equivalent = Refresh Rate × Scan Speed Factor → e.g. 60 × 8.3 = 500Hz
• MPRT = Frame Time × Duty Cycle × (1/Scan Speed Factor) → e.g. (1/60) × 0.625 × (1/8.3) = 1.25 ms
• Brightness = Pulse Height × Duty Cycle × (1/ Scan Speed Factor) → e.g. 2000 × 0.625 × (1/8.3) = 150 nits

There might be some minor variations in calculated vs measured results, I believe due to light dispersion and other factors.

[brownvim]

Small update on the ULMB Pulse Width scaling at 60Hz! Maybe someone finds it interesting.

If NVIDIA used the same scanning method for 120/240/360 Hz ULMB2 modes what would the numbers look like? I would be interested to see the perceveid hz at different brightness and pulse width settings if they actually fixed the ULMB2 modfes at 120hz+

[edgintheledge]

Recent theories and calculations led me to conclusion that Pulse Width setting is controlling backlight scan speed. More precisely, I believe it's doing a standard fixed ~62,5% pulse, scanned at ~2.5-25x or ~150-1500Hz speeds (Pulse Width 100-10). This is stricly for 60Hz mode, other refresh rates work differently!

Idk if any of my posts were part of the theory crafting but it's nice to know I was on the right track with what we know so far. I was trying to describe this behavior on this post...

Seems like all roads actually point toward the 60hz mode using a sort of QFT that dynamically adjusts to a higher ratio/scanout speed as you lower the pw. At pw100 the speed is somewhere between 80-120hz and it gets progressively faster (less skew) until it either becomes a global strobe at the lowest pw settings, or is scanning top to bottom so fast that it is effectively a global strobe under the scrutiny of ldat style lag testing.

But I accidentally used terms the terms QFT and scanout speed without clarifying that I meant only the backlight was changing speed and not the pixels. It also looks like I might have been slightly off on the speed of PW100 but hey we can't win em all.

[RealNC]

Is the ULMB 2 60hz mode on the monitor available and compatible with the Xbox Series X?

From what I've seen in discussions, that mode is compatible with everything. Consoles, Blu-ray players, upscalers (retrotink and whatnot,) everything. If it outputs a 60Hz signal, it should work with it.

[pipikiki]

Sorry to interrupt this thread, but do you guys think that ultrawide versions with G-Sync pulsar will appear in the near future?