http://bugs.winehq.org/show_bug.cgi?id=59450 --- Comment #17 from Tony Fabris <tfabris@gmail.com> --- Finally figured out why I couldn't get Wine or vkd3d environment variables to work. Simple syntax problem, either at the shell prompt or inside the bottle's cxbottle.conf. Every example I saw said to set Wine environment variables like this, with spaces and quotes: VKD3D_DEBUG = "trace" Turns out it has to be without quotes or spaces, like this (this one works in cxbottle.conf): VKD3D_DEBUG=trace Similarly for the shell prompt, though at the shell prompt I also had to prefix it with the "export" command or else it wouldn't work. That's also something that everyone omits from all the examples I saw when I was searching for instructions about it. It took Google's AI bot to tell me that, so it's useful for something I suppose. :) So my current situation is: - I can build and test versions of vkd3d from either Crossover or from mainline vkd3d. For crossover, I only have the source code for the version 1.18 included in Crossover 26.0. - So far only the Crossover 26.0 version (with the modified vkd3d v1.18) will run the game at all. Without modification, it hangs frequently, without any console message indicating a crash. If I switch its default console output to VKD3D_DEBUG=trace, the frame timing changes and the game doesn't hang, or hangs very rarely. - Can't figure out how to get mainline vkd3d 1.18 or 1.19 to actually render the game. Without modification, it halts with an error dialog which says "Renderer creation failed. Please ensure your graphics card meets the minimum requirement", but if I modify device.c with the line "vk_info->max_feature_level = D3D_FEATURE_LEVEL_12_2;" it just renders a red screen, even if I port all the changes from the crossover vkd3d-shader over to it. - Haven't tried attaching a debugger to the process yet, looks like that's my next step. I still suspect a memory management or cache management bug, but if so, I'll bet that catching that in the debugger will be tricky. -- 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.