NVIDIA G-Sync Pulsar monitor - Asus ROG Strix XG27AQNGV

[Mighty_opf]

"Anyway I believe this update is definitely a must-install to see the full potential these monitors have to offer in motion clarity.
Firmware in the OSD still reports MCM102 but maybe that is a separate thing to Pulsar internally but I don't know for sure."

I performed a reinstallation this morning because I wasn't entirely sure if it had been applied correctly with FW 1.1.6, and I've noticed that it now correctly displays the FW version on the monitor's OSD: MCM103(V1.1.6).

[leave]

I’d like to ask everyone: Is scanline sync required for Front Edge Sync? How does it change things if it’s enabled? Is there an optimal setting?

[liquidshadowfox]

Scanline sync isn't required for front edge sync. Scanline sync is only to be used if you are playing with Vsync off and don't have Gsync/freesync enabled as the point of it is to make the tear line consistently tear at the top or bottom of the screen so you get a low lag solution that removes tearing like Gsync/freesync. This is mostly useful for OLED monitor folks who can't normally use Gsync/freesync because their monitor has VRR flicker (essentially Gsync or freesync causes their oled to flicker when fps changes to rapidly which leads to eye strain and discomfort). Front edge sync is simply a way to change how riva tuner's FPS cap affects frame pacing. In my experience, front edge sync is the mode that has consistently given me the most consistent frame times for gsync pulsar to work properly.

[leave]

Scanline sync isn't required for front edge sync. Scanline sync is only to be used if you are playing with Vsync off and don't have Gsync/freesync enabled as the point of it is to make the tear line consistently tear at the top or bottom of the screen so you get a low lag solution that removes tearing like Gsync/freesync. This is mostly useful for OLED monitor folks who can't normally use Gsync/freesync because their monitor has VRR flicker (essentially Gsync or freesync causes their oled to flicker when fps changes to rapidly which leads to eye strain and discomfort). Front edge sync is simply a way to change how riva tuner's FPS cap affects frame pacing. In my experience, front edge sync is the mode that has consistently given me the most consistent frame times for gsync pulsar to work properly.

I thought I remembered reading that this was required in this forum, but I might have been mistaken. Thank you—that was a big help.

[BLooDS_inc]

Scanline sync isn't required for front edge sync. Scanline sync is only to be used if you are playing with Vsync off and don't have Gsync/freesync enabled as the point of it is to make the tear line consistently tear at the top or bottom of the screen so you get a low lag solution that removes tearing like Gsync/freesync. This is mostly useful for OLED monitor folks who can't normally use Gsync/freesync because their monitor has VRR flicker (essentially Gsync or freesync causes their oled to flicker when fps changes to rapidly which leads to eye strain and discomfort). Front edge sync is simply a way to change how riva tuner's FPS cap affects frame pacing. In my experience, front edge sync is the mode that has consistently given me the most consistent frame times for gsync pulsar to work properly.

And remember, all's rivatuner sync fps caps give u a 1 frame latency, only reflex cap give u lowest possible latency within rivatuner framecap

[liquidshadowfox]

Scanline sync isn't required for front edge sync. Scanline sync is only to be used if you are playing with Vsync off and don't have Gsync/freesync enabled as the point of it is to make the tear line consistently tear at the top or bottom of the screen so you get a low lag solution that removes tearing like Gsync/freesync. This is mostly useful for OLED monitor folks who can't normally use Gsync/freesync because their monitor has VRR flicker (essentially Gsync or freesync causes their oled to flicker when fps changes to rapidly which leads to eye strain and discomfort). Front edge sync is simply a way to change how riva tuner's FPS cap affects frame pacing. In my experience, front edge sync is the mode that has consistently given me the most consistent frame times for gsync pulsar to work properly.

And remember, all's rivatuner sync fps caps give u a 1 frame latency, only reflex cap give u lowest possible latency within rivatuner framecap

Sure, but reflex in my experience with pulsar so far has been a dice roll where I need a nat 20 before it works perfectly and I see consistent motion clarity across the screen. I'll take 1 frame of latency for perfect Gsync pulsar any day of the week with fps > 90. Still much less input lag than frame gen (even with reflex enabled there) and everything looks smooth and crispy like a fresh morning toast.

[kitabatake_radeka]

Is PULSAR still limited to 120, 240 and 360 Hz refresh rates; or is it possible to use other rates as well now with the update 1.1.6?

[BLooDS_inc]

Is PULSAR still limited to 120, 240 and 360 Hz refresh rates; or is it possible to use other rates as well now with the update 1.1.6?

I think u can use 360hz and lock fps at whatever u want >75 and <347, and it's gonna work like intended

[tsarri]

Is there any reason for 360htz pulsar users to be upgrading the firmware from the factory default? 1.1.6 mentions Improved operations for 100-180fps range, is this simply fixing the issues from the last firmware update or is there a noticeable improvement from the default firmware performance at that range?

[liquidshadowfox]

Is there any reason for 360htz pulsar users to be upgrading the firmware from the factory default? 1.1.6 mentions Improved operations for 100-180fps range, is this simply fixing the issues from the last firmware update or is there a noticeable improvement from the default firmware performance?

Default firmware has the following problems
1. Gsync pulsar disengages too often so it's too strict on frame times
2. Gsync pulsar has heavy double images below 90 fps which sometimes ruins clarity at higher refresh rates if your fps dips too much within that range
3. No ULMB 60 hz mode is available
4. Some issues with multi monitor setups.
5. Weird bug where LFC (low frame rate compensation) was activating despite not being needed on this mediatek Gsync module which ruins some lower fps ranges.

I highly recommend the latest update, it fixes a LOT of issues and now gsync pulsar works across the advertised refresh range correctly.