Yeah I don’t think I’ve had a single crash with the mesa drivers after my overclock was dialed in. And I’ve ran some pretty janky stuff (like my vega 56 that was flashed with a 64 bios).
Yes, personal experience, but also from benchmarks, the open source mesa drivers are just faster at this point, unless you’re turning on raytracing in everything.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Why would you use the official ones? Mesa is better
Yeah I don’t think I’ve had a single crash with the mesa drivers after my overclock was dialed in. And I’ve ran some pretty janky stuff (like my vega 56 that was flashed with a 64 bios).
Are you talking from personal experience? If so, I might give them a try.
I tought AMD official drivers where the best option for graphics and performance.
Yes, personal experience, but also from benchmarks, the open source mesa drivers are just faster at this point, unless you’re turning on raytracing in everything.
Nah, I may play around with raytracing in the future, but it’s not a must for me.
Well, I will give the open source drivers a try, thanks.
How is ROCm these days? I remember needing the official AMD drivers for OpenCL stuff a while ago and ROCm was in very early development.
For ROCm you need the official drivers. For OpenCL, RustiCL (OpenCL implemented over Vulkan) works perfectly for me.