http://bugs.winehq.org/show_bug.cgi?id=59450 --- Comment #10 from Tony Fabris <tfabris@gmail.com> --- Tried so far: In the Crossover version of vkd3d 1.18, I tried setting the debug level back to the default level of "fixme" and adding these lines at the beginning and the end of the d3d12_command_list_ResourceBarrier function: FIXME("****** START d3d12_command_list_ResourceBarrier ******\n"); FIXME("****** END d3d12_command_list_ResourceBarrier ******\n"); The reason I did them at fixme level instead of trace level was so that I could hopefully induce the hang more often. These lines indeed show up on my console outuput, but they show up as often as the other trace messages did, so the continuous console spew still slows down the game's framerate, thus, as before, preventing a repro. In the Crossover version of vkd3d 1.18, I tried confirming that "vk_info->max_feature_level " is the reason that Crossover runs the game and Mainline vkd3d doesn't. Indeed, this seems to be true: setting the Crossover version back down to the same version as mainline vkd3d 1.18 (D3D_FEATURE_LEVEL_11_0) does produce the dialog box, and setting the mainline vkd3d 1.18 version to D3D_FEATURE_LEVEL_12_2 does allow the game to launch. (By the way, the dialog box in question is the one that says "Renderer creation failed. Please ensure your graphics card meets the minimum requirement".) 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. My next task will be trying to build the latest build of mainline vkd3d (1.19 or newer) and see if a simple change to max_feature_level will let it launch the game. However I can't download its source code from git because, purely by coincidence, the web site hosting the latest code (codeberg.org) is down right now. Sigh. I'll try again later. :-) In the meantime, I'll go back to the Crossover version with the messages on the d3d12_command_list_ResourceBarrier function, and see if a longer play session will induce the bug. -- 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.