brownvim wrote: ↑08 May 2026, 18:14
Update is out
I've been using a DP80 cable (3 meters) with my monitor and firmware 1.1.6 fixed the random blackscreens I was having, once in a while. Fortunately, I haven't experienced that anymore.
The improved motion clarity for 100 – 180 FPS range is also noticeable.
supernovae wrote: ↑30 Apr 2026, 09:49
Did the new firmware udpate fixes the 321 Hz refresh rate cap?
And how's the latency when we use in-game limiter set to 357? Do we get the most out of the refresh rate and pulsar technology? Or latency still takes a hit?
Thank you again, I really want to get one but want to be absolutely sure about getting one
The 320/321hz behavior with a single monitor is still there, sadly.
- If you set a 357 fps limit in any game with a single monitor, Pulsar will cap at 320/321hz. You will be out sync and screen tearing will be visible.
- If you enable V-Sync in any game while using a single monitor, Pulsar will cap at 320–321 Hz, and the game will run at 320–321 FPS. This keeps everything in sync and eliminates tearing, but it does come with a noticeable hit to render latency.
- If you disable V-Sync in any game while using a single monitor, Pulsar will still cap at 320–321 Hz, and the game will run unconstrained. You will be out sync and screen tearing will be visible if you are above 320/321 fps.
What’s particularly interesting is that the monitor behaves
as if 321 Hz was its true maximum refresh rate — even though that’s not the case. I can confirm this because the render latency in this scenario is almost identical to what happens when a second monitor is connected and you run V-Sync ON without Reflex nor LLM. But in this case, pulsar will cap itself at 360hz, and the game will run at 360 FPS. If you then enable Reflex, while a second monitor is connected and running, Pulsar will cap at 327hz and and the game will run at 327 FPS, but now you will have the expected improved latency benefit.
So, clearly
there is a problem to be fixed. The strange 320/321hz limit, with a single monitor connected
is a bug and not a feature.
The reason why Reflex and LLM are doing nothing to improve latency for Pulsar when a single monitor is connected
is because Reflex and LLM are trying to impose a 327 fps limit while the monitor caps itself
as if 321 Hz was its "true maximum refresh rate". Therefore unaffecting render latency, because the fps limit is OVER the refresh rate limit Pulsar imposes when a single monitor is connected.
The moment you connect a second monitor, Pulsar behaves normally. V-Sync behaves normally. Reflex and LLM behave normally.
- The monitor max refresh rate will be 360hz.
- Enabling V-Sync without Reflex or LLM will cap the game at 360fps. With the expected latency hit for that sync.
- Enabling Reflex or LLM then, will sync the refresh rate and ingame fps to 327, and you will have the expected better latency.
As for how I've been using Pulsar without a second monitor:
Vsync OFF + Reflex OFF + LLM OFF + RTSS Async cap to 300/310 = No tearing + good latency + smooth frametimes.
As for how I've been using Pulsar with a second monitor:
Vsync OFF + Reflex OFF + LLM OFF + RTSS Async cap to 340/350 = No tearing + good latency + smooth frametimes.
I find that Pulsar doesn't need V-Sync, Reflex nor LLM at all, as long as your ingame FPS don't go over its maximum refresh rate, it will maintain sync. That is why setting any FPS cap below the max refresh rate is the simplest and most effective way, latency wise, to use Pulsar right now. I personally like RTSS Async because it has the smoothest framegraph if your performance is comfortably above target.