Blur Busters Forums

liquidshadowfox wrote: ↑

13 Mar 2026, 10:51

Argus wrote: ↑

13 Mar 2026, 10:18

Has anyone managed to update their Acer model? I've tried 2 different PCs, several cables, different browsers, etc. yet no matter what I do, the website keeps saying no compatible devices found. Followed all the instructions perfectly yet nothing is working.

You did plug in the monitor to the PC through the micro usb port on it and put it into firmware update mode through the monitor OSD right? it's not the default usb connection for the usb hub on the monitor, you have to use the micro usb port on the monitor.

Oh...my monitor didn't come with a micro usb cable...do I have to buy one separately?

Discorz wrote: ↑

30 Jan 2026, 03:04

I just noticed something! Based on the oscillographs MUB provided, the main pulse width is unproportionally narrower at the bottom end and wider at the top end of the range. That means pulse width is not a fixed 25%. I measured them manually, then transferred the findings to one of my MPRT charts to see how it scales over the range. It's a less steep straight line that intersects with advertised 25% line at 120 fps. So it still scales linearly, just not in a way we are used to. After some rounding up this is what I got:

• 100 fps * 23.8% = ~2.4 ms
• 120 fps * 25% = ~2.1 ms
• 144 fps * 26.5% = ~1.8 ms
• 170 fps * 28.1% = ~1.7 ms
• 240 fps * 32.5% = ~1.4 ms
• 330 fps * 38.1% = ~1.2 ms
• 360 fps * 40% = ~1.1 ms

Interesting behavior! Not sure if this is intentional or some limitations are at question. Also, my findings don't fully correspond with their "Over 1000 Hz Effective Motion Clarity" claim. However it does go beyond "quadruple motion clarity" below 120 fps.

The chart allowed me to visualize a shortcut formula for approximate Pulsar MPRT target (main pulse):

• MPRT = (1000/frame rate)*0.175 + 0.625

For now formula works for 360Hz input and VRR frames below. It’s still unclear how Pulsar scales across different input frequencies, or how it behaves with VRR off (ULMB 2). Also beware of the LFC at <90 fps. Things might change for bottom range if they introduce algorithms in firmware update.


Pulsar MPRT 2026.png


MUB Pulsar 98 Hz fps

MUB Pulsar 170 Hz fps.jpg


MUB Pulsar 239 Hz fps

MUB Pulsar 330 Hz fps.jpg

