Blur Busters Forums

daviddave1 wrote: ↑

27 May 2026, 16:53

Guys if you play Apex Legends that is capped at 300fps and you manage fps from 240 to 300 ingame so fluctuating fps what are the best settings?

I am about to buy this monitor next week can someone please tell the best settings for Apex Legends with the natural fps cap of 300 fps?

daviddave1 wrote: ↑

30 May 2026, 07:50

I am about to buy this monitor next week can someone please tell the best settings for Apex Legends with the natural fps cap of 300 fps?

You already own a CRT & have the ability to use Nvidia FastSync.
Why would you ever get these, inferior in motion clarity, models?

Mighty_opf wrote: ↑

26 May 2026, 14:22

CriticalHit_NL wrote: ↑

19 May 2026, 15:37

"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).

Interesting, thanks.
I know the update did apply successfully since the 120-180 range is working fine now, was just curious why the firmware version sticked.
Maybe they did an inbetween fix, but not too bothered by it.

mawi wrote: ↑

28 May 2026, 06:09

kitabatake_radeka wrote: ↑

28 May 2026, 06:00

As I alluded to, with older drivers, i.e. the 57x and 58x branch, 360 Hz 10 bit color gives me black screen in fullscreen mode.

Switching to 240 Hz 8 bit color (no DSC), there is no issue.

Interesting. Could it be that with 10bit color and 360 Hz, even RTX50 cards have to use multiple pipelines and run into the same problems as RTX40 cards with 360 Hz 8bit?
In this case... DSC is (again) not the actual problem.

You could try to disable the tiling via registry. With 8-bit color the 360 Hz mode should still be available. With 10-bit it could be gone.

RTX 50-series cards do not share the same limitation as DP 1.4 videocards did with DSC, that means even with DP1.4 monitor and cable you can use DSR / DLDSR (or custom resolution) and not have the same black screen issues as RTX 40-series and older experience.

You can also use 10-bit with VRR/Pulsar with HDR no problem. With DSR 'hacked' to 8K resolution you even get to keep the 360Hz output, I think at 16K it may be 60Hz but that is an exceptionally high resolution not workable in many games.

It runs on all RTX-50 series cards on a single display pipeline even though DSC is still active to compress the image to send it through to the display but the GPU side is well capable enough to handle all the bandwidth required.

So whatever issues you experience on DP 1.4 videocards may disappear using a newer videocard.

You can also see some more in depth explanations here to have an idea what each combination offers:
https://tftcentral.co.uk/articles/loads ... nd-updates

kitabatake_radeka wrote: ↑

29 May 2026, 08:54

To circle back a little bit to my previous question: which driver would you recommend for the firmware 1.1.6 and an 5090 GPU?

I would probably advice to still install the latest one, unless you're experiencing issues you didn't on previous ones which can at times be a bit of a mixed bag between GPU architectures, though recently they have implemented some security updates for the drivers in May so I would still make sure to have atleast that version or newer installed for security.

https://nvidia.custhelp.com/app/answers ... --may-2026

I did have to install the 610.47 driver completely clean because I had issues with GTA V Enhanced not booting due to some strange underlying driver issue which may have been a result of doing multiple GPU driver upgrades in a row without a clean install which caused below crash errors in the launcher error logs:

[DISPLAY] [23800] [gamelaunch] Game exited with code 0xc0000005 (3221225477)

So what I did was wipe 610.47 completely including leftover folders, registry and physx + legacy physx.

Then I reinstalled the previous driver, re-imported my driver profiles with Nvidia App override bypass so I can control DLSS overrides in any game without Nvidia App resetting the driver profiles for those particular games.

The game functioned again afterwards with all my programs open + RTSS overlay.
After that I installed the 610.47 driver over it and install Legacy PhysX without doing a clean install and things are fine again.

Noteworthy, I had some stuttering issues on the Pulsar display in DOOM TDA with the previous few drivers on 3x/4x MFG mode, but that looks to be solved now in 610.47 with maybe the only leftover 'issue' being if you switch from a Legacy native FPGA G-sync monitor to the Pulsar display that 4x MFG may still exhibit some frametime stutters until you retoggle the MFG settings ingame.

