Blur Busters Forums

This questions already might have been answered, but I couldn't find it due to the insane amount of messages in this thread:

Does ULMB2 at 60 and 120 Hz work with HDR or only in SDR?

Baron of Sun wrote: ↑

01 Oct 2026, 02:49

Does ULMB2 at 60 and 120 Hz work with HDR or only in SDR?

Yes, ULMB2 with still less than 60Hz works both SDR and HDR.

Is there anyone who got a monitor without it any backlight bleeding whatsoever? I know that IPS glow is normal and you can’t avoid that, but backlight bleeding is a lottery again.

This is my monitor and there is some bleeding at the bottom. Not the end of the world to be fair, but still annoys me.

hammelgammler wrote: ↑

01 Oct 2026, 11:11

Is there anyone who got a monitor without it any backlight bleeding whatsoever? I know that IPS glow is normal and you can’t avoid that, but backlight bleeding is a lottery again.

This is my monitor and there is some bleeding at the bottom. Not the end of the world to be fair, but still annoys me.

IMG_5645.jpeg

We don't need any worry because new LED backlight for replacement is cheap, fortunately.

kyube wrote: ↑

28 Sep 2026, 03:02

Chief Blur Buster wrote: ↑

27 Sep 2026, 14:43

Also, most LCD VR headsets now outperform a FW900 CRT, at least for refresh rates that the VR headset supports.

Has anyone done any pursuit photographs on these models? Surely, the G2G RT's @ 120-144Hz result in some form of crosstalk at these low pulse on times?

I run at 90 as a good compromise, both on Quest 2 and Quest 3S, as I get better resolution and fewer stutters that way.

There is zero crosstalk at 90 Hz on both Quest headsets when I run testufo.com/crosstalk in the in-headset Chromium-based web browser. Truly zero. No phosphor ghosts, no crosstalk. I briefly tried 120 and did not notice crosstalk, at least for a warmed-up headset that had been running for at least 30 minutes (hot LCDs are faster performing).

It might be possible that a small part of the GtG heatmap doesn't fit in the VBI, but all the colors used by the Crosstalk test did fit in the VBI, showing nothing at top/center/bottom. No afterimages. None. At least during 60-90Hz range.

The older Quest 2 was actually one of the benchmarks I tuned XG2431 towards. The Quest 2 seems to do a better job, thanks to the giant Facebook budget spent on the tuning. It clearly does go crosstalk-free at a higher Hz than XG2431 can. It utilizes a lot of tricks including superior OD LUTs and larger blanking interval.

So, on Hz-vs-resolution priorities. The nice thing about impulsed displays is you can maintain motion clarity at lower Hz, so the ROI sometimes goes to the "BlurryVision" spatials -- I wanted to make my Quest headsets sharper at rendering.

I often use Quest Game Optimizer to get more resolution (true 4K rendering) to get 3x sharpness at 72fps 72Hz. The flicker is worse, but the motion clarity is superlative. Not often, but there are some games that will tolerate a 200-300% extra resolution forced into the game on the mobile CPU/GPU built into Quest headsets.

QGO will overclock the CPU/GPU if you want, but be careful -- too much overclock and it will thermally throttle. So you need to tweak a balance, depending on if the game wants more CPU or more GPU, etc. If you do this, you will also want to enable mobile spacewarp, since that helps de-stutter some of the superscaling stutters.

What annoys me is Quest 3S does not do 60Hz anymore like Quest 2 can. Quest 2 works great with emulators at 60fps 60Hz. Whether a virtual arcade cabinet you stand in front of, or whether you cast it from your PC, or whether you sideload an Android emulator .apk.

Remember, you need third party utilities to access custom refresh rates on a Quest (whether OGO or SideQuest or other), all of which requires Developer Mode and sideloading at least a little something, to force a specific Hz.

kyube wrote: ↑

28 Sep 2026, 03:02

This implies it's doing ~4444,44 cd/m² of voltage boosting, which would be the highest I've seen any consumer LCD do.
I'm surprised that it doesn't burn down in an instant

1. Study Talbot-Plateau Theorem. Learn about it before replying.
2. CRTs did 30,000 nits at the beam spot.

That said, you definitely want to strobe far above flicker fusion threshold. Also, I don't think it strobes that bright anyway in real life. I even wonder if the 180 may even be pre-strobe. The nice thing is that your eyes adjust to the dark pretty fast in a VR headset, and the screen doesn't need to be nearly as bright.

When I got these headsets, they were incredibly cheap (under $300), so they are quite handy as general purpose motion-blur-reduced displays. You do want a comfortable replacement headset strap, as it is otherwise uncomfortable for more than an hour. A used Quest 2 is among the best 60 Hz LCD strober money can buy on the market currently, but it's unconventional compared to the XG2431.

kyube wrote: ↑

28 Sep 2026, 03:02

That's all great in theory, but the "merely" part is exactly where >95% of implementations on the market falter.

That's true. I was speaking in terms of theoreticals. What is happening is that the LCD stops becoming the limiting factor, and now it's the backlight's turn to shine.

nuninho1980 wrote: ↑

01 Oct 2026, 09:08

Baron of Sun wrote: ↑

01 Oct 2026, 02:49

Does ULMB2 at 60 and 120 Hz work with HDR or only in SDR?

