Originally posted by mphuZ
View Post
AMDVLK simply exists for two reasons:
1.) AMD promoted a FOSS driver and due to PR(and some legal issues) they have to provide one, hence this is basically a semi regular code dump to meet that criteria.
2.) AMD has to provide an "Official" driver because there are segments of the market that may require it but those will use AMDVLK from the closed driver(wink wink see my point).
At this point RADV(and bigger optimizations are waiting merge at the time of this post) is superior in every aspect to AMDVLK hence it doesn't make any sense for Valve or anyone else(including AMD) to pour any more effort on AMDVLK than they already have.
Please note that DXVK/D9vk/Valve developers tried at some point to fix issues but the management was not as fluid as Mesa/RADV, AMDVLK is basically FOSS but is managed as a closed release.
About Google Stadia "AMDVLK" i suspect they are using a heavily modified version of AMDVLK(probably the closed one tho) with some special sauce for their special use case.
Comment