This is a great update
The only thing left for me now is an update to ULMB 2 at 60 Hz and a fix for the input lag.
Once that happens, I’ll buy the monitor again without hesitation.
I'd be curious to know whether the “reduced input lag for 240 Hz Pulsar” change applies only when the monitor is explicitly set to 240 Hz mode, or whether it also applies when a 360 Hz Pulsar monitor is left in 360 Hz mode but running at around 240 FPS under VRR.
Who is responsible for the software of these monitors? No vivid pixel, sharpening, dynamic crosshair, no option to save or load a profile, really bare bones even compared to cheaper Asus monitors, even the 25 inch mode is 24.9 inches, it's basically copy paste osd from my old pg27aqn, with 60hz ulmb2 and pulsar in the menu, would be cool to have a dedicated 24.5 inch, 24.135 inch, 24, hell even 26.5 like all the current oleds (same as there Asus and other current esports displays) instead of using sre and cru as a work around with a custom non scaled resolutionManuelG_NVIDIA wrote: ↑02 Jul 2026, 13:35Could you provide additional details on how you are reproducing this issue?
- When the issue occurs, does only the display enter sleep mode, or does the entire PC also go to sleep?
- Are any additional monitors connected to your RTX 4080?
- Have you changed any NVIDIA Control Panel or NVIDIA App settings from their default values that could affect display behavior (for example, custom color settings, power management, or other display-related settings)?
- Do you power off the monitor when not in use, or do you leave it in sleep mode?
- Approximately how long does the display need to remain in sleep mode before the issue can be reproduced after waking it?
- Are you currently using the latest NVIDIA driver (610.62)?
- Are there any other steps or conditions that consistently help reproduce the issue?
Yeah in game its hard to spot even when looking for it, non issue.edgintheledge wrote: ↑03 Jul 2026, 05:35I took a stab at a 1920px/sec 120hz crosstalk test as well. (30fps video @ 1/30sec as usual)
Do note that the slightly dark vertical band near the center is due to the phone's rolling shutter (shot vertically so shutter sweeps horizontally across the screen and presumably caused the vertical band). I tried to capture as much detail, but you'd really need a camera on a rail capturing photos rather than video that compresses tiny details alot more, but this should give an idea of how much I was nitpicking every last detail when it's basically a nonissue in real use.
Displayninja done a good review with great pursuit shots here: https://www.displayninja.com/msi-mpg-272qrf-x36-review/


Calling it global flash just because the backlight rolls extra fast is indeed confusing. Why mix the two terms?edgintheledge wrote: ↑02 Jul 2026, 06:05They called it "global flash" in the patchnotes so I just repeated it, but that mightve lead to confusion... sorry! It is the same behavior as the 60hz mode. I think they just call it global flash because at the lowest PW it basically is for both 60 and 120
brownvim wrote: ↑02 Jul 2026, 11:38This help? 1920 pixels per second, PW100, 120hz.
https://youtu.be/WcBL8boY_mQ
That will do. Brownvim used PW 100, what did u use?edgintheledge wrote: ↑03 Jul 2026, 05:35I took a stab at a 1920px/sec 120hz crosstalk test as well. (30fps video @ 1/30sec as usual)
download/file.php?id=7144
If 120Hz method is identical to 60Hz, u can use the previously mentioned formula to calculate MPRT:
Absurdly good implementation.brownvim wrote: ↑03 Jul 2026, 06:53Displayninja done a good review with great pursuit shots here: https://www.displayninja.com/msi-mpg-272qrf-x36-review/
--snip--