6750XT no antialiasing

[mLine]

Since my upgrade from RX 580 to RX 6750 XT, models and orbital lines have massive flickering. It seems there is no antialiasing. I cant play this game anymore because this flickering makes me sick.
It occures with all settings, but is a little bit better with Ultra and AMD FSR disabled (minute 1:44) but model edges and orbital lines still flickering. Also the light from suns flicker (i think also because the ship edges arnt smooth)

It seems i am not the only one with this problem (radeon series 6000 bug). Why is there no fix?

Maybe some video quality got lost because of the compression but problem is still visible

Source: https://youtu.be/4wE3uLPrlIY

 

[STRONTIUM DOG]

some amd cards have always had orbit line rendering probs it seems https://forums.frontier.co.uk/threads/orbit-lines-rendering-issues-with-a-radeon-6800.584059/

 

[mLine]

some amd cards have always had orbit line rendering probs it seems https://forums.frontier.co.uk/threads/orbit-lines-rendering-issues-with-a-radeon-6800.584059/

Yeah. Like i wrote...

It seems i am not the only one with this problem (radeon series 6000 bug). Why is there no fix?

 

[]M[]

Since my upgrade from RX 580 to RX 6750 XT, models and orbital lines have massive flickering. It seems there is no antialiasing. I cant play this game anymore because this flickering makes me sick.
It occures with all settings, but is a little bit better with Ultra and AMD FSR disabled (minute 1:44) but model edges and orbital lines still flickering. Also the light from suns flicker (i think also because the ship edges arnt smooth)

It seems i am not the only one with this problem (radeon series 6000 bug). Why is there no fix?

Maybe some video quality got lost because of the compression but problem is still visible

Source: https://youtu.be/4wE3uLPrlIY

Similar issues, having gone from an RX 580 to a 6750 XT - apparently it’s a known issue wth 6xxx GPU’s that’s unlikely to be fixed…

It appears that RX 6000 series cards just don't handle AA properly in DX9 games. Frontier doesn't seem interested in updating to a newer DX version, and I doubt AMD is going to make changes for something as outdated as DX9. I've added a post to the tracker with a link to the article I found. There isn't much information in the article, but that scenario would explain why this has been an issue for so long.

I'm currently re-installing ED Horizons to see if it's playable on my 4K monitor. I only had a 1080 monitor to work with on my last test. It might take awhile to get my HOTAS setup again. I'll reply back ASAP with my results.

 

[mLine]

Sooooo... no fix for a year for current hardware. Also no more console support. Thats sad. Seems like ED is slowly dying. Luckily i spend no more money on odyssey

o7

 

[Morbad]

Elite: Dangerous has been D3D11 since 2016. It's not an API issue it's a line AA specific issue with the combination of this particular game and RX 6000 or later AMD GPUs. Wouldn't hold my breath for any official fix from either Frontier or AMD.

As a partial workaround, you could try this, which was mentioned in another thread.

 

[Fixitman]

Elite: Dangerous has been D3D11 since 2016. It's not an API issue it's a line AA specific issue with the combination of this particular game and RX 6000 or later AMD GPUs. Wouldn't hold my breath for any official fix from either Frontier or AMD.

As a partial workaround, you could try this, which was mentioned in another thread.

The issues go well beyond ED. Just one example is FreeCAD. It can't be used fullscreen with a 6000 series card, as it will freeze up. The widget at the top-right of the main window doesn't work properly with these cards either.

The only real fix I found was expensive. My new 3080 Ti is working great, and takes up much less space. For me, the RX 6900 XT was a waste of money. I'll never get more than 20% of my investment back, so on the shelf it goes. I'll eventually upgrade to a newer card so I can put the 3080 Ti in my HTPC. Once that's done, I'll have an RX 6650 XT on the shelf too.

The way I see it (as an automotive tech), AMD cards are like real-world implementations of the fast and furious. They just slap something together, and make it go fast. It's going to be obnoxiously loud (hot), and it's probably going to break, but it goes fast. That's OK for someone who is into that. As my sig states, I prefer quality over quantity.

 

[Morbad]

The issues go well beyond ED.

I'm talking about the line AA issue, which is something I haven't seen or heard of anywhere else...not that I'm ruling out the possibility.

There are other bugs with other programs. Always has been, always will be, and AMD has no monopoly here.

The way I see it (as an automotive tech), AMD cards are like real-world implementations of the fast and furious. They just slap something together, and make it go fast. It's going to be obnoxiously loud (hot), and it's probably going to break, but it goes fast. That's OK for someone who is into that. As my sig states, I prefer quality over quantity.

A handful of personal anecdotes doesn't imply a broader trend. Overall, it's been a very long time since I've considered AMD to be the lower quality choice, if ever.

Just one example is FreeCAD. It can't be used fullscreen with a 6000 series card, as it will freeze up. The widget at the top-right of the main window doesn't work properly with these cards either.

Out of curiosity, I tried FreeCAD on my wife's system, which also has an RX 6900 XT in it, and I could not reproduce these issues. The app runs full screen just fine and the navigation widget appears to work normally. This is the newest release version of FreeCAD on Windows 10 22H2 with the 23.4.1 AMD drivers.

I'm not very familiar with FreeCAD, so maybe it's some specific model or add on you're using, but I can't find any issues playing around with the samples.

 

[Fixitman]

Out of curiosity, I tried FreeCAD on my wife's system, which also has an RX 6900 XT in it, and I could not reproduce these issues. The app runs full screen just fine and the navigation widget appears to work normally. This is the newest release version of FreeCAD on Windows 10 22H2 with the 23.4.1 AMD drivers.

