Well... for SC it'll eventually go to Vulkan. I think I'll rejoice when that happens. But for now, cheesey DX11 burps...
Information regarding AMD RX 6000 series driver updates.
- Thread starter sallymorganmoore
- Start date
Every change breaks something.
Statistically speaking, I'd be surprised if dozens of games aren't fixed and broken, with every driver release, even without the signifcant updates that came post-22.5.1.
FDev could have fixed the crashing by changing a single variable in plain text config file.
The shader fix would probably require a little more work, but should have been very doable.
They fixed what was stated (the game crashing), and what was probably in the most popular bug report they got with regard to the game.
However, that wasn't the whole issue, and they probably don't even know about the shader problem that turns everything except a small bar teal, which was always the harder thing to fix.
Yeah... Appreciate the complexity of these things. It's not quite like testing for a console game.
However, they've still gotta put forth the right resources and QA for such products. So, to solve a PART of the above problem you mentioned. This is called regression testing.
Perhaps they did such a thing, but perhaps the sample of games they did it on wasn't sufficient.
Though.. for like 6 months we only had the 22.5.1 driver under WHQL. So... I'm imagining they (AMD) just pushed out revisions over the 6 months times into production and had the end consumer test it for them indirectly, with steaming ears because there were problems now with crashing.
Only thing to do was to just sit on 22.5.1 and hope things get fixed. Cause, we're not paid testers, and a lot of us don't have the time to delve into all this mess.
Elite: Dangerous is a niche game from 2014. It probably hasn't been on AMD's radar since Polaris was new and likely doesn't get any regression testing in normal circumstances. Even after issues were specifically pointed out, they only tested it far enough to fix that specific crashing problem, not far enough to see the other blatant issues that remained.
Still, it's more than FDev has done.
Several post-22.5.1 versions are WHQL. 22.5.2, 22.6.1, 22.10.2, and 22.10.3 are all WHQL. All have the teal overlay, and all but 22.10.3 crash when near planet surfaces if DP floats aren't disabled.
WHQL doesn't mean anything other than it doesn't blatantly misbehave as far as Windows itself is concerned and that Microsoft can now force it down the throats of unsuspecting users via Windows Update.
Anyway, we are getting very near the release of the 7000 series and they will push through a 'recommended' driver for that release, no matter how well it works or doesn't. And I'm not expecting it to address the remaining issues with this game (even 22.5.1 and all prior drivers for RDNA2 have problems with orbit lines that don't exist on other AMD GPUs, or any NVIDIA ones); would be nice, but I'm not expecting it.
Ok. well I guess I take the 'recommended' 22.5.1 driver which was WHQL the last one. Else, why not 'recommended' other drivers that made the WHQL?
Anyways..
Yes, that's the bug the new drivers don't fix.
Either go back to 22.5.1, or spend five minutes setting up 3DMigoto to knock out the offending shader.
Turquoise planet sees through your ship into your soul.
The most jarring thing copying my XBox profile to PC was that even as I revelled in how the game on max settings looks identical between XBox and PC (but runs 80fps smoother), the bizarre moire effect on orbit lines on PC stuck out like a sore thumb. It's like antialiasing is completely disabled just for them.
It is. Well, the very subtle shader AA settings we (FXAA, SMAA, MLAA) have still apply to them (not that it does much), but the separate line specific antialiasing that they should have is just completely absent on RDNA2.
Were orbit lines ever antialiased? I don't remember them being so... but I've played Odyssey with AA off for the past year and a half so I could be misremembering the before times.
EDIT: Just checked some Horizons-era screenshots, and no, they were never antialiased - and I would've played with all graphics settings cranked up back then. Yes they were I am blind.
Last edited:
Mine definitely were, and still are, just not on the RX 6000 series.
It's wild that they're so much smoother on XBox.
Funnily enough, even though the GPU in that is RDNA2. I would surmise due to the game running within an XBox One emulator there?
So… dont buy AMD?
It's not emulated (the XBox runs everything in VM's, but that's not the same thing), and despite XBox system software being based on Windows, it's not quite Windows and doesn't use the same drivers.
If this is the only game you play, you may want an NVIDIA card, or to at least avoid the RX 6000 series, if you don't already have one.
None of the issues with this game, as far as I am aware of, exist on any prior generation AMD parts and there is no way to tell if they'll persist into later generations. The RX 5000 series is architecturally extremely similar to the 6000 series and uses the same drivers packages, but lacks the orbit line AA problems (introduced at the 6000 series launch and never corrected), the DP float crashes (introduced in the May 2022 preview drivers and corrected in 22.10.2), or the teal overlay (introduced at the same time as the crashing, never corrected).
The new driver branch also resulted in problems with a few other games, but I'm extremely doubtful that, overall, AMD is any less compatible than NVIDIA or Intel. NVIDIA does have more detailed release notes, so it's often, but not always less guess work in determining what's broken and what's been fixed. Problems with titles, even fairly popular ones, can also linger on NVIDIA drivers for just as long. For example, the original Witcher (which was more popular than ED ever was) still has problems with lights being visible through occlusions on some of my NVIDIA parts after more than fifteen years.
Basically, everyone sucks, and even if you do your due dilligence to find out who sucks least for what you're specifically doing, you'll likely run into unpleasant surprises sooner or later.
For me it works. I used the cleanup tool from amd and do a fresh install. The 22.11.1 driver runs now fine with ED Odyssey
Prefix: I am not an AMD GPU owner (but considers it given NVIDIA's lack of reasonable pricing) - warning for stupid incoming question
Question: What cleanup tool?
I hope the link will help You.
My english is realy to bad to explain it... This tool works with Win 11 and removes all AMD GPU drivers and settings...
"The AMD Cleanup Utility is designed to thoroughly remove any previously installed AMD driver files, registries, and driver store from systems running Microsoft Windows® 7 and later. The cleanup process includes removing AMD display and audio drivers as well as AMD software components but does not remove AMD chipset driver components such as GPIO, SATA, USB, etc."
I'm not either, and not seeing it happening anytime soon.
No matter how neat was their hardware, their drivers were always lacking - also, the current laptop i own has a ryzen 9 5900hx and runs optimus with an nvidia 3080.
My games do crash quite often if i chose to run them using onboard (cpu) amd gfx (it feels silly to run Catan on 3080 or, fwiw, to run really older games on the nvidia card)
My next laptop will definitely NOT have any type AMD gfx in it cause i'm really sick with Amd gfx driver errors.
And if i will actually chose to get back to desktop, i will get an RTX3080TI or a similarly price/performance ratio card from 4000 series.