AMD RX 6000 series driver issues & workarounds

I have absolutely no issues after rolling back the RX6950XT driver to 22.5.1. I can put up with the still thin orbit lines but everyhing else with planets and terrain is working great on high and ultra settings. Absolutely loving the gameplay now.
 
I have absolutely no issues after rolling back the RX6950XT driver to 22.5.1. I can put up with the still thin orbit lines but everyhing else with planets and terrain is working great on high and ultra settings. Absolutely loving the gameplay now.
Much the same with the 6750 XT - after a recent semi-auto update that slipped past my guard and a series of Orange Sidewinders, it has been as fine as before with a quick rollback to 22.5.1 (y)
 
I use 22.11.2 with a 6900XT, often struggle with deformed planets. Sometimes I can't start the game (always crashes on start-up) when I'm at an "unfortunate" point on the surface (including planetary docks) - only way out is to start the game on a different PC and fly someplace else.

Deformations vary - if I exit and reenter an affected system multiple times, the planets are broken differently. I can iterate through breakage e.g. for Guardian sites until the site isn't in the center of its planet.

I use PermitNativeDoubles=false, but nothing else.
 
only way out is to start the game on a different PC and fly someplace else.
You might try the new "get unstuck" option (Start Menu -> Help -> rightmost option, labelled for SRV and on-foot issues). Works for me, puts me in my ship back into orbit.

What also seems to temporarily help (for me) so that I can at least land once (e.g. on the Engineer bases) is to run a "verify game files" before I start a session. Only seems to work for this one session, though.
 
Tested 22.11.2 on VR (using 6800) and first few planets i approached are absolutely fine with great performance. However some planets are still having the distorted form. Not sure if the distorted ones are systems i visited before. Is the VR shader cache separate from the normal cache? Anyway to reset them?

Update : Made an approach to Long Sight Base. Planet was constantly being re-rendered during the approach, alternating between smooth surface and a planet with a gravity warp grenade thrown at it. On close approach, rendering looks smooth but after the glide terminated, base wasn't didn't appear on the surface with nav marker indicating 2 km farther in from the surface. Decided to punch through the surface and then the base appeared underneath. Base rendered ok but the terrain around it was all garbage. Able to land and get my done with Elvira.
TLDR : Planet rendering is wonky still but land base is "working". Had a few other similar occurrences but not sure if its the same for all.
 
Last edited:
All, I have a RX 6800m running the absolute latest 22.11.3 and I can confirm there are issues with VR. Normal non-VR mode does not give me issues in Odyssey, I am at a guardian site with my explorer landed and can run the pylons no issues. However, if I but when I load either Odyssey 4.0, the planet is gone and all of the things on the ground except for my ship fall into nothingness... no terrain. If I try to load Horizons 4.0, I get Orange Sidewinder errors, which I think are only will be corrected when I login without VR since my CMDR coordinates are probably borked. I tried workaround #2, it didn't help me.
 
Yes there is a problem with planets in VR !
One courageaous person should make a bug report on frontier site, and we all should vote for it
 
Thanks Ashnak i voted !

Did you try this ?

Try and set your "Terrain Work" slider to a higher value in the graphics settings. Mine was really low, and seemed to be the cause of this issue. Set to 50% now, and seems to not cause any performance issues.
 
Thanks Ashnak i voted !

Did you try this ?
Already had it at maximum. Moving it one step down didn't change anything.
also not successful:
  • clearing gpuworktable while in space
  • clearing gpuworktable while landed on an affected planet

Trying to start the game while landed on a planet leads to a CTD, though.

What helps:
  • get unstuck option in the start menu at least moves me from the striken planet (with the CTD at startup) into orbit, where I can at least boot the game again
  • validating game files seems to help for the immediately following game session (this is how I was able to land at a planet - Engineer base - at least)

Next steps on the list:
  • clean reinstall of graphics drivers (suggestion from support, they're really good guys and gals there)
  • same, but back to 22.5.x (I don't wanna)
 
I think it's how the textures are rendered. It has different timings if you compare the GPUWorkTable with VR and non-VR. Some lines are removed. Others are added. So VR is a different animal for generating the planets.

Lower quality, I'm sure, due to the fact we have three screens to render.
 
Last edited:
Did AMD move on from the 6x00 GPUs? No new drivers in this round of updates.

They moved 22.11.2 to "Recommended", and are currently scrambling to patch much more serious bugs with RDNA3.

The older generations of RDNA parts aren't being moved to legacy status yet and should still see regular updates.
 
It's annoying that they did that, when 22.11.2 "recommended" still has so many issues, e.g. with Space Engine and DayZ and probably many more. I also feel that it still introduces some occassional micro stutters in ED as well. Tried it for a while with my 6800 card and was just not feeling it. Rolled back to 22.5.1.
 
Currently looking at a 6800xt red devil at the price of a 3070. Very tempted - but if it means I cant play the game it will only brick my rig.
Are there any performance differents between the 22.5.1 and newest recommended drivers?

I play alot in VR.
 
Back
Top Bottom