AMD RX 6000 series driver issues & workarounds

Hey folks, hopefully someone can help me out here. I followed @Morbad directions to remove the green banding which i thought i did to the letter but now my game is crashing on launch and I cant figure out why

Edit: crashes on launch in VR but the game will launch normally without vr albeit without the issue being fixed.

313011760_1121210925427883_7170106848421572687_n.png
 

Attachments

  • 313011760_1121210925427883_7170106848421572687_n.png
    313011760_1121210925427883_7170106848421572687_n.png
    46.9 KB · Views: 82
Last edited:
Thanks for the reply Morbad

Iv attached the log, appreciate any help

"Error opening C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous\Products\elite-dangerous-odyssey-64\d3dx.ini"

Same problem AdAstra was having on the prior page. I think it's probably a path or permissions issue, but I don't use Steam and cannot reproduce it myself.
 
"Error opening C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous\Products\elite-dangerous-odyssey-64\d3dx.ini"

Same problem AdAstra was having on the prior page. I think it's probably a path or permissions issue, but I don't use Steam and cannot reproduce it myself.
No problem, thanks for taking a look all the same. Iv rolled back the driver for the time being
 
No problem, thanks for taking a look all the same. Iv rolled back the driver for the time being

You could try moving the file, creating a new text file in the game directory, pasting the contents from the original into it, saving it, and naming it d3dx.ini to see if it's a permission issue. Should either start, or throw the same error if it doesn't work, irrespective of driver version...so you can test it without swapping back to the new driver.
 
I am with the latest AMD drivers, and the game does not crash on the planets but I have the green color problem on the scanned planets.
I'm not going to make any changes to the game files ...
It's not fair that I have to do it, the game developers or AMD have to think about it.

This thing from my point of view has been going on for too long now ...

Srry for late reply, have some minor stuttering with 22.5.1 but overall I've got great FPS, think I'm gonna to stay until Frontier fix this and Recommended AMD Adrenalin driver

Wondering if Resizable BAR can cause some stuttering/flickering?

Kind regards
/e33et
 
Last edited:
Hey Cmdrs, I tried workaround #2 but am having the same issue as AdAstra and Nevioni, an error opening the d3dx.ini. I tried recreating the file by copying over the text within your attached version to a new text document but no dice. Am I better off using the EDHM fix?
 
Hey Cmdrs, I tried workaround #2 but am having the same issue as AdAstra and Nevioni, an error opening the d3dx.ini. I tried recreating the file by copying over the text within your attached version to a new text document but no dice. Am I better off using the EDHM fix?
They are practically the same thing, both EDHM and #2 use the migoto way. Migoto uses d3dx.ini for settings. Check the file security persmissions, your windows user should have full control over it.
Edit: are you sure you've set the File Explorer View Options to show extensions for known file types? to make sure that the d3dx.ini is actually "d3dx.ini" and not "d3dx.ini.txt" (if extensions are hidden)
 
Last edited:
Also for workaround #2:

If EDHM is properly installed for Odyssey (it changes hud and menu colours and all that jazz) (easiest way is to use EDHM_UI: https://github.com/BlueMystical/EDHM_UI/releases/tag/v2.1.31)

Then you can skip the steps in workaraound #2 concerning downloading and installing 3dmigoto and just put the lines for the shader bypass into the d3dx.ini that got installed with EDHM and then continue with the step where you need to modify the AppConfig.xml by setting "PermitNativeDoubles="false"".

Pro about that one is we can keep the custom EDHM colours that anyone that uses that mod has grown accustomed to while on newer drivers, and the num block doesn't get overtaken by the 3d migoto shader skipping controls that I used to find which shader was the culprit.
Where in EDHM's d3dx.ini would I enter the lines of text from Morbad's?
 
Hey folks, hopefully someone can help me out here. I followed @Morbad directions to remove the green banding which i thought i did to the letter but now my game is crashing on launch and I cant figure out why

Edit: crashes on launch in VR but the game will launch normally without vr albeit without the issue being fixed.

View attachment 330939
Your D3dx.ini file still has the .txt extension, it should look like this:
d3d.png


You will need to show file extensions:
menu.jpg


From the View option.

Your D3Dx.ini will read D3Dx.ini.txt - just delete the .txt and save. All should be well.
 
There is another possibility. When you download the file, the built in windows security blocks it by default. You have to unblock it (after you rename it to d3dx.ini).
View attachment 331304

Yeah that's also a possibility, though creating a new file and manually pasting in the contents should eliminate any chance of any security or permissions issues.

Anyway, these problems have been enlightening, if only to show me how disconnected my experience is from the typical PC user. I never would have considered not disabling "hide known extensions", not checking for log files after an error, or not double checking security permissions for something I downloaded.

To think, we've had people do multiple driver reinstalls because they didn't see a file extension...
 
For non-VR setups, Workaround #2 involves editing a single variable in a text file and putting three files in the game directory. If you figured out how to install the game, this should not be difficult.
As a customer I should not have to make changes to folders or files. To install the game all I had to do was select it from steam and that was it. I have no idea what to do with folders or files. All I know is what I learned about computers in the 90's.. mess around with folders and files things will get really messed up so don't do it...
All that I want is my money's worth for both purchasing a game and purchasing a GPU. Its the job of the makers to produce and fix, not mine.
If it really is easy and takes 5min to do...then why have AMD or Frontier not done that?
 
Did I misunderstand or didn't AMD do a massive rewrite of their DX11 driver? If so it seems normal that it would break some games?
 
Back
Top Bottom