Does anybody know a solution for the broken planets on AMD GPU's when using VR?

Hello there,

i have bought a 7900 xtx amd radeon card to upgrade from my nvidia rtx 3080. But there is an issue when playing elite in vr on amd gpu's since amd made a driver with dx11 optimizations. Since then, the rendering of some planets in vr are broken. now i wonder why amd doesn't want to adress this issue and fix this in a future update. I have tried the latest driver version and cleared the shader cache. but it didn't solve the issue. So my question is does somebody know a workaround fix for this issue? Or could frontier release an update that fixes this problem? I have made a Bug Report in the AMD Software hopefully whether AMD or Frontier knows a solution.

Reddit Thread with Pictures of the problem

Greetings
 
Last edited:
Hello there,

i have bought a 7900 xtx amd radeon card to upgrade from my nvidia rtx 3080. But there is an issue when playing elite in vr on amd gpu's since amd made a driver with dx11 optimizations. Since then, the rendering of some planets in vr are broken. now i wonder why amd doesn't want to adress this issue and fix this in a future update. I have tried the latest driver version and cleared the shader cache. but it didn't solve the issue. So my question is does somebody know a workaround fix for this issue? Or could frontier release an update that fixes this problem? I have made a Bug Report in the AMD Software hopefully whether AMD or Frontier knows a solution.

Reddit Thread with Pictures of the problem

Greetings
No help, but it seems to be a known problem with amd cards and Elite: Dangerous. Sorry.
 
So my question is does somebody know a workaround fix for this issue?
The problem has been acknowledged by FDev, and it looks like some users have have managed to fix the issue by using OpenXR + OpenComposite or downgrading drivers. Please look in the comments of the issue report:


I hope it gets fixed in this months Update 👍
 
Hello there,

i have bought a 7900 xtx amd radeon card to upgrade from my nvidia rtx 3080. But there is an issue when playing elite in vr on amd gpu's since amd made a driver with dx11 optimizations. Since then, the rendering of some planets in vr are broken. now i wonder why amd doesn't want to adress this issue and fix this in a future update. I have tried the latest driver version and cleared the shader cache. but it didn't solve the issue. So my question is does somebody know a workaround fix for this issue? Or could frontier release an update that fixes this problem? I have made a Bug Report in the AMD Software hopefully whether AMD or Frontier knows a solution.

Reddit Thread with Pictures of the problem

Greetings
Does this happen in Legacy as well?
 
If you are using oculus quest 2 / quest pro then for me the fix is using airlink and a lot of other little settings.

First off though make sure you that you are on v53 on the HMD, this might work for you on V51 but V53 definitely works, then ensure that you're subscribed to the beta channel on the windows app, this fixes the limited transfer speeds on AMD devices.

Secondly, if you're on the 7900xtx / xt manually increase your encode width to something decent otherwise you're stuck at the encode bit rate of 2016x1088 since the desktop app does not recognise the new GPU's yet, .I use 3664.

Third switch off HEVC (registry entry set to 0)

Lastly, in the debug tool, add an offset to your dynamic bit rate of 200mbps (don't go too high since there is a limit on the decode side in the headset). I also set dynamic bit rate here of 200mbps which gives me an effective transfer speed of 400mbps.

This fixes several issues off the bat:
the stupid tearing/warping no the right hand side of the screen (using H264 instead of H265)
Fuzzy text / image clarity (the encode width)
being capped at 65mbps transfer speeds (the V53/beta channel + the bitrate offset)
compression artifacts (higher bitrate)

Now lastly use opencomposite for Elite dangerous and the planets/orbit lines will appear properly. Using Virtual Desktop does not work since it uses the Steam OpenXR but for whatever reason I don't get the open composite bypasses this and fixes the problem. As a bonus you get a few more fps since you don't have the overhead of steam anymore!

Apologies if this is unclear, I wanted to avoid a wall of text but this works for me.
 
The problem has been acknowledged by FDev, and it looks like some users have have managed to fix the issue by using OpenXR + OpenComposite or downgrading drivers. Please look in the comments of the issue report:


I hope it gets fixed in this months Update 👍
Hello again,

I would Like to ask If i could use openxr with my valve index. Or did i have to use WMR, Oculus. Headsets? If so, did i have to replace the openvr_api.dll of Elite Dangerous with a modded one? Where did i get this?
 
Ah, yes, OpenComposite isn’t compatible with the Index. Have you tried downgrading your video drivers to 22.5.1 as per some of the report comments?
No i didn't, but i also don't want to do. I don't know if this driver version is even compatible with a 7900 xtx. It looks like i'm screwed now.
 
Last edited:
Hey It seems that the planets were fixed in the Update, i was in a Station near a broken Planet but now the Planet isnt broken anymore. Omg thank you frontier thank you. but now the thargoids destroyed my ship. It went very Bad..Is there a possible solution to avoid Being intercepted while hyperjumping or does someone know a strategy surviving These targoid attacks with a Type 7 Transporter?
 
Last edited:
Hey It seems that the planets were fixed in the Update, i was landed in a Station near a broken Planet but now the Planet isnt broken anymore. Omg thank you frontier thank you.
That’s great news - sounds like the game has been updated to work with the latest AMD drivers.

Hopefully other Team Red VR users can confirm the problem is solved 👍
 
Latest preview drivers have fixed this for me.
Also a very nice improvement in Vr performance.


Haven't tested these in VR yet, so I can't confirm the fix, but the overall performance seems very good on my 6800 XT.

One oddity for tweakers is that there is no SPPT by default with these drivers, so one has to import a saved table from some prior version before being able to tune things with MPT or the like.
 
Back
Top Bottom