Tried the 22.11.2 on a 6600xt, random ctd when I'm on planets, orbit lines still bugged. Went back to 22.5.1.
AMD RX 6000 series driver issues & workarounds
I can verify that planets in the FSS, in VR, are borked on 22.12.2 - they are 'folded' as they were before Morbad's fix for 22.5.1 onward.
Let me start by saying this that i had watched this thread earlier aka when i didnt have my AMD RX6400. I got this gpu as a xmas gift and as i got it i thought this gpu might also be affected by the blue teal effect/bug.
My Old PC Specs & driver
So i installed the recommended gpu driver 22.5.1 as said in the thread i only did that not the 3dmigito stuff or any other the performance was to find a stable setting i even had to go down to 800x600 just to check but of no use so i tested the 22.10.3 driver which after i exited the game to desktop would hang my pc driver issue
so i tested 22.11.2 and here are the screenshots i took
Settings are all low at 1080p @ 30fps with Normal AA 1x turned off the check board thing as well.
So i guess AMD RX 6500 and above series gpus are affected not the 6400 the game is running somewhat smooth but this is just a test i game aft 1600x900 so the performance will improve more. I hope this blue teal thing gets fixed in 14.0.2 update thats all from me 07 cmdrs. Just adding the gpu-z info as well
My Old PC Specs & driver
So i installed the recommended gpu driver 22.5.1 as said in the thread i only did that not the 3dmigito stuff or any other the performance was to find a stable setting i even had to go down to 800x600 just to check but of no use so i tested the 22.10.3 driver which after i exited the game to desktop would hang my pc driver issue
so i tested 22.11.2 and here are the screenshots i took
Settings are all low at 1080p @ 30fps with Normal AA 1x turned off the check board thing as well.
So i guess AMD RX 6500 and above series gpus are affected not the 6400 the game is running somewhat smooth but this is just a test i game aft 1600x900 so the performance will improve more. I hope this blue teal thing gets fixed in 14.0.2 update thats all from me 07 cmdrs. Just adding the gpu-z info as well
Last edited:
Hi,
I watched your video, and based on the measurement values, I suggest that you firstly raise the frame rate limit to 60 Hz, because the highest GPU usage reading that I saw on the video was 72%, and it was below 70 most of the time. You could also try a notch higher terrain quality setting, because your graphics card has quite much free VRAM for the whole duration of the video. And I recommend that you stick with the FullHD (1080p) resolution from now on, because the RX 6400 is very capable to handle that.
BR,
Mika L.
Yes thank you for your inputs and yeah RX 6400 is a good gpu i can run witcher 3 at 1440p at 30fps with FSR 2 (Performance) but Elite on the other hand needs alot of optimisation to reach that level.
Steam Community :: Error
Noticed that the new RX 7900 series 23.1.2 driver contained a fix for SpaceEngine that, if it's not purely application specific, might be of some help to those still experiencing issues with Odyssey. I also noticed that, while the driver only claims 7000 series support, that this includes RDNA2 based APUs, which suggests that the driver should actually function on Navi2x (6000 series) parts.
So, for anyone that wants to try it, I've modded the newest 23.1.2 driver to be compatible with the RX 6000 series cards. Unfortunately, this required modifying the .inf, which breaks driver signatures. The recommended way to bypass this is to hold shift while selecting restart from within Windows, then "advanced options", "startup settings", and restart. Once the startup settings menu comes up, select "disable driver signature enforcement", and let it boot into Windows. Then install the new drivers and 'install anyway', when it prompts about unsigned drivers, then restart again.
Note, I have no real idea what issues these drivers might fix or introduce. They should be clean (feel free to scan them yourself, of course), as I the only thing I did to them was a cleanup pass with Radeon Software Slimmer (which itself doesn't alter anything beyond AMD's install scripts), then manually pulled out a few more things from the .inf before copy-pasting in support for the 6000 series cards, which is all done in plain text.
If one doesn't like them, just uninstall them (I recommend DDU or AMD's own cleanup utility) then reinstall your preferred drivers.
So, for anyone that wants to try it, I've modded the newest 23.1.2 driver to be compatible with the RX 6000 series cards. Unfortunately, this required modifying the .inf, which breaks driver signatures. The recommended way to bypass this is to hold shift while selecting restart from within Windows, then "advanced options", "startup settings", and restart. Once the startup settings menu comes up, select "disable driver signature enforcement", and let it boot into Windows. Then install the new drivers and 'install anyway', when it prompts about unsigned drivers, then restart again.
Note, I have no real idea what issues these drivers might fix or introduce. They should be clean (feel free to scan them yourself, of course), as I the only thing I did to them was a cleanup pass with Radeon Software Slimmer (which itself doesn't alter anything beyond AMD's install scripts), then manually pulled out a few more things from the .inf before copy-pasting in support for the 6000 series cards, which is all done in plain text.
If one doesn't like them, just uninstall them (I recommend DDU or AMD's own cleanup utility) then reinstall your preferred drivers.
Zippyshare.com - [now defunct] Free File Hosting
www8.zippyshare.com
It'll be interesting to see if it solves the DayZ crash to desktop attempting to launch. Might give this a whirl - or might just wait for the official package to be safe
The corresponding entry within the issue tracker is now in state "Vote".
issues.frontierstore.net
Maybe if enough people vote there, Frontier will do something about that.
Regards
Issue Tracker
issues.frontierstore.net
Maybe if enough people vote there, Frontier will do something about that.
Regards
Added a comment (can repro 100% of the time) and upvoted issue.The corresponding entry within the issue tracker is now in state "Vote".
Issue Tracker
Maybe if enough people vote there, Frontier will do something about that.
Regards
Apparently a group of Modders have 'improved' AMD drivers:
Amernime MODDED Drivers here: https://www.amernimezone.com/
Amernime MODDED Drivers here: https://www.amernimezone.com/
For me it only happens with last AMD drivers 22.11.2 and when I use pico 4 visor. With first Oculus Quest it didn't happens. I didn't try if the error persist in windows 11. I have windows 10 with all updates. For me come back to previous work properly. I try to use Virtual Desktop to avoid HEVC codec but with H.264 codec the error persist. I didn't try to connect Quest with Virtual Desktop to try if the error persist. I always use Quest buy usb cable.
Nope.
There was an official "News & Bulletins" thread which used to be pinned but is now un-pinned: https://forums.frontier.co.uk/threa...-rx-6000-series-driver-updates.606134/page-10 .
The bug tracker issue is still in state "voting": https://issues.frontierstore.net/issue-detail/56183 .
It doesn't look like communication is going to happen anymore, let alone actual bug fix work.
Is there actual any bugfix except going back to driver 22.5.1 ?
No. AMD fixed their end in 22.10.3 (crash to desktop when launching ED), FDev claims to have delivered a fix for broken planets in some minor patch release last year but forgot to verify if it also fixes VR (it doesn't). If you have a RX6xxx then rolling back to 22.5.1 is the only option (though this implies a performance penalty). If you have a RX7xxx you're out of luck.
Last edited:
23.2.1 works fine in EDO - just did a quick run around an atmo planet...
EDO VR still broken with 'folded' planets, as previously.
ETA: I'll have a better play around a little later and check out a few other scenarios.
EDO VR still broken with 'folded' planets, as previously.
ETA: I'll have a better play around a little later and check out a few other scenarios.
Last edited:
Unluckily I can confirm that with the new drivers landable planets in VR are still broken. What I did:
I will add the info to the issue.
- Installed 23.2.1
- Cleared shader cache
- Deleted gpuWorkTables.xml
- Launched ED in VR
I will add the info to the issue.
I tried 23.2.1 (without VR) and observed the oddities with the orbit and gravity lines were still there - meaning the gravity lines tend to break / disappear when they are positioned exactly horizontally or exactly vertically, and the orbit lines are very faint.
- Installed 23.2.1 over the 22.11.2 - in place upgrade.
- Rebooted
- Launched Odyssey and it rebuilt whatever it does upon startup when it detects a new driver has been installed
- Tested - in space only, haven't landed yet