Forum Discussion
I do have a work around that I use. Have HDR enabled in windows, load up the game and switch it to windowed mode. Then relaunch the game and as soon as the window pops up hit the expand box. Now it will work as intended at about 98% fullscreen. I changed my accent colors to black so I don’t even notice I’m in windowed mode. It works every time for me.
I might have found a workaround for AMD users......
If you're using AMD, give this a try and see if it works for you.
Download the latest drivers - 23.12.1 as of this post.
Enable Radeon Super Resolution.
Set your in game resolution 1 step down from your native resolution. (this causes RSR to "kick in")
The first time this is set, you might need to exit the game and relaunch.
Enjoy HDR!
I forgot how amazing this game looks with HDR it's been so long since 4.2.0 released and wrecked it!
I don't know why this works - I'm guessing when RSR is enabled and intercepts it allows the game, windows, and HDR all to sort out their differences like adults and work together? 🤷♂️
- 2 years ago
...just wanted to add - that using Radeon Super Resolution causes the game to first launch in a small window, which will go fullscreen after clicking on it.
I believe this is the key - this is the same behavior that used to exist prior to the 4.2.0 update.
This also explains why @lex_lutha111384 's fix works - the key has something to do with the game launching in a window that allows HDR to work properly.
However, simply running the game in windowed mode doesn't allow HDR to work properly.
- SubSonix2 years agoSeasoned Rookie
This just sounds like another work around, not a proper solution.
But I'm glad you've found something that works for you. I am running nvidia so I can't even try this sadly. - 2 years ago
This is right. If you just switch to windowed mode, from fullscreen, hdr is still dull and *. You have to launch the game in windowed and expand the screen as soon as it pops up. The other day it was working but it was bizarre. Switching to HDR and SDR was not flashing. It was just switching in real time. It looked correct though. I’m lost.