Who you gonna call? The Blur Busters! For Everything Better Than 60Hz™
https://forums.blurbusters.com/
I suppose you have a beefy machine and your 1% lows are still fine? Then I guess that is possible.toyosenpai wrote: ↑03 May 2026, 18:02
I tested various things like gsync off, ulmb2 on, frame cap to 360, uncapped etc... and none of these tests made the game as smooth as pulsar+gsync+vsync+reflex.
My Discord is vim18, but I'm not really into shooters so don't know how much help I can be. I was just trying to get it set up right for my brother to test out the monitor.toyosenpai wrote: ↑03 May 2026, 18:02Hey. Do you have a discord we can share to test some stuff together?
Not the best at the moment - 1 generations ago I guess, 13900kf and 4090, my fps very rarely dip below 320 at 2560x1440 - enemies appear super clear so I really like this res and I used to play 1920x1080 before.mawi wrote: ↑04 May 2026, 13:52I suppose you have a beefy machine and your 1% lows are still fine? Then I guess that is possible.toyosenpai wrote: ↑03 May 2026, 18:02
I tested various things like gsync off, ulmb2 on, frame cap to 360, uncapped etc... and none of these tests made the game as smooth as pulsar+gsync+vsync+reflex.
I've added you on disc if you want to test a few more settings together.brownvim wrote: ↑04 May 2026, 16:31My Discord is vim18, but I'm not really into shooters so don't know how much help I can be. I was just trying to get it set up right for my brother to test out the monitor.toyosenpai wrote: ↑03 May 2026, 18:02Hey. Do you have a discord we can share to test some stuff together?
I would consider 4090 as beefytoyosenpai wrote: ↑05 May 2026, 02:58
Not the best at the moment - 1 generations ago I guess, 13900kf and 4090, my fps very rarely dip below 320 at 2560x1440 - enemies appear super clear so I really like this res and I used to play 1920x1080 before.
Sorry I missed your post. The issue was present out of the box with V1.0.6 and is still present on V1.1.4. V1.1.6 is not out for my ASUS monitor yet to test.Allen.YL.Wu wrote: ↑30 Apr 2026, 20:06@rexbinary
6. The latest issue is after the monitor wakes from sleep, and you launch a game set for fullscreen display, the game will not display. You will instead see a black screen, and the bottom most light strip will blink once. It will repeat this slowly as if it's trying to go into full screen repeatedly. I have to ALT-F4 the game, and then power off the monitor and power it back on. Then full screen games will launch with no issues until the monitor sleeps again.
I’m pretty interested in this issue. Aside from setting it to 240Hz, are there any other ways to work around it? For example, something similar to how it behaves on FW V1.1.6.
I’d also like to understand whether this issue already existed in V1.0.6, or if it started showing up after updating to V1.1.4. I’m currently on V1.0.6, so I’m trying to decide whether it’s worth updating the firmware.
Could you also share the exact steps to reproduce the issue? That would help me evaluate whether I should proceed with the FW update.
I tried this for you on my RTX 5090, desktop is set to 10-bit SDR mode at 360Hz, GTA IV which I know doesn't do fake fullscreen / borderless also set to 360Hz and it works just fine, monitor recovers back to G-sync/Pulsar enabled mode and runs the game fine.rexbinary wrote: ↑07 May 2026, 00:10Sorry I missed your post. The issue was present out of the box with V1.0.6 and is still present on V1.1.4. V1.1.6 is not out for my ASUS monitor yet to test.
Steps to reproduce:
1. Set desktop to 360Hz.
2. Set in-game to 360Hz.
3. Let monitor full sleep. (No glow at all) You can set the timeout to as low as 2 minutes in Windows.
4. Wake the monitor.
5. Launch the game.
6. You will get a black screen that flashes white repeatedly slowly.
7. To avoid this issue, you need to cycle power on the monitor after sleep before launching any games.
I have the RTX 4080 Super Founders Edition. I'm not sure but this might not be an issue for RTX 50x0 owners.
The workaround as I mentioned is to just run your desktop at 240Hz and set 360Hz in game.
I have the same problem, after monitor goes to sleep can't run any game. Have to turn it off then back on.rexbinary wrote: ↑07 May 2026, 00:10Sorry I missed your post. The issue was present out of the box with V1.0.6 and is still present on V1.1.4. V1.1.6 is not out for my ASUS monitor yet to test.Allen.YL.Wu wrote: ↑30 Apr 2026, 20:06@rexbinary
6. The latest issue is after the monitor wakes from sleep, and you launch a game set for fullscreen display, the game will not display. You will instead see a black screen, and the bottom most light strip will blink once. It will repeat this slowly as if it's trying to go into full screen repeatedly. I have to ALT-F4 the game, and then power off the monitor and power it back on. Then full screen games will launch with no issues until the monitor sleeps again.
I’m pretty interested in this issue. Aside from setting it to 240Hz, are there any other ways to work around it? For example, something similar to how it behaves on FW V1.1.6.
I’d also like to understand whether this issue already existed in V1.0.6, or if it started showing up after updating to V1.1.4. I’m currently on V1.0.6, so I’m trying to decide whether it’s worth updating the firmware.
Could you also share the exact steps to reproduce the issue? That would help me evaluate whether I should proceed with the FW update.
Steps to reproduce:
1. Set desktop to 360Hz.
2. Set in-game to 360Hz.
3. Let monitor full sleep. (No glow at all) You can set the timeout to as low as 2 minutes in Windows.
4. Wake the monitor.
5. Launch the game.
6. You will get a black screen that flashes white repeatedly slowly.
7. To avoid this issue, you need to cycle power on the monitor after sleep before launching any games.
I have the RTX 4080 Super Founders Edition. I'm not sure but this might not be an issue for RTX 50x0 owners.
The workaround as I mentioned is to just run your desktop at 240Hz and set 360Hz in game.