Diablo III Tips

Fix: "Removed from Game" and freeze at "Retrieving Heroes"

The modification to the script required to run the game is minimal. It just executes the Battle.net Desktop App and you'll be able to run your game from there

setarch i386 -3 -L -B -R $HOME/cxoffice/bin/cxrun --bottle "$BOTTLE" "$HOME/.cxoffice/$BOTTLE/drive_c/Program Files/Battle.net/Battle.net Launcher.exe"

NOTE: The info below is obsolete since the 2.0.1 patch

As of June 6, many people on 64-bit systems are experiencing issues with the game freezing at "Retrieving Heroes". After a few days, this issue was resolved but the issue re-manifested itself as a "Removed From Game" error with spinning CPU.

The fix for me (adapted from a related command posted on those boards) was to run Diablo 3 using the commands:
BOTTLE="Diablo III"<br>setarch i386 -3 /opt/cxoffice/bin/cxrun --bottle "$BOTTLE" "$HOME/.cxoffice/$BOTTLE/drive_c/Program Files/Diablo III/Diablo III.exe"
Or, if you are using this in a launcher, interpolate the environment variables and set a working directory:
setarch i386 -3 /opt/cxoffice/bin/cxrun --bottle "BOTTLE" "/home/MYUSER/.cxoffice/BOTTLE/drive_c/Program Files/Diablo III/Diablo III.exe"  
(with working directory): /home/MYUSER
Where "BOTTLE" is your Crossover bottle name and "MYUSER" is your linux username.

I will remove this tip if it becomes obsolete, as this is essentially a workaround ( still required as of Crossover 11.2.0 beta 2).
While people are getting stuck trying to log in it's best to have it available here until then. Hope that helps!

by Ryan Sanden Ryan Sanden on 2014-03-09 13:56:37
Important Information Tips are provided by the CrossOver Community and Advocates. They are not intended to be used for official CodeWeavers Support. For that, please visit our official support pages.
CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...