I'm not very familiar with FreeCAD, so maybe it's some specific model or add on you're using, but I can't find any issues playing around with the samples.

That issue must have been fixed in the later drivers then. I never updated past 22.5.1 because every driver update seemed to cause more issues. Everything else I stated was opinion based on personal experience. I have no issue with their hardware, as it seemes to be quite stable. Their drivers are another story IMO. I personally have no desire to utilize AMD GPU's going forward.

 

[Morbad]

That issue must have been fixed in the later drivers then. I never updated past 22.5.1 because every driver update seemed to cause more issues. Everything else I stated was opinion based on personal experience. I have no issue with their hardware, as it seemes to be quite stable. Their drivers are another story IMO. I personally have no desire to utilize AMD GPU's going forward.

Even the most expansive degree of personal experience is will be a comparatively small sample size that barely scratches the surface. It's one thing to identify and attribute a cause to the issues that one is experiencing--though I'm inclined to believe that many problems attributed to drivers have little or nothing to do with drivers--and quite another to make sweeping generalizations about driver quality from a small number of examples.

The only quantitative evidence that really exists for AMD's relative driver quality either comes from AMD themselves (which, even if the literal truth, is still going to be spun and presented in the best light possible, not to mention prone to sampling bias), sponsored independent audits (usually narrowly focused, to make the testing practical), potential surveys of bug reports on AMD and NVIDIA's forums (which are both flooded with constant streams of complaints that could easily lead to confirmation biases if one isn't careful), and a variety of generally non-public error report statistics (making them hard to use).

As for the post 22.5.1 drivers, there does appear to have been an unusually large number of new bugs, largely due to the major overhaul to the D3D11 driver at that time, but there is very little to suggest that problems were being introduced at a higher rate than they were fixed. It's unlikely such a hypothetically flawed driver branch would have been released so late in the RDNA2 life cycle, more than a year after most reviews were old news, as AMD would have had to have known that any negative publicity would outweight any potential performance increase. There was also an even more major overhaul to AMD's OGL drivers in 22.7.1; it would have made a lot of sense to try updating to that branch (or the 23.3.1 version, which fixed certain issues known to have been introduced with 22.7.1) if one suspected a driver issue with an OGL apps on a prior version.

Anyway, I'm not telling you what GPU to purchase. Indeed, generally recommend NVIDIA for this particular game because there are long-term unresolved issues with how AMD handles it (the orbit/gravity line AA problems that prompted the OP to create this thread, as well as some VR issues). Even beyond this title, there are countless objective, factual, reasons why one might prefer NVIDIA. I'm just pointing out that your opinion on AMD's wider driver quality doesn't have a whole lot of basis.

 

[Fixitman]

I'm just pointing out that your opinion on AMD's wider driver quality doesn't have a whole lot of basis.

That's why I stated these are my opinions, based on personal experience.The facts are too muddy these days, so that's all I have. I apologize if f I didn't clarify that well enough.

Also: I do want to tell you I appreciate the information you provide. If I ever seem to be arguing with you specifically, it's not intentional. My social skills are very lacking in person, and they are worse in text. Misunderstandings are a constant and unavoidable part of my life.

 

[mLine]

The issues go well beyond ED. Just one example is FreeCAD.

No issues here with other Software. But i have dualboot and use - for example - freecad on ubuntu.

there are long-term unresolved issues with how AMD handles it (the orbit/gravity line AA problems that prompted the OP to create this thread, as well as some VR issues)

I used a RX 580 before (pre odyssey). No issues apart from overall low performance (could barely reach stable 75fps with high settings).
Im pretty sure its not a AMD driver thing

So many other - even much more performance hungry and complex - games working great and without any problems

 

[Morbad]

I used a RX 580 before (pre odyssey). No issues apart from overall low performance (could barely reach stable 75fps with high settings).
Im pretty sure its not a AMD driver thing

Drivers may be unified into a single package, but at a functional level they still target specific architectures. If it's not a driver related issue, then there is something specific to RDNA 2/3 hardware that impacts Elite: Dangerous' line AA.

Note, this doesn't absolve Frontier either. Just as with the shader compile/crashing issue previously, it's hard to separate the application and the driver. If the application adhered to API standards, there wouldn't have been an issue. If the driver didn't change how it worked, there wouldn't have been an issue.

So many other - even much more performance hungry and complex - games working great and without any problems

Many of which need application specific workarounds in drivers to function. That's why drivers have application specific profiles.

I'll use NVIDIA's drivers as an example as I'm sitting at a system with an NVIDIA card (AMD does the same sort of thing). There are nearly seven-thousand application specific profiles in the drivers I am currently using (I dumped the whole list with nvidiaprofileinspector and used Notepad++ to count instances of "EndProfile"), and many of these applications wouldn't work correctly, or at all, without the specific workarounds contained therein. Redfall is a modern example...it experiences intermittent crashes on any NVIDIA driver that predates the drivers with 'game ready' (application specific) support. Is the software buggy? Is the driver buggy? Who can say? It's very probably both.

If everyone adhered perfectly to API standards and reference renderer defaults, there would be no need for any application specific tuning, nor even a need for more than one or two drivers per hardware generation. However, both games and GPU drivers collections of hacks and shortcuts, seeking to maximize performance and account for the other guy's screw ups at the same time. It's a constant tug of war, complicated by everything's complexity.

I'm reasonably confident that this line AA issue could be addressed in drivers, unilaterally, by AMD. I'm just as confident that Frontier could address this line AA issue with a game patch, irrespective of AMD.