AMD had their own implementation of Vulkan (primarily aimed at their Professional cards) called AMDVLK
The rest of the open source community contributes to radv.
AMD doing their official testing and releases on the Vulkan implementation you’re using should help find bugs and they can submit fixes directly to radv
The gap is fairly narrow if you look at mesa-git performance. This is workload dependent but if anything, RADVs trajectory of improvement in RTRT seems great even without AMD’s involvement.
Can someone explain this like I’m an idiot? Is this good for me or bad for me?
Probably good.
AMD had their own implementation of Vulkan (primarily aimed at their Professional cards) called AMDVLK
The rest of the open source community contributes to radv.
AMD doing their official testing and releases on the Vulkan implementation you’re using should help find bugs and they can submit fixes directly to radv
Thank you both for the explanation, all makes sense now!
Good, probably. Radv is generally considered better then amdvlk so having them focus solely on it, I imagine it will only bring good things for it
Except Raytracing where AMDVLK exceeded. Hopefully, Raytracing will improve now that AMD will fully contribute to it.
The gap is fairly narrow if you look at mesa-git performance. This is workload dependent but if anything, RADVs trajectory of improvement in RTRT seems great even without AMD’s involvement.