On Fri Jul 31 17:40:57 2026 +0000, Brendan Shanks wrote:
I understand the principle, but in practice it feels like a regression. Currently it’s common for Wine to use MoltenVK directly without the loader (CrossOver does, I believe @Gcenx’s builds also do), this results in apps using MoltenVK whether they opt-in to portability or not. With KosmicKrisp becoming an option using the Vulkan loader will be common, and it’s unfortunate if using MoltenVK with the loader requires extra configuration or out-of-tree patches vs. the current status quo of using it directly. In addition, are there any Windows Vulkan apps/games that opt-in to portability? I thought it basically exists only for MoltenVK, in that case I wouldn’t expect any Windows app (other than Wine’s own components) to ever specify it. Requiring applications to opt-in when we know that none do or ever will feels like correctness to a fault. So what was the point of MoltenVK actually using this flag as intended in the first place, then?
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/11538#note_147503