That may be a ridiculous reason for you, but I'm not you. I became too reliant on those lines for navigation over the years. I've accepted many other changes before this, and finally had to walk away when this became evident. As I stated, it was the last straw (not the first). I wouldn't be here right now if I boycotted ED. On the contrary, I sincerely hope they fix this issue one day. For now, it's unplayable for me.
Information regarding AMD RX 6000 series driver updates.
- Thread starter sallymorganmoore
- Start date
This is absolutely an issue with the game, don't be naive.
I did this yesterday morning, then upgraded AMD drivers to 22.8.1, and everything is stable, from on-foot combat to in-space bumbling about.
An interesting side note is that locking my desktop now leaves the running game in front of the lock screen (until entering the PIN), so it makes for a very visual lock screen for my son while I'm making a coffee!
I did the same thing as KronenBerg and it worked as well for my RX 6950XT with Adrenalin 22.8.1.
It seems to be a valid workaround.
It seems to be a valid workaround.
Are curved lines in supercruise (orbit lines, exclusion zones, etc) still broken wherever they are horizontal or vertical? If this fixes that, I'll be back by the weekend.
This issue isn't limited to Elite Dangerous, so before getting out the pitchforks for Frontier, you may want to look around.
Source: https://www.reddit.com/r/EliteDangerous/comments/wmuxbd/just_confirming_new_amd_driver_2281_still_borks/
Source: https://www.reddit.com/r/EliteDangerous/comments/wmuxbd/just_confirming_new_amd_driver_2281_still_borks/
until more game studios stop drinking the koolaid from Microsoft and implement their games in cross platform-open api's such as vulkan, we'll rely on workarounds like the dxvk and vk3d wrappers to fix things for them. Luckily, those wrappers work pretty well for most games.
Yep, I've been having weird issues all over the place for a couple of months now. I just discovered that the interface for my slicer software (3D printing) is now borked. There are definitely issues with the last couple months' AMD driver releases. If it weren't for NVIDIA's attitude towards Linux, I would have switched back last year (and I'd still be playing ED).
6000 series cards affected, fact.
Fdev not resolved issue , fact.
AMD not resolved issue, also a fact.
I have tested several pre 6000 AMD cards and they work fine, another fact.
Plenty factual evidence available but no desire to resolve them.
I suppose I should have worded my reply differently. It's naive to blame one side specifically without
Edit: The game runs fine without this issue on NVIDIA, fact.
Does that mean it's not the game?
Last edited:
this post is a bit ambiguous on what exactly you would be switching from and to and confusing why the different possible scenarios are keeping you from playing elite.
Just to be clear, in linux, most people dont use amd's drivers in linux. They use the open source mesa driver. The only thing that amd provides is firmware files. And i dont think there have been any issues with this setup (plus the amd driver issue appears to be directx centric as the same drivers outputting the equiv rendering in vulkan appears to work fine). So it would seem like linux would be immune to this issue, or at the very worst, have entirely separate amd driver issues unrelated to this issue.
So if you have amd hardware, you wouldn't need nvidia hardware to play elite without issue in linux, so there would be nothing keeping you from switching now and playing elite.
And if you dont have amd hardware, why would nvidia's horrible open source support and thus being stuck in windows, keep you from playing elite in windows?
I went all AMD with the two PCs I built last year. There is an issue with AA on all lines drawn in space during supercruise. They are severely broken and/or missing wherever they are horizontal or vertical. This makes the game unplayable for me, and it occurs on Windows and Linux.
I've never played with orbital lines enabled and I assume these are the only items impacted because i have not heard of 6000 series having such issues cross-api and shared across open source and proprietary drivers. And i have no issues myself, with my 5700xt with anti-aliasing in elite that haven't always been anti-aliasing issues in elite since launch and aren't specific to amd or nvidia (such just just having crappy anti-aliasing in general).
If you're seeing the issue in open source drivers under vulkan (linux) and proprietary drivers in direct x in windows then I would think that points to the implementation fdev is using to draw to the card being the root of the problem, since it's obvious what they're doing is not optimal in odyssey, so very likely the newer hardware's firmware is less flexible to that abuse. Though there is always a chance at hardware/firmware faults ...you'd think if it were hardware / firmware related the issue would present itself in many other situations. The drawing of just the orbital lines being impacted would suggest an fdev problem. Even if the issue only presents as a problem under 6000 series amd hardware.
my wild guess is that fdev is doing things out of a "proper" order - drawing to the hardware and the newer hardware is optimizing calls differently (maybe it's more strictly enforcing when certain scene level AA processes occur) than previous hardware an this is causing it to be excluded from the AA process that's been chosen.
Driver crashes ..i'd blame amd. But something particular like orbital lines misbehaving, i would blame that on fdev. Really anything AA related i'd first assume Fdev is doing it wrong since they've never had proper AA working in elite.
People seem to keep saying they don't want to downgrade their drivers because of the performance improvements in the newer ones, not realising that those improvements come from cutting corners...
Interesting, do you have any info that supports this claim?!
It can be both problems from fdev and AMD! AMD Drivers are in fact known to sometimes be buggy, but fdev is also... well, fdev
Oh yes, that's a fact, but they are mostly for new games, or more recent games, Elite is kind of oldish without many updates, and it's a very specific issue, like.. .going onto a planet, honestly if it was entirely AMD's fault, it would occur in other places (most likely), but at the same time, fdev completely ignoring us, it's pretty much what you say about AMD as well!
I for one, am not gonna rollback, the workaround I posted on the previous page seems to be working for the time being (although not in VR I guess). So until there is any update from either parties, you either rollback, or use the workaround.
I for one, will go the workaround way (for now), I play other games as well, and I'm totally not gonna sacrifice better performance/features for any specific game!
Planet/terrain generation relies very heavily on the GPU via compute shaders, using them to a much larger extent than most games.
Instead of the details of the entire planet's surface being stored in a database somewhere and being sent over the network every time someone visits it, the game feeds the planet's "seed" into the generator and the GPU does all the work to calculate the terrain. Something is going wrong during that generation with the newer AMD's drivers (either it's returning values out of range or perhaps the game is using some sort of checksum to ensure all players see the same terrain, and there are inconsistencies) causing the game to throw Orange Sidewinders.