A Mesa developer wrote up a blog post about the conformance of the open source Mesa Vulkan driver 'radv' for AMD.
The blog post shows off how well it does, but it also shows radv is far from finished.
From the post where he used the Vulkan test suite:
He also notes that's using some patches from his 'radv-wip-conform branch' on github.
Quite a way to go before supporting all of the Vulkan API, but a fantastic effort from all involved.
One major bit missing from radv currently is tessellation support, something a lot of games need.
It will be interesting to see what AMD do officially, since they were supposed to open source their Vulkan driver too. I really think they will end up just using radv.
The blog post shows off how well it does, but it also shows radv is far from finished.
From the post where he used the Vulkan test suite:
QuoteTest run totals:
Passed: 82551/150950 (54.7%)
Failed: 0/150950 (0.0%)
Not supported: 68397/150950 (45.3%)
Warnings: 2/150950 (0.0%)
He also notes that's using some patches from his 'radv-wip-conform branch' on github.
Quite a way to go before supporting all of the Vulkan API, but a fantastic effort from all involved.
One major bit missing from radv currently is tessellation support, something a lot of games need.
It will be interesting to see what AMD do officially, since they were supposed to open source their Vulkan driver too. I really think they will end up just using radv.
Some you may have missed, popular articles from the last month:
7 comments
Wow, more than 50 % already passing. Didn't know they got along that well in the past month.
1 Likes, Who?
Please note that not every 'Not supported' means that anything is missing. A Vulkan driver needs only to support what is in the hardware (e.g. only the supported image formats) and only what makes sense for the platform (I don't think that 'win32' extensions would ever be supported in radvd).
'Failed: 0' is the most important part of the conformance tests results.
'Failed: 0' is the most important part of the conformance tests results.
1 Likes, Who?
Quoting: JajcusPlease note that not every 'Not supported' means that anything is missing. A Vulkan driver needs only to support what is in the hardware (e.g. only the supported image formats) and only what makes sense for the platform (I don't think that 'win32' extensions would ever be supported in radvd).
'Failed: 0' is the most important part of the conformance tests results.
Indeed, it would be interesting what's actually "not implemented" and what "won't be implemented". Actually, that games already run using radv is a sign that it probably isn't that far from completion.
0 Likes
Quoting: STiATradv doesn't currently have tessellation support, so that's a big thing missing a lot of games need.Quoting: JajcusPlease note that not every 'Not supported' means that anything is missing. A Vulkan driver needs only to support what is in the hardware (e.g. only the supported image formats) and only what makes sense for the platform (I don't think that 'win32' extensions would ever be supported in radvd).
'Failed: 0' is the most important part of the conformance tests results.
Indeed, it would be interesting what's actually "not implemented" and what "won't be implemented". Actually, that games already run using radv is a sign that it probably isn't that far from completion.
0 Likes
Nice. Time to work on performance.
1 Likes, Who?
Hehe, these guys should move to diaspora* from LiveJounrnal. Good work otherwise :)
So what percentage of AMD Vulkan features are still missing in radv then?
Last edited by Shmerl on 20 March 2017 at 3:34 pm UTC
Quoting: JajcusPlease note that not every 'Not supported' means that anything is missing. A Vulkan driver needs only to support what is in the hardware (e.g. only the supported image formats) and only what makes sense for the platform
So what percentage of AMD Vulkan features are still missing in radv then?
Last edited by Shmerl on 20 March 2017 at 3:34 pm UTC
0 Likes
The Mesa folks continue to do a great job! My Amd GPU thanks them!
0 Likes
See more from me