NVIDIA G-Sync Pulsar monitor - Asus ROG Strix XG27AQNGV

[brownvim]

Does anyone have confirmation whether any of these monitors use DSC or not? I found I was unable to use DLDSR on the Acer monitor but I'm not sure if that's indicative of DSC being on or not.

I think I can use DSR on mine, if this is what you mean:

Untitled.jpg

Strange. DSR doesn't even show up on mine and I can't make custom resolutions or even make one with CRU. Anyone know why?

This was on the previous firmware using display port and a RTX 5080.

Which Pulsar display do you have?

I have the Acer. Maybe different models haven’t had things enabled yet, would need someone else to confirm with your model.

[kyube]

Using a DP 2.1 cable. 4080 Super.
I've rolled back the FW update cuz of ghosting issues

The cable is irrelevant, you are still limited by the scaler IC's capabilities.
The only option to be (hopefully) without DSC is to run HDMI 2.1 on the new firmware update.
They've enabled FRL5 bandwidth with the new firmware update, as opposed to TMDS on out of the box firmware (seemingly?)
Though, whether FRL5 bandwidth will be enough... I have my doubts.

[Argus]

Does anyone have confirmation whether any of these monitors use DSC or not? I found I was unable to use DLDSR on the Acer monitor but I'm not sure if that's indicative of DSC being on or not.

I think I can use DSR on mine, if this is what you mean:

Untitled.jpg

Strange. DSR doesn't even show up on mine and I can't make custom resolutions or even make one with CRU. Anyone know why?

This was on the previous firmware using display port and a RTX 5080.

Which Pulsar display do you have?

I have the Acer. Maybe different models haven’t had things enabled yet, would need someone else to confirm with your model.

I have the acer model and I rolled back to the initial firmware. Could it have something to do with me using a 40 series gpu instead of a 50?

[kyube]

I have the acer model and I rolled back to the initial firmware. Could it have something to do with me using a 40 series gpu instead of a 50?

Yes, single head limit of the DP1.4 port on 20/30/40 series cards.

NVIDIA and DSC - ToastyX Wrote:
NVIDIA's driver currently ignores EDID overrides if Display Stream Compression (DSC) is active and the maximum resolution @ refresh rate combination exceeds the GPU's single-head pixel clock limit:

GTX 1600-series: 1330 MHz
RTX 2000-series: 1330 MHz
RTX 3000-series: 1335 MHz
RTX 4000-series: 1350 MHz
RTX 5000-series: Not affected

Workarounds:

SRE can add custom GPU-scaled resolutions but not custom refresh rates: https://www.monitortests.com/forum/Threa...Editor-SRE
Use RegEdit to disable using multiple heads, but the pixel clock will be limited to the single-head limit:
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\#### (usually 0000)
Value: "EnableTiledDisplay"=dword:00000000

[mawi]

NVIDIA and DSC - ToastyX Wrote:
NVIDIA's driver currently ignores EDID overrides if Display Stream Compression (DSC) is active and the maximum resolution @ refresh rate combination exceeds the GPU's single-head pixel clock limit:

GTX 1600-series: 1330 MHz
RTX 2000-series: 1330 MHz
RTX 3000-series: 1335 MHz
RTX 4000-series: 1350 MHz
RTX 5000-series: Not affected

Not really sure what this is about but could this be the reason for RTX50 series not showing black screens when alt+tabbing and also sometimes ingame when running 360 Hz?

[kitabatake_radeka]

Hello, I also have this monitor.

I had a little trouble getting it working, as with me using the 572.83 driver on a 5090 there were random black screens in games when connected via DP 1.4 (and HDMI 2.1 was limited to 120 Hz), so I updated to the 591.86 driver and everything seems to be working fine now, 360 Hz 10 bit depth HDR when connected by DP 1.4 (still using the original firmware it came with). But I still have few questions which hopefully someone of you will know answer for:

1. does the new firmware update allow for full bandwith via HDMI 2.1, i.e. no DSC? I guess bandwidth limitations would still make only 240 Hz viable with no DSC, but that is more than enough. If not, is the firmware update worth it anyway, if I am not interested in the new fixed 60 Hz mode?

2. I generally had the experience the newer the NVidia drivers after 572.83 the worse. What is the oldest driver fully compatible with the pulsar technology, and does it differ between the original and the new firmware?

3. In the control panel, is it better to set the scaling by GPU or by the monitor? I never had a monitor with a dedicated GSync chip before, so I standardly use GPU scaling, is there any difference here?

4. What is the best framecapping method to use with this monitor? Right now, I am using Special K and the Latent Sync limiter (no VSync, tearing ON) with the 1/2 refresh rate option (so approx 179.99 FPS) in most games; with the 1/3 refresh rate option (so approx 120 FPS) in the games that struggle to get above stable 130 FPS in QHD (such as Hell is Us).

[brownvim]

I rolled back the firmware today to confirm this problem goes away, 90-360hz is clean. Current firmware even a 1 FPS adjustment up or down causes ghosting between 90-180 FPS which negatively effects the clarity.

This is amazing! Thanks for that. Hopefully this will be adressed soon... Now having clear proof etc.

Some good news, Nvidia were able to recreate the issue and are working on a fix I have been told

[peupeuw]

3. In the control panel, is it better to set the scaling by GPU or by the monitor? I never had a monitor with a dedicated GSync chip before, so I standardly use GPU scaling, is there any difference here?

You won't need the scaling for neither native resolution nor competitive 25-inch mode if your monitors has it. Simply keeping the regular/competitive toggle and corresponding system resolution in sync should do the trick. My Acer model seems to actually use a refresh rate of 359.98 Hz for native res and 359.96 Hz in competitive - perhaps intentional for easier differentiation/switching.

[kyube]

Some good news, Nvidia were able to recreate the issue and are working on a fix I have been told

Where have you managed to contact Nvidia?
I'm hoping that they:
• Finally unlock full BW to HDMI 2.1 FRL6, instead of FRL5.
• Allow wider duty cycle range (or fix the PW slider?) in ULMB2 mode for 120Hz, 240Hz & 360Hz (so one can push much shorter duration strobe on periods, which is much easier on higher refresh rate)

[brownvim]

Some good news, Nvidia were able to recreate the issue and are working on a fix I have been told

Where have you managed to contact Nvidia?
I'm hoping that they:
• Finally unlock full BW to HDMI 2.1 FRL6, instead of FRL5.
• Allow wider duty cycle range (or fix the PW slider?) in ULMB2 mode for 120Hz, 240Hz & 360Hz (so one can push much shorter duration strobe on periods, which is much easier on higher refresh rate)

What's broken with the Pulse Width slider in the higher refresh rates? Seems to act the same way to me 10-100 adjustment and reduces brightness in the same way the 60hz mode does.