AMD RX 6000 series driver issues & workarounds

No change with 22.11.1.

Wasn't expecting a fix for the shader overlay problem, but I did have a small hope that the fix for missing prediction lines in World of Warships was non-specific enough to help the aliasing on orbit lines in Elite, but no dice.
Thanks for saying that. I was wondering.
 
It seems I am struggling to apply fix #2 on Epic EDO installation. Have anyone of you managed to apply this fix with Epic?

I am currently at 22.11.1 drivers (so no fatal crush, just faulty shader) , followed the instruction from the first page by copying d3d11.dll, d3dcompiler_46.dll and d3dx.ini (after renaming) into the Epic installation directory. Started EDO - faulty shader is still applied.

Possible reason: there is no EliteDangerous64.exe file in C:\Program Files\Epic Games\EliteDangerous directory. There is EDLaunch.exe though. Couldn't find EliteDangerous64.exe anywhere in my system.

I don't have AppConfig.xml in this directory because I didn't have to overcome the fatal crashes as my drivers are already patched.

Is it possible the instruction does not cover all the required steps? Do I have to run 3DmigoDo in any way? Or are those dlls automagically included when EDO is being run?
 
It seems I am struggling to apply fix #2 on Epic EDO installation. Have anyone of you managed to apply this fix with Epic?

I am currently at 22.11.1 drivers (so no fatal crush, just faulty shader) , followed the instruction from the first page by copying d3d11.dll, d3dcompiler_46.dll and d3dx.ini (after renaming) into the Epic installation directory. Started EDO - faulty shader is still applied.

Possible reason: there is no EliteDangerous64.exe file in C:\Program Files\Epic Games\EliteDangerous directory. There is EDLaunch.exe though. Couldn't find EliteDangerous64.exe anywhere in my system.

I don't have AppConfig.xml in this directory because I didn't have to overcome the fatal crashes as my drivers are already patched.

Is it possible the instruction does not cover all the required steps? Do I have to run 3DmigoDo in any way? Or are those dlls automagically included when EDO is being run?
Try C:\Program Files\Epic Games\EliteDangerous\Products\elite-dangerous-odyssey-64
 
Try C:\Program Files\Epic Games\EliteDangerous\Products\elite-dangerous-odyssey-64
Spot on. I found this folder when looking for GPUWorkTable.xml file location. Not sure why EliteDangerous64.exe could not be found by Windows file system search though...

Either way, thank you @DrinkyBird for helping me out and most importantly to all the people finding this solution. I salute you :)
 
Windows File Explorer is fine for searching via file names, but for files contents I use AstroGrep, especially because I don't run the Windows indexer.
 
Windows File Explorer is fine for searching via file names
It really isn't, searching for EliteDangerous64.exe takes several minutes for me - and that's when I just search the SSD it's on...
Meanwhile the tool Everything takes several seconds to index the names of all 5.5 million files on my entire machine, and after that searching by filename is literally instantaneous.
for files contents I use AstroGrep, especially because I don't run the Windows indexer.
For that I just open a Git Bash shell in the folder I want to search and use regular old GNU grep.
 
Back
Top Bottom