http://bugs.winehq.org/show_bug.cgi?id=59450 --- Comment #13 from Henri Verbeet <hverbeet@gmail.com> --- (In reply to Tony Fabris from comment #10)
However, even though mainline vkd3d 1.18 will "launch" the game with that one-line change, it doesn't render it on the screen at all, I get a fully red screen instead of the game screen. The game's main menu music still plays in the background, so I feel like we're making progress towards getting mainline vkd3d running it.
That's likely to be either from the vkd3d-shader changes, or from disabling VK_EXT_descriptor_indexing. In principle setting the VKD3D_DISABLE_EXTENSIONS environment variable to "VK_EXT_descriptor_indexing" should allow you to disable the extension without modifying the vkd3d source, but if you're worried about CrossOver interfering with environment variables, you can also just add the "vulkan_info->EXT_descriptor_indexing = false;" line to vkd3d_init_device_caps(). (You don't need the condition that limits it to MoltenVK for our purposed here.) The vkd3d-shader changes most likely to matter are those that touch dxil.c and spirv.c, and those depend on the changes to struct vsir_program in vkd3d_shader_private.h. As a first step it may make sense to just apply all the changes to vkd3d-shader, and then just remove things step by step. The other thing to point out is that shader compilation failures should result in a "Failed to compile shader, ..." WARN message from create_shader_stage(), which may help to narrow things down. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.