Did these measurements change after the update? I still feel like higher FPS has less profound benefits from pulsar than lower refreshes do for some reason. It's like their algorithm scales back pulse width the higher your FPS is rather than trying to keep it constant. I start noticing pulsar flicker below 90 hz or so, starts to bother me around 80 hz but I can see it looks clearer at lower refreshes than higher ones for some reason. Feels like nvidia might need at least 1 or 2 more updates to get this monitor where it should be. I assume there's another update coming since it was said earlier that 48 hz support was coming eventually (I hope 60 hz pulsar does too since there's a lot of 60 fps locked games).

Argus wrote: ↑

13 Mar 2026, 11:40

liquidshadowfox wrote: ↑

13 Mar 2026, 10:51

Argus wrote: ↑

13 Mar 2026, 10:18

Has anyone managed to update their Acer model? I've tried 2 different PCs, several cables, different browsers, etc. yet no matter what I do, the website keeps saying no compatible devices found. Followed all the instructions perfectly yet nothing is working.

You did plug in the monitor to the PC through the micro usb port on it and put it into firmware update mode through the monitor OSD right? it's not the default usb connection for the usb hub on the monitor, you have to use the micro usb port on the monitor.

Oh...my monitor didn't come with a micro usb cable...do I have to buy one separately?

Yes sir, you need your own cable for this otherwise you cannot update. I found it odd that nvidia didn't include one in the box.

Just tried it with my PS5 and Switch 2, it looks amazing, 60fps is great again.

Even with the pulse width at 100 which is max brightness, it blows away the motion clarity on my OLED, without sacrificing any brightness at all. Going down the range to 10 (lowest) its a massive hit to brightness but it does look less blurry. I will test brightness on PC and report back.

You can do ULMB2 on 120hz mode too on the PS5 but I don't have any games with a locked 120fps to test. They all run in VRR at around 90fps but VRR not supported in conjunction with ULMB2 so the game just doesn't display right. Frames and pulse are out of sync.

brownvim wrote: ↑

13 Mar 2026, 12:57

You can do ULMB2 on 120hz mode too on the PS5 but I don't have any games with a locked 120fps to test. They all run in VRR at around 90fps but VRR not supported in conjunction with ULMB2 so the game just doesn't display right. Frames and pulse are out of sync.

Can you adjust the pulse width on consoles in the 120Hz mode?
It'd be great if you could measure the brightness on PW=100 & PW=10 setting.

kyube wrote: ↑

13 Mar 2026, 13:00

brownvim wrote: ↑

13 Mar 2026, 12:57

You can do ULMB2 on 120hz mode too on the PS5 but I don't have any games with a locked 120fps to test. They all run in VRR at around 90fps but VRR not supported in conjunction with ULMB2 so the game just doesn't display right. Frames and pulse are out of sync.

Can you adjust the pulse width on consoles in the 120Hz mode?
It'd be great if you could measure the brightness on PW=100 & PW=10 setting.

Yes you can adjust pulse width in 120hz mode, so its good to go for a locked 120fps game, but they are rare on console.

Brightness measurements on fullscreen white:

Pulse Width - Nits
100 - 524
90 - 472
80 - 420
70 - 369
60 - 317
50 - 265
40 - 212
30 - 160
20 - 106
10 - 54

mawi wrote: ↑

13 Mar 2026, 09:44

passballtotucker wrote: ↑

13 Mar 2026, 09:21

brownvim wrote: ↑

13 Mar 2026, 02:14

Added 60 FPS ULMB mode with adjustable duty cycle

Long shot but does this work through HDMI for consoles?

Yes it does! Switch 2 looks fantastic with 60fps games. You just need an hdmi audio extractor or compatible dac.

Oh that is big news... Ok Switch is Nvidia as well but as far as I understood this was not working with nvidia hardware outside of Windows. I dont think the Switch is recognizing this as a pulsar display so it seems like the display itself deals with the 60hz signal and strobes it as it should be. That is amazing!
So 3.5mm audio output throuth display is not working?

Audio does work through the 3.5 output of the display. My DAC doesn't support analog inputs so I need an HDMI extractor instead.

The firmware update has broken the Auto Switch Input for me on my Acer Predator, anyone else had this issue?

When I turn on my Switch 2 or PS5 Pro it doesn't automatically change source. It worked fine before the firmware update.

Also noticed the ports are labelled HDMI 1 (2.1) and HDMI 2 (2.1) on the OSD, either an error or they may add full support.

brownvim wrote: ↑

13 Mar 2026, 13:17

Yes you can adjust pulse width in 120hz mode, so its good to go for a locked 120fps game, but they are rare on console.

That's not necessarily an issue per say.
One can just 'cope' with the phase-shift / aliasing artifacting of the refresh rate & frame rate mismatch.

brownvim wrote: ↑

13 Mar 2026, 13:17

Brightness measurements on fullscreen white:
Pulse Width - Nits
100 - 524
90 - 472
80 - 420
70 - 369
60 - 317
50 - 265
40 - 212
30 - 160
20 - 106
10 - 54

Note: This below is a theory, exact numbers are likely going to be slightly different depending on external tool used and/or a few other variables
There's a heavy assumption at hand here that this 60Hz update translates onto every refresh rate setting, but that may not be the case at all.

Based on these comments, I somewhat believe none of this below applies at all....

PW=20 → 5,3% – 10,6% PW (2000–1000 cd/m²)
PW=10 → 2,7% – 5,4% PW (depending on whether we're talking about 2000–1000 cd/m² voltage boosting; I doubt that it's outside this amplitude range)
If this behavior, assumingly, translates onto every refresh rate setting, we're talking such ULMB2 behavior:
Worst-case assumption
PW=5.4% (aka PW=10 in OSD)
60Hz (16,667 ms) @ 0,900018 ms strobe On period @ 54cd/m²
120Hz (8,333 ms) @ 0,449982 ms strobe On period @ 54cd/m²
240Hz (4,1667 ms) @ 0,22500018 ms strobe On period @ 54cd/m²
360Hz (2,7778 ms) @ 0,15000012 ms strobe On period @ 54cd/m²

Which would put it roughly on-par with the ASUS PG27AQN, while having a QD-based backlight, a rolling scan implementation & allowing single-strobe fixed refresh rate 60Hz.
Very good results, if above theory is true.
One of a kind product on the market, in terms of fixed refresh rate backlight strobing capabilities.
This would also imply that the 120–360Hz refresh rate range (when using ULMB2) is CRT-like in terms of total achievable eye-tracked motion performance.

Also noticed the ports are labelled HDMI 1 (2.1) and HDMI 2 (2.1) on the OSD, either an error or they may add full support.

Could you please verify whether you can do QHD@360Hz over the HDMI port on PC? Do a screenshot and post it here.
This would be monumental, if Nvidia listened to my request.

It only does 120hz on HDMI and Pulsar is disabled so no changes there.