NVIDIA G-Sync Pulsar monitor - Asus ROG Strix XG27AQNGV

[MSIfanboy]

they dont even seem to be in the same clarity realm, if you are a no crosstalk enjoyer who plays only aim trainers on static single colored grey and cyan backgrounds, you are gonna love this monitor

[radeko]

Have you read the instructions on how to use the MPRT indicator test?
https://testufo.com/mprt#pps=240&number=decimal

Instructions are in the text description.

Instructions: Your MPRT is the pair of vertical bars that touches edge-to-edge without overlap or gap. If all lines has a gap, please increase Pixels Per Sec.

Set Values Always decimal.

To understand how the test works, set your monitor to 60Hz and the test speed to 240 pixels per second. moving from left to righ

The length of one frame. the MPRT value
1000ms/60hz= 16,66ms per 1 hz MPRT value
1000ms/120hz= 8,33ms
1000ms/240hz= 4,16ms
1000ms/360hz=2,77ms

Look at pairs of vertical bars , Pair with number 20.8 they should have a visible gap between them, pair with numer 16.7 should touch edge-to-edge. You look at the first pair that touches, looking from right to left. Whichever pair touches first corresponds to the MPRT value.

Mathematical operations can be performed in a similar manner

1000ms /16,66ms = 60hz
1000ms / 8,33ms= 120hz
1000ms / 4,16ms =240hz
1000ms / 2,77ms = 360hz

Pulsar mode has a duty cycle of 25%, so you have to multiply/divide by 4 to get the equivalent of the MPRT sample and hold.

120hz + Pulsar = 120hz x 4= 480hz
The length of one frame In Pulsar Mode. MPRT value.
1000ms/480hz = 2,08 ms

So in the UFO TEST MPRT indicator. You should see vertical bars that touches edge-to-edge with about 2ms signed under them
If they touch at 8ms and not 2ms, it means that Pulsar is not working.

ANALOGICALLY
240hz + Pulsar = 240hz x 4= 960hz
The length of one frame In Pulsar Mode. MPRT value.
1000ms/960hz =1,04ms

So in the UFO TEST MPRT indicator. You should see vertical bars that touches edge-to-edge with about 1ms signed under them
If they touch at 4ms and not 1ms, it means that Pulsar is not working.

To sum up, the MPRT indicator test can be used to test the strobe mode of monitors and on this basis, without an oscilloscope, etc., we can check the duty cycle.
We can also test without the strobe. If the value is higher than the calculated value, then the monitor has poor GTG speed.
So the monitor has 400Hz, but these Hz are only on paper because it's physically 240Hz. Just like AOC has been doing lately with IPS displays.

[olain]

Have you read the instructions on how to use the MPRT indicator test?
https://testufo.com/mprt#pps=240&number=decimal

Instructions are in the text description.

Instructions: Your MPRT is the pair of vertical bars that touches edge-to-edge without overlap or gap. If all lines has a gap, please increase Pixels Per Sec.

Set Values Always decimal.

To understand how the test works, set your monitor to 60Hz and the test speed to 240 pixels per second. moving from left to righ

The length of one frame. the MPRT value
1000ms/60hz= 16,66ms per 1 hz MPRT value
1000ms/120hz= 8,33ms
1000ms/240hz= 4,16ms
1000ms/360hz=2,77ms

Look at pairs of vertical bars , Pair with number 20.8 they should have a visible gap between them, pair with numer 16.7 should touch edge-to-edge. You look at the first pair that touches, looking from right to left. Whichever pair touches first corresponds to the MPRT value.

Mathematical operations can be performed in a similar manner

1000ms /16,66ms = 60hz
1000ms / 8,33ms= 120hz
1000ms / 4,16ms =240hz
1000ms / 2,77ms = 360hz

Pulsar mode has a duty cycle of 25%, so you have to multiply/divide by 4 to get the equivalent of the MPRT sample and hold.

120hz + Pulsar = 120hz x 4= 480hz
The length of one frame In Pulsar Mode. MPRT value.
1000ms/480hz = 2,08 ms

So in the UFO TEST MPRT indicator. You should see vertical bars that touches edge-to-edge with about 2ms signed under them
If they touch at 8ms and not 2ms, it means that Pulsar is not working.

ANALOGICALLY
240hz + Pulsar = 240hz x 4= 960hz
The length of one frame In Pulsar Mode. MPRT value.
1000ms/960hz =1,04ms

So in the UFO TEST MPRT indicator. You should see vertical bars that touches edge-to-edge with about 1ms signed under them
If they touch at 4ms and not 1ms, it means that Pulsar is not working.

To sum up, the MPRT indicator test can be used to test the strobe mode of monitors and on this basis, without an oscilloscope, etc., we can check the duty cycle.
We can also test without the strobe. If the value is higher than the calculated value, then the monitor has poor GTG speed.
So the monitor has 400Hz, but these Hz are only on paper because it's physically 240Hz. Just like AOC has been doing lately with IPS displays.

Yeah man, that is really complicated stuff, however I did do your test, and found some success.

I set the display to 60 hz, and 240 PPS, and I could observe that the vertical lines seemed to meet at the 16.7 marker.
I then set the display to 120 hz and kept 240 PPS and I could observe that the vertical lines seemed to meet at the 8.3 marker.
(At 60 and 120 hz, this display has Pulsar disabled FYI.)

