Quoting: yar4eAwesome news!!! My wife is waiting for Witcher 3 will be fully playable in Linux for very long time now

So is mine ;)

Hopefully now @YoRHa-2B can focus on completing those workarounds :)

Quoting: ShmerlHopefully now @YoRHa-2B can focus on completing those workarounds :)

Did he ever specifically say that they were "workarounds"? Maybe he has access to something that is not public yet and simply needs to wait until it is.

Quoting: Ehvis

Quoting: ShmerlHopefully now @YoRHa-2B can focus on completing those workarounds :)

Did he ever specifically say that they were "workarounds"? Maybe he has access to something that is not public yet and simply needs to wait until it is.

https://www.gamingonlinux.com/articles/valve-officially-confirm-a-new-version-of-steam-play-which-includes-a-modified-version-of-wine.12400/comment_id=131679

I'll just leave this here:
https://github.com/KhronosGroup/Vulkan-Ecosystem/issues/26#event-1806602576

"Resolving inside Khronos"

Yeah, he said they are workarounds. Resolving inside Khronos is great, it means things are moving forward for Vulkan itself at last. But until that's done and actual spec is released and then drivers implement it, might take quite a while. May be workaround will be available sooner :)

Did he use the word "workarounds" anywhere? I could only find something less specific. If it was a workaround, it could have been pushed into a branch already. It's entirely possible that he has access to preliminary stuff. With Valve employing driver devs, there could also b e an internal preview version of a new extension that he used to implement it. In fact, the quote linked above explicitly says he didn't work around it. Since he did post a picture, I'm leaning to him having access to things that aren't public yet.

See here. From it, it sounded like he didn't solve the problem, but somehow just made it look good even with it.

Unless what @YoRHa-2B meant that he actually collaborated with Vulkan driver team to use an experimental not in spec feature to implement it, and then submitted it to the Khronos group as a proposal. That would have been cool. But this process is not public, so it's hard to know what that meant.

Progress confirmed for EXT Vulkan extension:

QuoteSome members of the Vulkan working group are developing a multi-vendor EXT extension for transform feedback with the primary goal of satisfying the needs of the DXVK, vkd3d and ANGLE translation layers. The Vulkan working group does not plan to promote this functionality as a KHR extension or as core functionality because it believes there are better, more forward-looking ways of processing and capturing vertex data with the GPU. The multi-vendor EXT extension should be available soon and is likely to be implemented on those platforms where DXVK, vkd3d and ANGLE translation is required.

Pretty much as I expected. Not including it in the core specification sounds reasonable. But since Khronos was always working towards API translation, having an extension specifically used for that was something they had to do.