Yes, ULMB2 with still less than 60Hz works both SDR and HDR.

Thanks for the response. That's good news (besides the fact that 120 to 480 nits is not really good HDR, but it's good in terms of compatibility).

hammelgammler wrote: ↑

01 Oct 2026, 11:11

Is there anyone who got a monitor without it any backlight bleeding whatsoever? I know that IPS glow is normal and you can’t avoid that, but backlight bleeding is a lottery again.

This is my monitor and there is some bleeding at the bottom. Not the end of the world to be fair, but still annoys me.

IMG_5645.jpeg

I just got mine.Mine has some bleeding on the top side so the opposite yours.


Your picture as an example.I marked where mine are.

Make sure to disable dark boost.I think this setting makes it worst.
It's honestly not visible in day to day use.Only noticable when the monitor is starting up and shutting down because there's no actual image being shown.

Hi everyone,

I’ve been reading through this thread and I’d really appreciate some advice from anyone who has tested the latest firmware extensively.

I’m using the ASUS XG27AQNGV with the latest monitor firmware already installed, an RTX 5070 Ti, and I only play Warzone at around 190–245 FPS using DLSS.

For this specific FPS range, what would you consider the best practical setup today for motion clarity, frame pacing and low latency?

Would you leave Windows/NVCP at 360 Hz and use G-SYNC Pulsar with an FPS cap somewhere around 190–220 FPS, or is there any real advantage in switching the display to 240 Hz when the game normally runs between roughly 190 and 245 FPS?

A few additional questions specifically for this setup:

- With NVIDIA Reflex available in Warzone, would you use Reflex On or On + Boost with Pulsar?

- For 190–245 FPS, would you use RTSS, the Warzone in-game limiter, or leave the game uncapped within the VRR range?

- If RTSS is preferable, which limiting method currently works best with Pulsar: the normal limiter, Front Edge Sync / frame-start presentation, Async, or something else?

- Where would you personally place the FPS cap for this performance range?

- Is there currently a specific NVIDIA driver version that works particularly well with G-SYNC Pulsar for frame pacing, motion clarity and stability, or should I simply use the latest driver?

- For SDR gaming, is RGB Full / 10 bpc / gamma 2.2 still the preferred output setup, and would you use sRGB or Wide Gamut specifically for gaming?

I already have G-SYNC and NVCP V-Sync enabled as required for Pulsar, so I’m mainly interested in the remaining settings that can actually affect Pulsar behaviour.

My priority is Warzone motion clarity during fast camera movement and enemy tracking, while keeping frame pacing consistent and latency as low as possible.

Thanks in advance for any advice.

.

fanet0s wrote: ↑

03 Oct 2026, 05:22

Hi everyone,

I’ve been reading through this thread and I’d really appreciate some advice from anyone who has tested the latest firmware extensively.

I’m using the c with the latest monitor firmware already installed, an RTX 5070 Ti, and I only play Warzone at around 190–245 FPS using DLSS.

For this specific FPS range, what would you consider the best practical setup today for motion clarity, frame pacing and low latency?

Would you leave Windows/NVCP at 360 Hz and use G-SYNC Pulsar with an FPS cap somewhere around 190–220 FPS, or is there any real advantage in switching the display to 240 Hz when the game normally runs between roughly 190 and 245 FPS?

A few additional questions specifically for this setup:

- With NVIDIA Reflex available in Warzone, would you use Reflex On or On + Boost with Pulsar?

- For 190–245 FPS, would you use RTSS, the Warzone in-game limiter, or leave the game uncapped within the VRR range?

- If RTSS is preferable, which limiting method currently works best with Pulsar: the normal limiter, Front Edge Sync / frame-start presentation, Async, or something else?

- Where would you personally place the FPS cap for this performance range?

- Is there currently a specific NVIDIA driver version that works particularly well with G-SYNC Pulsar for frame pacing, motion clarity and stability, or should I simply use the latest driver?

- For SDR gaming, is RGB Full / 10 bpc / gamma 2.2 still the preferred output setup, and would you use sRGB or Wide Gamut specifically for gaming?

I already have G-SYNC and NVCP V-Sync enabled as required for Pulsar, so I’m mainly interested in the remaining settings that can actually affect Pulsar behaviour.

My priority is Warzone motion clarity during fast camera movement and enemy tracking, while keeping frame pacing consistent and latency as low as possible.

Thanks in advance for any advice.

The only reason to drop to 240 Hz is if you don't want to use DSC, it makes no sense otherwise in a competitive game like Warzone. My personal recommendation would be no fps cap at all considering you're basically within the optimal Pulsar range for motion clarity, it is not worth the latency penalty. If you really want to use a frame limiter I lean towards RTSS Reflex limiter or NVCP for competitive games because of the lower latency cost. RTSS Front Edge Sync is king for motion clarity with Pulsar but adds noticeable latency so its a no go for competitive for me. Honestly though, your best bet is to test all of these in game and see which you like best.

V-Sync is not required at all and, in fact, does nothing in your case. Wide Gamut vs SRGB is preference. Reflex On is almost always preferred over On + Boost for frame pacing reasons but Reflex can mess up frame pacing anyways. One tip I can give you is to set Pulsar low fps to 120 for games where you're comfortably averaging 200+ fps and 1% lows are not terrible. Gives a slight motion clarity boost.