Then I set it to 240 hz, and I had to increase PPS to 480, as the calculated 1000ms / 240hz = 4.16 marker wasn't available, lowest value from left was 8.3. This puzzled me, as the dropdown for the PPS said 240 Pixels/Sec - For MPRT >= 4ms, and 4.16 > 4.
However, when I set the PPS to 480, I noticed I could see a clear black void between the two white vertical lines at the 4.2 marker. I then disabled Pulsar, and now the lines were touching edge-to-edge. So yes, Pulsar is working. I also tried @ 960 PPS, and the lines weren't touching at the 2.1 marker. My eyes can't track the vertical lines when the PPS is 1440 or above, so I guess I couldn't do the rest of your test.
Thanks for helping.
I do however, still think something is wrong with my unit, as I should be able to notice a considerable benefit in motion clarity when playing with a frame cap of 120 fps, in the VRR range, when the desktop is set to 360 and Pulsar is enabled. But I can't, I really really can't.
Could be the old tale of the "Emperors New Clothes", of course.

[radeko]

set 120hz and turn pulsar on lines should stick at 2ms. If they touch at 8ms . Pulsar is not working and maybe your model have failure.

[kyube]

Not sure what you are asking, but the 300 hz display I already have, has 2 strobing mode, normal and extreme, with different pulse widths. Only Normal is playable, as Extreme makes the display too dim. Either way, with the normal mode, @ 300 fps you get a 600 hz motion like LCD clarity, which seems just as good as the 280 hz 4.th gen WOLED or this new 360 pulsar monitor.

Make a pursuit photograph of your Acer display @ 120, 240hz & 300hz with both VRB settings each, if possible.
Use these tests:
https://testufo.com/ghosting (1920px/s)
&
https://testufo.com/crosstalk

What I was referring to with KSF/PFS was this topic (red fringing)

BUT my big concern is not so much that I cant see a difference at the high 300+ fps motion, but in _all_ the reviews, it is said that even @ 120 fps, this Pulsar will seem like 360+ FPS motion clarity, however, I cannot see that my self. I see alot of blur @ 120 fps, and its the same with Pulsar disabled. This worries me, and makes me think that something is wrong with my unit.

I do however, still think something is wrong with my unit, as I should be able to notice a considerable benefit in motion clarity when playing with a frame cap of 120 fps, in the VRR range, when the desktop is set to 360 and Pulsar is enabled. But I can't, I really really can't.
Could be the old tale of the "Emperors New Clothes", of course.

You're supposed to be using Displayport.
Use GSYNC+VSYNC+Reflex (or rely on a in-game frame rate limiter)
~120FPS @ ~120Hz in-game should get you ~2,083ms MPRT (“Effective ~480Hz” eye-tracked motion clarity) when Pulsar is enabled.
Pulsar doesn't work when you set your desktop refresh rate to <240Hz (e.g.: 120Hz) or if you use HDMI.

If you swing your mouse fast in-game, you might not perceive a large difference as motion can be in the +900px/s pixel speed range.

[radeko]

Than how use pulsar bellow 240hz? Pulsar was supposed to work from 90hz and after the update from 48hz

[kyube]

Than how use pulsar bellow 240hz? Pulsar was supposed to work from 90hz and after the update from 48hz

G-SYNC PULSAR (VRR+Strobing) only works if:
- a Nvidia dGPU (Turing or newer, DP1.4) is used
- The display's refresh rate is set to ≥240 Hz in Windows
- Pulsar is enabled in the OSD menu.
- G-SYNC is enabled in the NvCPL (make sure to enable V-SYNC in-game or per-profile in NvCpl as an alternative)

From there on, you rely on frame rate limiters or the game's low optimizations.
Whether it's Reflex's autocap, NvLimiterV3 with Reflex, RTSS or the game simply being bound to a particular frame rate target doesn't matter.

ULMB2 (single-strobe PWM, fixed refresh rate backlight strobing) behaves like typical non-VRR displays.

[radeko]

So, I understand this to mean that if the monitor is set to ≥240 hz, but the frame rate drops to 120 fps, the Pulsar will still work. So, you can't test the Pulsar at 120 hz in the UFO test in webbrowser.

[liquidshadowfox]

After some testing with smooth frog, I do see 120 fps very clear but only if the FPS is REALLY consistent, otherwise it'll blur out a bit and not be as clear (I see this in a lot of games that I don't cap using riva with async mode). This monitor has really good motion clarity above 95 fps (below 95 fps with pulsar on there's some crosstalk which I assume is due to the bug they are fixing in the next firmware update). In order to take advantage though, I think it's best to cap the FPS where the frame times are consistent and you have a flat line shown by the riva overlay, otherwise you might get some inconsistencies where it'll momentarily blur our or look "fuzzier" than it should be, that's been my experience so far. Some games you don't have to cap anything and the frame times are consistent enough (variance is very slow, no huge dips) where pulsar works without any extra effort.

[kyube]

So, I understand this to mean that if the monitor is set to ≥240 hz, but the frame rate drops to 120 fps, the Pulsar will ̶s̶t̶i̶l̶l̶ work.

If you strike through the "still" part in your quote above, yes.
Pulsar is a variable refresh rate implementation. It functions within the same set of rules as any other normal variable refresh rate display.

So, you can't test the Pulsar at 120 hz in the UFO test in webbrowser.

You can only use SmoothFrog with a TestUFO photograph to emulate such an synthetic environment.
The alternative is checking out in-game.

Web browsers (& Windows altogether) are always FPS=Hz, therefore VRR doesn't work.