Georg Lehmann
Georg Lehmann
Mhm, I guess we can change that, but as far as I understand scanout should ignore alpha. Some game also output non opaque alpha, so if it isn't ignore that...
Looks to me like the main plane should always use XRGB though: https://github.com/Plagman/gamescope/blob/cd31090733c0517ce786bcb32574d42daa81130f/src/drm.cpp#L172-L174 Unless intel doesn't support XRGB at all?
This should be reported to mesa, as far as I know we do everything correctly now. All the validation errors have been fixed.
@vignedev All of that indicates that it's a driver issue, so something that should be reported to mesa.
@patrickaldis There's always the possibility that there's some subtle bug in our code, but given that gamescope works fine on radv I think it's an anv problem. The hacks by...
Can you bisect the issue?
Seems like anv *really* dislikes creating a mutable dmabuf image with bgra8 srgb+unorm. Pretty sure this is a driver issue, you should report it.
anv bug report: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6031
So it's interesting that the game doesn't load d3d*.dll or dxgi but vulkan-1.dll gets loaded. Can somebody make a log with `WINEDEBUG=+vulkan`?
Looks better now, just one thing that you need to pay attention to is that you actually use `vkGetPhysicalDeviceProperties2KHR` for Vulkan 1.0 instances, and not `vkGetPhysicalDeviceProperties2`. I don't think the...