kambala wrote:NodiX wrote:kambala wrote:I might have found a strange "fix" for macOS: adding the following wine debug channels fixes character loading for me:
+timestamp,warn+all
Can you elaborate more? Are you referring to BigSur character crash? If so, how do we do that in CrossOver?
I'm talking about getting stuck on the Loading screen, on linux the same thing also might happen. Not sure which crash you're referring to, all works fine on my Big Sur.
I haven't found how to customise
WINEDEBUG in CrossOver GUI, instead I use a shell script to launch d2 (and optionally d2stats) using CrossOver's wine. Can share it if you're interested.
It's likely that crash you mentioned since I managed to run Sigma 2 with your solution (finally!). My temporary fix is to add
WINEDEBUG key with value of
warn+all in regedit by adding it to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\EnvironmentNOTE: if anyone who don't know how to access regedit in CrossOver bottles you can open it by inserting "regedit" instead of browse for exe in bottle's Run command.
EDIT:Sometimes the game still crashes setting WINEDEBUG in regedit. In this case WINEDEBUG can still be injected through CrossOver by checking the "Create log file" when clicking right button on Diablo 2 -> Run with options. This will create a log file that you can save wherever you want, because this is not important since all we need just to inject WINEDEBUG into CrossOver. Text field for "Extra environment variables" will available and you can enter
WINEDEBUG=warn+all there (with this method you might have to repeat entering the WINEDEBUG env variable every time starting up the game exe, though).
