http://bugs.winehq.org/show_bug.cgi?id=59450 --- Comment #35 from Tony Fabris <tfabris@gmail.com> --- Henri, thanks again for your excellent sleuthing and suggestions. Zeroing in on that variable was a stroke of genius. As I promised in my prior comment, I've done more testing (aka, playing the game a bunch) and I'm pretty confident about this now: Hang bug no longer repros after hours of play: export MVK_CONFIG_SYNCHRONOUS_QUEUE_SUBMITS=1 Hang bug repros at the same frequency as before: export MVK_CONFIG_SYNCHRONOUS_QUEUE_SUBMITS=0 And since, before I knew about that variable, the hang bug repro'd without that variable being set at all, I wonder if that means (as I discussed in my prior comment) that the value is defaulting to 0 on my system, even though my system is higher than version 10.14, so it should have defaulted to 1? Of course, the version of MoltenVK that's having the issue is the one that came with Crossover 26.0, which (I think?) differs significantly from the one on GitHub, at least with regard to the handling of the synchronous queue submits. I suspect that, in the Crossover version, the function "mvkOSVersionIsAtLeast()" is the thing that's doing me dirty here. I don't think it's the fault of the folks at https://github.com/KhronosGroup/MoltenVK in this case, because their version on GitHub just hard-codes that variable's default value to 1 without any version check. Henri, do you have any way of confirming that stuff above and in my prior comment? For instance, do you have access to the internal git system at CodeWeavers, so you can Git Blame to find out who's responsible for that version check in the Crossover build, and ask them about this? -- 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.