brownvim wrote: ↑12 Mar 2026, 16:46
What's the reason your both using it in 240hz mode?
With 360 Hz the display signal is compressed via DSC. On some displays (not just pulsar, also some Asus OLEDs) this leads to black screens when switching to full screen and alt+tabbing. Not just that. It even blacks out in the middle of some games if you run them on exclusive full screen. Which is the only option on some older games or emulators if you dont want to have any menu bars.
According to some reddit posts, this is a problem with RTX 30 and 40 cards (4070 on my end).RTX 20 and RTX 50 cards as well as AMD cards do not show this behaviour (AMD of course is anyway not an option with pulsar but they seem to work fine on OLEDs with 360 Hz, qhd and DSC). The fact that RTX50 cards are DP2.1 should not matter as the display is just 1.4 but I have read somewhere that RTX 20 cards have more "conservative link training"... whatever that means, and RTX 30/40 cards are more sensitive to extreme pixel clocks. RTX 50 cards have the latest DP2.1 PHY which could help. And the fact that I havent found ANY reports that this happens there... is enough for me.
Long story short... noone can really say why it behaves like this. But with 240 Hz we assume (although you cannot really confirm this through Nvidia CP or display OSD) the signal is not compressed, hand shake works better, no more black screens. Of course when switching to exclusive full screen its also black, but for a much shorter time and it does not black out while gaming.
If pulsar works as it should (1% lows are good)... a well strobed 230 fps picture anyway looks almost identical to a 340 fps picture.
But as stated above, I have now discovered this new thing regarding pulsar being turned off when returning from standby. I will not switch back to 360 Hz for now anyway (until i upgrade to a rtx50 card or newer), so I just hope this will be fixed with a fw update.
