A good lead right now is a potential driver bug around indirect count where the indirect count is not clamped to maxDrawCount.
Confirmed with various tests that this is a driver bug, not vkd3d.
I saw 440.66.04 was posted yesterday.. Vulkan beta tho, but probably leaps ahead of 440.58.x series :)
Not really, 440.58.x is quite recent. It's been confirmed to be a driver bug in the NV driver, so probably next beta driver or something will have a fix.
Solved in latest beta driver as of April 1.
Nothing extracted yet.
GTX 1660 Ti, driver 440.58.02.
The game uses vkCmdMultiDrawIndirect and friends, and it renders the wrong data somehow.
Oddly enough, capturing the game with RenderDoc, the game renders fine.
I've tried forcefully adding barriers and waitforidles everywhere to no avail.