Test `test_hull_shader_punned_array()` currently emits this validation error:
```
VUID-RuntimeSpirv-OpEntryPoint-08743(ERROR / SPEC): msgNum: -1986897773 - Validation Error: [ VUID-RuntimeSpirv-OpEntryPoint-08743 ] Object 0: handle = 0x270000000027, type = VK_OBJECT_TYPE_SHADER_MODULE; Object 1: handle = 0x280000000028, type = VK_OBJECT_TYPE_SHADER_MODULE; | MessageID = 0x89925893 | vkCreateGraphicsPipelines(): pCreateInfos[0] (SPIR-V Interface) VK_SHADER_STAGE_TESSELLATION_CONTROL_BIT declared input at Location 2 Component 3 but it is not an Output declared in VK_SHADER_STAGE_VERTEX_BIT. The Vulkan spec states: Any user-defined variables shared between the OpEntryPoint of two shader stages, and declared with Input as its Storage Class for the subsequent shader stage, must have all Location slots and Component words declared in the preceding shader stage's OpEntryPoint with Output as the Storage Class (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.ht…)
```
It might or might not be related to this MR, I haven't debugged yet.
--
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/537#note_64015
This applies on top of !672, the last three commits belong here.
Here we compute additional "synthetic" loops that will be used to implement non-trivial forward edges using (possibly conditional) `break` instructions.
--
v2: vkd3d-shader/ir: Sort loop intervals.
vkd3d-shader/ir: Generate synthetic intervals for forward edges.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/698
Fix a regression from "bb496ea8 - server: Always queue mouse messages delivered to another window."
Fix ETHER VAPOR Remaster (214570) launches to black screen when the cursor is in the game window.
The game calls ReleaseCapture() when handling WM_MOUSEMOVE. After bb496ea8, WM_MOUSEMOVE is always
queued because the message window is NULL. So ReleaseCapture() ends up queuing another WM_MOUSEMOVE.
So the game ends up handling infinite WM_MOUSEMOVE messages at startup and is not able to do anything.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/5263
--
v3: win32u: Move D3DKMT vulkan implementation out of winex11.
win32u: Open adapters in NtGdiDdDDIEnumAdapters2 outside of the display devices lock.
win32u: Move D3DKMTSetVidPnSourceOwner / D3DKMTCheckVidPnExclusiveOwnership out of winex11.
win32u: Move D3DKMT functions to a new d3dkmt.c source.
https://gitlab.winehq.org/wine/wine/-/merge_requests/5220
This applies on top of !672, the last three commits belong here.
Here we compute additional "synthetic" loops that will be used to implement non-trivial forward edges using (possibly conditional) `break` instructions.
--
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/698
On Fri Mar 8 09:47:03 2024 +0000, Giovanni Mascellani wrote:
> Yeah, right. Even for SM6 the current code is likely to produce bad
> results, because AFAIU many signature elements can be merged in a single
> one using `register_count`. I think the appropriate action right now is
> to emit the signature only for SM4-5, and leave the rest to the future
> if the need will arise. I will submit a MR for that.
Mmh, I'm probably confused about SM6. At least for the moment these metadata are meant to represent whatever is stored in the DXBC container, so it shouldn't change anything with SM6. I'll just disable for SM1-3.
--
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/553#note_63977
On Fri Mar 8 09:47:03 2024 +0000, Henri Verbeet wrote:
> Should we output input/output signatures for d3dbc shaders? Currently we
> do, and there's something to be said for that, but it does complicate
> things in a couple of ways:
> - We wouldn't be able to assemble such signatures in any meaningful
> way for d3dbc targets. I.e., the assembler would largely just have to
> ignore them.
> - The register names are slightly different. E.g. ps_2_0 has t#
> texture coordinate inputs and oC# colour outputs.
Yeah, right. Even for SM6 the current code is likely to produce bad results, because AFAIU many signature elements can be merged in a single one using `register_count`. I think the appropriate action right now is to emit the signature only for SM4-5, and leave the rest to the future if the need will arise. I will submit a MR for that.
--
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/553#note_63974