When waking up my Ultrawide LG 34gk950f from sleep, the resolution of my monitor goes to 1200x800 and has black bars on the left and right side. The issue is resolved by either powercycling the monitor, reseating the DP cable, toggling the display port in the monitor between 1.4 and 1.2 or rebooting the PC. Thinking that the monitor may be starting slower than the 6900xt, I played with Windows power settings, nothing helped. I've turned off HDCP, freesync and all other settings within Adrenaline, this did not solve the issue. Installing the monitors latest driver did not solve the issue. Swapping to another DP cable did not solve the issue. Tried a RTX 3080 and could not duplicate the issue. Uninstalling/reinstalling the latest driver/adrenaline did not solve the issue (DDU was used for a clean wipe).
I did a clean boot of Windows and ended the Adrenaline process. When my monitor went to sleep, it woke up with the correct resolution. Tested this multiple times and each wake up worked correctly. I then started Adrenaline, let the monitor go to sleep, and the resolution issue returned.
I uninstalled the driver and adrenaline software again, then installed ONLY the 6900xt driver. Ever since doing this, waking my monitor up from sleep has been fine. It seems something between Adrenaline and having an ultrawide monitor is causing this issue. I already reported the issue to AMD, but wanted to see if anyone else has experienced this problem or found a fix. At the least, making the community aware of my problem may help someone down the road too.
I have tried rebuilds, clean driver installs, and nothing is working, if I use 20.9.1 and earlier it all works, if I use 20.11 or 20.12 then I get the resolution issue and I have to reboot or pull cables from the monitor and its annoying now.
Grabbed the 20.12.1 drivers, turned off Freesync via the monitors OSD and turned off freesync in the AMD drivers and now it will wake sometimes without he resolution issue but you do get the black screen issue! Still have to turn the monitor off to sort it. Will stick on the 20.9.1 for the forseeable I think and try again in a few months.
Do either of you have VR setup by chance? I do, and I'm thinking that Adrenaline is waking up both devices at the same time, and my VR's headset is quicker. Which then Windows is "extending" or "cloning" the display to match it's resolution to my monitor, even though it's not set to do that. An odd thing I noticed when I first got the 6900xt is that my VR's display is always on when plugged into the hdmi port after installing Adrenaline. To get that to shut off, I have to go into Steam, open VR up and shut it down, and the headset no longer stays on. But, just maybe, there's still a wakeup signal coming from the headset. I have unplugged the VR's hdmi port from the card, but haven't had a chance to test.
I don't have a VR headset but you got me thinking, I do have the usb cable from the monitor to the PC and I am wondering if the USB is causing an issue, I will disconnect it and try with newer drivers and see what happens.
I will update this after work this evening and let you know how I get one, will reduce the connection to the one DP1.4 cable. I may jump down to the HDMI 2.0b and just game at 85hz and see if I get the issue on HDMI.
So I do not want to curse this but I used the cleaner utility again, installed 20.12.1 and unplugged the USB cable from the monitor to the PC and its not done it since so it might be that the USB was waking at the same time and causing issues. not sure how but not seen the error as yet.
Mind my monitor is still working like a dream on the 20.12.1 drive atm with me disconnecting the usb cable used to update the monitor OSB/software for the LG ultra wide. I will keep monitoring it and see how I get on.
With my VR disconnected (only a single DP port plugged in), I set Windows power settings to put the monitor to sleep after 1 minute for testing. I found that waking the monitor up after around 1 minute of sleep was quick and there was no resolution issue (tested around 5 times). I got up, did some things, let the monitor "deep sleep" for over 5 mins, and the issue occured upon wake up (tested 3 times, each failed).
I'm still thinking the monitor is waking up slower than the video card, and a handshake of sorts is not taking place. Adrenaline still recognizes the display as my monitor, and nothing generic. Since we're all doing a sort of...powercycle...to get the display properly after the GPU is awake, it seems a signal is being missed when the GPU and monitor are both being woken up.
1. GPU sends a wakeup signal and request asking the monitor of its capabilities. The monitor gets the wakeup signal, but is too slow and doesn't hear the capability request from the GPU, therefore never sending one. The GPU is then forced to do its job in some fashion, and forcing low resolution modes that any monitor should be capable of handling.
3. Adrenaline is forgetting what the monitor is capable of doing, when it really should retain that info and push the last known settings used ---- (TBH, I'm unsure if a signal from the monitor advising of its capabilities is a real thing. I assume it is since somehow Windows knows what resolution or Hz a monitor can be without a monitor driver).
I can confirm, that it works ok if you wake it up as you say very quick like a minute. I am not really sure, if the monitor does have different sleep states, so my guess would be it is the GPU drivers.
I will also try searching LG & other forums, where some users reported issues with black screen after waking up (probably not related, but at this point I will look into anything). Also, I am eager for a new AMD driver to see if it fixes it.
I moved to the HDMI cable last night, yes this only gives 85hz (I bought the monitor for the 144hz gaming) however playing last night, freesync is smoother on 85Hz and the card seems to handle better.
With the HDMI I cable, I locked the computer and then did a load of tests, 5 mins, 10, 30, 60, 2 hours, 4 hours etc and each time I came back no monitor issues at all with the resolution (I am using a HDMI 2.0b spec cable), it just works.
Went back to the DP cable, removed all drivers, went from 20.8.x to 20.12.1, DP worked up to 20.9.1, then after that the issue appears so has to be driver issue as if it was monitor, cable or card then it would do it regardless.
I think LG have an issue with the screen and they are doing nothing about it, they released a 38" version and that doesn't do it, in the LG Community link you can see that Linus tech mentioned this about the monitor and it did it for him too.
To fix the issue when it happens I am using the Ctrl + Shift + Win Key + B which resets the display driver and it sorts it that way. Interestingly, if I don't lock the machine and just leave it to go to sleep normally I have not seen the issue as yet, just from the lock screen!
Has anyone else tested that yet? If we find that with only installing the driver doesn't result in this issue, I think we can safely remove the driver and monitor as the issue, and point our finger at Adrenaline.
Never let the monitor go to sleep and if I know I am gonna walk away for a while turn off the monitor. I can't work out any other option other than staying on months old drivers and praying it doesn't happen.
Thats the part I can't work out. Maybe something with the monitor and the driver not triggering the issue and newer ones do, or windows patches, I do also get this issue on the old Iiyama 24's 144hz monitors I used to have.
I am on an old Intel chipset though so could it be that? I am on a i7 6700K and the MSI Krait Z170A chipset. Is it a chipset issue, bios issue. I just don't know. All I know is if I use HDMI its great and works, Display Port it doesn't and I have tried turning off options for the card, certified cables, bios tweaks and nothing.
I managed to get the 38" version of our LG panel from work yesterday, guess what, issue does not happen, same drivers, same cables, it always comes back even after hours of letting it put the monitor to sleep.
With the latest Adrenalin and chipset drivers, I sometimes get a black screen when waking the monitor as well, not just the low 1280x800 resolution. I switched to HDMI (85Hz) now and will report back.
Now interestingly, when this happens, if I had any windows open at the time, they all resize to 1200x800 instead of half and half on the screen, however the res stays at 3440x1440 so its not causing the res issue. It does this on any driver with the screen saver. I am starting to think this is something to do with either the Picture in Picture that the panel can do or there is some weird display issue with the firmware/panel.
I also ordered a high quality (VESA certified) DisplayPort 1.4 cable and will test as well. I will also test with an Nvidia GPU, as the original poster mentioned he couldn't reproduce the issue with an RTX 3080 card.
An ultrawide support fix for Devil May Cry 5 has appeared on Steam, while players wait for Capcom to potentially add an official solution to their resolution woes, and it turns out it is quite easy to use.
Open it with your software of choice (or 7Zip if you have it), and you'll find a series of executables titled after several ultrawide resolutions. Simply paste the executable of the resolution you want to use in the game's folder. By default, it should look something like Drive:\Program Files\Steam\steamapps\common\Devil May Cry 5\.
After copying the executable, simply launch the game using it and change the resolution to your desired one while in-game. As it's a player-made ultrawide fix, and not an official patch for Devil May Cry 5, you may run into issuess. At the moment, however, it seems to be the only options for playing Devil May Cry 5using ultrawide resolutions.
I have an ultrawide monitor that is great. I fly the Fenix. Is there a Captains profile out there that doesn't stretch the entire view to the first officer side? Ideally i'd like to have a more realistic viewpoint from the captain flying perspective. I was curious for those using an Ultrawide and the Fenix what you are using. I have a 49" UW monitor
c80f0f1006