Check out our Monthly Survey Page to see what our users are running.
We do often include affiliate links to earn us some pennies. See more here.

Feral about AMD driver support

By - | Views: 15,709
Reading through the Feral Interactive Facebook page, I stumbled upon this post, which is the most elaborate about the topic by Feral I know of about AMD support.

QuoteWe can also pass your query on to our devs in the hope one of them has a moment to answer, and we were lucky enough to snag a bored one on his lunch break. So here goes:

At Feral we target three different vendors on two different platforms so we have experience working on six different possible card and driver combinations (not counting the OpenSource AMD drivers which would make seven). This means we spend a lot of time working on code that is portable and can support specific options to work around around limitations on all the various hardware and software combinations when various setups are detected.

When asked, we've always been open about our support for different vendors and the reasons behind the support or lack of it. With recent games we have taken a large leap forward in the complexity of the title, meaning even on minimum settings features available in OpenGL 4.1 or in some cases 4.3 are requirements to be able to even load on the minimum settings.

This has meant we have been pushing the newer and less tested areas of the drivers to the maximum and unfortunately this means that in some cases we find either missing features (in the case of the MESA drivers) or some driver issues that need to be addressed which has been the case on AMD.

The actual issues we find are always interlinked and not as simple as X doesn’t work, but usually more subtle. E.g. in this specific instance of this spec this feature doesn’t work as intended, or when running feature X and feature Y at the same time then side effect Z will happen, so it’s not something simple that can be listed in bullet points. We are and always have been committed to supporting all vendors devices when possible and that goal has not changed.

However, as the MESA driver fix list is open and you seem to be interested in the technical side of things, here's an example of an issue we found in drivers that has been fixed but prevented a game we are working on from rendering correctly: Link

The source of the quote can be found under the question of Steffen Wnkr on this page: Article taken from
The comments on this article are closed.
Page: «2/2
  Go to:

Eike Dec 7, 2015
View PC info
  • Supporter Plus
Quoting: maodzedunHowever, the real blame lies with developers who go the quick and dirty route instead of writing clean code, which results in unplayable performance in on AMD and Intel and nerfed on Nvidia.

How many professional game implementations did you check to make these claims?
Because I'm sure at Feral they did check some.
Pecisk Dec 7, 2015
This is the case where I can fully agree that bringing in Vulkan will help. This situation sucks, but overall it is hard to put all blame on one part of puzzle. I hope this clears out as we get engine Vulkan supports appearing and OpenGL legacy code updated to handle issues with workarounds.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone with no article paywalls. We also don't have tons of adverts, there's also no tracking and we respect your privacy. Just good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.