CrossOver Support - Community Forums

As stated in another post about the login freeze and some other issues I have received a response from tech support please see below. The advice helped get my version up and running again:

From Codewavers Tech Support:

"Hello,

Apologies for the delay as we have been out because of the holidays here. Our own testing and the reports of our users have been that Diablo IV is working with D3DMetal and ESync enabled. The behavior you are experiencing here is not what we have seen reported.

If you try to launch the game while your Mac is connected to a mobile hotspot, do you experience any different behavior? If the behavior is the same than you may want to do a fresh install of Crossover using our removal tool. This will delete Crossover and all of it's bottles and files. The removal tool can be found here https://support.codeweavers.com/en_US/getting-started/using-the-crossover-removal-tool

Another option would be to create a new user and see if the Diablo IV runs well on the new user. If it does than there is most likely something causing the issue specific to your main user. Directions on how to do that can be found here https://support.apple.com/guide/mac-help/add-a-user-or-group-mchl3e281fc9/mac#:~:text=On%20your%20Mac%2C%20choose%20Apple,may%20need%20to%20scroll%20down.)&text=Click%20the%20Add%20User%20button,choose%20a%20type%20of%20user.

Let me know how this works for you.

Regards,
Codeweavers Support
"

Just out of curiosity, which piece of advice helped get you running?

I apologize I forgot to put that in my post it was removing crossover and reinstalling it using their directions.

Has anyone else done these steps? I had it running with no problem for a while there and now it's freezing again on the login screen. I replied to the e-mail and will post any new info here for everyone. This way they only have one ticket in the system for multiple users. I don't know if that's what they want but it seems to me to be more economical.

I’m genuinely surprised that the developer denies the existence of the freezing issue, especially given the numerous reports from users on this forums. I’ve tried the fixes you mentioned, but they didn’t work at all. I strongly suggest that the developer avoid testing this issue on their own development Mac and instead try using a different, fresh clean Mac, such as an M2 Mac Mini with just 8GB of RAM. I’m confident the freezing issue will occur—without a doubt.