Sometimes MFG behaves differently on the old G-sync monitor versus the Pulsar monitor even on different multiplier modes, but the recent updates in the drivers regarding multi-monitor with MFG and V-sync fixes may have contributed to this improved stability.

Only RTX-Remix games like Portal and Half-Life 2 still seem to stutter on 4x MFG mode (2/3x is smooth) making the motion feel like half the smoothness on 4x mode despite higher FPS even on DLSS Ultra Performance on a RTX 5090 which is a bit questionable why this happens when games like Cyberpunk 2077 have zero stutter doing even 6x MFG.

The 610.47 driver has not yet fixed the Stand-by -> wake up for G-sync on the PG279Q essentially deactivating it when woken up but that is to be fixed in the future, Pulsar does not show this problem.

But in short I would probably still go for 610.47, albeit a clean install and re-import your driver profiles if required through Nvidia Inspector.

Mighty_opf wrote: ↑

26 May 2026, 14:22

CriticalHit_NL wrote: ↑

19 May 2026, 15:37

"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).

Interesting, thanks.
I know the update did apply successfully since the 120-180 range is working fine now, was just curious why the firmware version sticked.
Maybe they did an inbetween fix, but not too bothered by it.

mawi wrote: ↑

28 May 2026, 06:09

kitabatake_radeka wrote: ↑

28 May 2026, 06:00

As I alluded to, with older drivers, i.e. the 57x and 58x branch, 360 Hz 10 bit color gives me black screen in fullscreen mode.

Switching to 240 Hz 8 bit color (no DSC), there is no issue.

Interesting. Could it be that with 10bit color and 360 Hz, even RTX50 cards have to use multiple pipelines and run into the same problems as RTX40 cards with 360 Hz 8bit?
In this case... DSC is (again) not the actual problem.

You could try to disable the tiling via registry. With 8-bit color the 360 Hz mode should still be available. With 10-bit it could be gone.

RTX 50-series cards do not share the same limitation as DP 1.4 videocards did with DSC, that means even with DP1.4 monitor and cable you can use DSR / DLDSR (or custom resolution) and not have the same black screen issues as RTX 40-series and older experience.

You can also use 10-bit with VRR/Pulsar with HDR no problem. With DSR 'hacked' to 8K resolution you even get to keep the 360Hz output, I think at 16K it may be 60Hz but that is an exceptionally high resolution not workable in many games.

It runs on all RTX-50 series cards on a single display pipeline even though DSC is still active to compress the image to send it through to the display but the GPU side is well capable enough to handle all the bandwidth required.

So whatever issues you experience on DP 1.4 videocards may disappear using a newer videocard.

You can also see some more in depth explanations here to have an idea what each combination offers:
https://tftcentral.co.uk/articles/loads ... nd-updates

kitabatake_radeka wrote: ↑

29 May 2026, 08:54

To circle back a little bit to my previous question: which driver would you recommend for the firmware 1.1.6 and an 5090 GPU?

I would probably advice to still install the latest one, unless you're experiencing issues you didn't on previous ones which can at times be a bit of a mixed bag between GPU architectures, though recently they have implemented some security updates for the drivers in May so I would still make sure to have atleast that version or newer installed for security.

https://nvidia.custhelp.com/app/answers ... --may-2026

I did have to install the 610.47 driver completely clean because I had issues with GTA V Enhanced not booting due to some strange underlying driver issue which may have been a result of doing multiple GPU driver upgrades in a row without a clean install which caused below crash errors in the launcher error logs:

[DISPLAY] [23800] [gamelaunch] Game exited with code 0xc0000005 (3221225477)

(For the record, a friend with RTX 5090 and 610.47 driver had the exact same issue as above, yet someone at Nvidia I let them test the same thing and their 610.47 driver booted the game, albeit they installed it using clean install method so the upgrade path may be broken, all three RTX 5090s)

So what I did was wipe 610.47 completely including leftover folders, registry and physx + legacy physx.

Then I reinstalled the previous driver, re-imported my driver profiles with Nvidia App override bypass so I can control DLSS overrides in any game without Nvidia App resetting the driver profiles for those particular games.

