NVIDIA G-Sync Pulsar monitor - Asus ROG Strix XG27AQNGV

[whitespider999]

but i don't think nv engineers are taking requests. It would certainly be something that I would request.

It has become really quiet since 1.1.10. Two more edits of the changeblog post regarding the black screen issue and 320 fps bug. But other than announced both bugs were not fixed with yesterdays nv driver update. Also no more forecast to whats next on a possible 1.1.11 which always came quick after the releases of 1.1.6 and 1.1.8.
Its been 9 months now and of course the day will come when no more fw updates will arrive for these models. My gut feeling is we might see one more fw... but not too soon.
Hopefully they keep optimizing things on driver side which affect pulsar users more than others like a dynamic frame cap.

Well, i'm no expert in NV thinking. But they seem pretty invested in this judging from the past efforts. It seems like it's come pretty far. The original gsync module took a while to become more mainstream (i even remember a few forum posts suggesting it would not take off, or it's for a niche crowd that only care about no screen tearing). One thing I will say about NV is they are pretty forward looking, they tend to understand what a bit of dedication and potential will result in, and it usually does result in those things. Not immediately, over many years. After using pulsar for a while now, i can confidently say it's outright scary going back to what i was using before (4k qd-oled, 240hz).

[mawi]

Well, i'm no expert in NV thinking. But they seem pretty invested in this judging from the past efforts. It seems like it's come pretty far. The original gsync module took a while to become more mainstream (i even remember a few forum posts suggesting it would not take off, or it's for a niche crowd that only care about no screen tearing). One thing I will say about NV is they are pretty forward looking, they tend to understand what a bit of dedication and potential will result in, and it usually does result in those things. Not immediately, over many years. After using pulsar for a while now, i can confidently say it's outright scary going back to what i was using before (4k qd-oled, 240hz).

I agree. I wasnt saying I am disappointed or anything. I am really happy with my monitor and with the latest firmware. The fact that non of the two advertised fixes were actually present yesterday without any information gave me the idea they might slow it down a bit.

As you said. There is no way back. Unfortunately you get used to it very quickly and the "wow" effect turns more into an "ewww" effect when looking at other displays.
Lets hope they just have a break, maybe some vacation time and then announce some new ideas and features, either driver wise or fw wise.

In the meantime i keep playing goldeneye xbla, perfect dark, twilight princess (dusklight) and wace race 64 recompile with shiny new water animations at 240 fps with unseen clarity. Its just amazing. All these new pc port projects popping up on a daily basis look so amazing on a pulsar display. This is just what pulsar is made for. These games were all played on CRTs in the past... and now they return at the perfect timing so motion blur is not ruining anything

[liquidshadowfox]

I think more people should post on the nvidia forum post asking for pulsar ultra and extreme modes to be a last hail marry. Am I happy with the monitor as is firmware wise? Yes but I'd love to see at least 1 more pulsar "Extreme" mode where it's half the duty cycle across the board for 1/2 the max brightness (I currently think it gets too bright without adaptive brightness enabled so I know the headroom is DEF there). I'd even take a 3/4 of current max brightness in exchange for a lower duty cycle!

[kyube]

but i don't think nv engineers are taking requests. It would certainly be something that I would request.

I'm somewhat certain that my constant, constructive complaining here about fixed refresh rate strobing being bad on launch was seen and ULMB2 was "unleashed" afterwards.
Let's hope they'll listen to my Pulsar request now

A more aggressive pulse on time x refresh rate curve would also indirectly dampen (perhaps even eliminate) out the "improper frame pacing / large frametime jitter leads to more blur" complaint that users have here.
If the effective motion clarity eclipses the necessary pixel speed, then it doesn't matter what the frametime value jitters to, you won't physically see/feel it.
With the current 20-41,5% curve that Pulsar comes with, every jitter is seen.