The game functioned again afterwards with all my programs open + RTSS overlay.
After that I installed the 610.47 driver over it and install Legacy PhysX without doing a clean install and things are fine again.

Noteworthy, I had some stuttering issues on the Pulsar display in DOOM TDA with the previous few drivers on 3x/4x MFG mode, but that looks to be solved now in 610.47 with maybe the only leftover 'issue' being if you switch from a Legacy native FPGA G-sync monitor to the Pulsar display that 4x MFG may still exhibit some frametime stutters until you retoggle the MFG settings ingame.

Sometimes MFG behaves differently on the old G-sync monitor versus the Pulsar monitor even on different multiplier modes, but the recent updates in the drivers regarding multi-monitor with MFG and V-sync fixes may have contributed to this improved stability.

Only RTX-Remix games like Portal and Half-Life 2 still seem to stutter on 4x MFG mode (2/3x is smooth) making the motion feel like half the smoothness on 4x mode despite higher FPS even on DLSS Ultra Performance on a RTX 5090 which is a bit questionable why this happens when games like Cyberpunk 2077 have zero stutter doing even 6x MFG.

The 610.47 driver has not yet fixed the Stand-by -> wake up for G-sync on the PG279Q essentially deactivating it when woken up but that is to be fixed in the future, Pulsar does not show this problem.

But in short I would probably still go for 610.47, albeit a clean install and re-import your driver profiles if required through Nvidia Inspector.

Mighty_opf wrote: ↑

26 May 2026, 14:22

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).

Oh thanks for the hint. Mine was also on MCM102... browser updater said I was running on 1.1.6 but after reinstall I also have MCM103(1.1.6).

As the ghosting was gone on RE9 I assume it really was 1.1.6 before... But who knows

There was a problem with the version number on the original upload of the 1.1.6 firmware for ASUS.

drG-SYNC wrote:Our first posting of Asus 1.1.6 on Tuesday May 19th 2026 had an incorrect Asus version number MCM102. The correct version is MCM103. We just posted the corrected version on link .

MCM102(1.1.6) and MCM103(1.1.6) are functionally identical, except for the version number itself !

If you updated before today and want to change your MCM102(1.1.6) to MCM103(1.1.6) you can use the link to Reinstall v1.1.6. It will tell you you are running latest, but you can choose to Re-install and it will get you MCM103(1.1.6). But again, there is no functional difference, so there is really no need.

Sorry for this confusion, drG-SYNC.

Source: https://www.nvidia.com/en-us/geforce/fo ... mcm103116/

rexbinary wrote: ↑

30 May 2026, 13:39

There was a problem with the version number on the original upload of the 1.1.6 firmware for ASUS.

drG-SYNC wrote:Our first posting of Asus 1.1.6 on Tuesday May 19th 2026 had an incorrect Asus version number MCM102. The correct version is MCM103. We just posted the corrected version on link .

MCM102(1.1.6) and MCM103(1.1.6) are functionally identical, except for the version number itself !

If you updated before today and want to change your MCM102(1.1.6) to MCM103(1.1.6) you can use the link to Reinstall v1.1.6. It will tell you you are running latest, but you can choose to Re-install and it will get you MCM103(1.1.6). But again, there is no functional difference, so there is really no need.

Sorry for this confusion, drG-SYNC.

Source: https://www.nvidia.com/en-us/geforce/fo ... mcm103116/

Good to know my assumptions were correct, thank you.

this monitor is actually 26.92056 inches diagonal, (pretty sure exact size of old pg27aqn) its 25 inch mode is actually 24.901518 inches, to get 24.5 inches

if you intend to try it out, be careful, make a system restore, or make sure you have another monitor, first time trying with just sre resulted in display black screen, so i had to use cru first, than make custom sre resolution, then reboot pc, then i had to disable ulmb2 and disable and re enable gsync for pulsar to start working

24.5, and then enable gpu no scaling in nvdia control panel

^^^ edit: I WOULDNT RECOMMEND DOING THIS, ATM SOME GAMES JUST DONT PLAY NICE, MAYBE I NEED TO MAKE OTHER 240HZ AND 60HZ OPTIONS, or that my pc is corrupted idk atm