Repository navigation
Replies: 11 comments 24 replies
|
will try building it step by step by step |
|
scripts/create-bottle.sh returns "==> Installing build tools (bison 3.x, mingw-w64) |
|
i guess i didn't have homebrew installed, i think that was the issue |
|
new issue, cannot find libd3dshared.dylib in game porting toolkit dmg |
|
@mikey92 i made a github just for this please reply at your soonest convenience </3 |
|
Thanks for the report, this one is on me. The installer looked for the toolkit under Right now you can point the script at the mounted volume directly: (adjust the version in the name to whatever Finder shows). Then run the installer again, it will see the toolkit as already installed and go on to the launchers. The fix that finds the mounted image by asking hdiutil, and lets you paste the path at the prompt, is merged in #22 and is on main now, so a fresh |
|
Thanks so much! |
|
Finally got it installed, but I'm getting this weird loop when launching D2R. Can press play and launch it, but nothing actually happens then it says it needs an update and it just stays stuck on initializing... @mikey92 have you been able to play D2R on battlenet ? |
|
I had this exact same issue with crossover as well... |
|
"00e4:err:seh:dispatch_exception assertion failure exception" is what I get when trying to launch D2R from battlenet or directly via scripts/play.sh d2r do I need to be on macos 26 ? I am currently still on sequoia |
|
|
|
That is the macOS version. D2R got a new anti-cheat in January 2026 that trips a Rosetta 2 bug, and Apple fixed it in macOS 26.4. On macOS 15 the game dies right after launch, which is what Battle.net turns into "Update" and an Agent stuck at Initializing. CrossOver hit the same wall at the time, which matches what you saw there. The assertion line in the log is noise, it shows up on my 26.5 machine too while the game runs fine. So for D2R specifically: update to macOS 26.4 or later, then it should start as-is, nothing to reinstall. The launchers and other games do not depend on that fix, but I have only verified everything on 26.5. Sorry I could not get this one working for you on Sequoia, it is on Apple's side and there is nothing Soju can do around it. And sorry the requirement was not in the README after you went through all of that; it is now. |
|
One more thing, if you have two minutes before updating. I am going by the symptoms and the CrossOver match; I have not seen the actual stall on a Sequoia machine. A stack sample would confirm it, and if it turns out to be something else, that I can fix. With Battle.net closed, run Then attach |
|
I immediately updated my OS to Tahoe :'( |
|
No worries, the sample was only to double check my reading. On Tahoe you are past that bug, so D2R should just start now, from Play in Battle.net or with |
|
Will let you know as soon as I reinstall everything, so far soju installation was like butter already finished battlenet install. |
|
insterestingly enough, launching gave me same issue when trying to launch from battlenet**** |
|
That changes things, so it is not the Rosetta bug, or not only. I need to see what actually happens on your machine. Four quick things:
Your log stops right after the MoltenVK extension list, before D3DMetal says anything, so the game is stalling before graphics init. On my machine D2R starts fine in a fresh bottle from the installer with both the CrossOver and the 4.0 beta 2 toolkit, so the sample is what will tell us where yours stops. |
|
when I run soju d2r game launched! and it is online! |
|
but when i try to launch from battlenet nothing happened, same issue where it says now playing but nothing actually happens then asks for an update and it initializes for a long time and then the play button returns |
|
ps -o rss=,%cpu= -p $(pgrep -f D2R.exe) |
3)4.0 beta 2 gtpk |
|
Good, that narrows it a lot: the game and the toolkit are fine, it is the hand-off from Battle.net that fails. No need for the sample any more. Two things from the Battle.net side, right after one failed Play:
Also, if you installed D2R somewhere other than the default |
|
1)grep -ah "Launched|GameLaunch|gameRunning|InstallState (osi)" ~/.battlenet-macos/bottle/drive_c/users//AppData/Local/Battle.net/Logs/battle.net-.log | tail -30 returns D 2026-09-03 22:07:45.025638 [ProductState] {Main} InstallState (osi): installed=1 hasInstallModificationOptions=1 installPath=C:/Program Files (x86)/Diablo II Resurrected selectedRegion=kr activeConfigKey=00000000000000000000000000000000 regionalVersions=(eu: {playable:false config_key:623f7a1f73eabb08ccb2b2046e3f9164}, kr: {playable:false config_key:623f7a1f73eabb08ccb2b2046e3f9164}, us: {playable:false config_key:623f7a1f73eabb08ccb2b2046e3f9164}) repairSupported=true localVersion= latestVersion=93847 |
returns -rwxrwxr-x 1 rashedalkatawneh staff 83199 Sep 4 01:38 /Users/rashedalkatawneh/.battlenet-macos/bottle/drive_c/Program Files (x86)/Diablo II Resurrected/blz-log.txt |
|
i installed it in the default location |
|
That log is actually good news: Battle.net does start the game (pid 2592, running for 54 seconds) and it reaches networking before it exits, so this is not the launch hang, it is something that kills it a bit later. The "Update / Initializing" afterwards is just what Battle.net shows once any game closes, on my machine too, so that part is a red herring. The practical part first: since For the Play button itself, the difference is in how Battle.net's Agent starts the game versus how |
|
I'll check back later! Once again, my sincerest thanks to you for all your work especially now that I can finally play D2R! |
|
Glad you are in. For the record so it does not bite the next person: Play failing while |
|
Yes, I did notice that running soju d2r after killing all soju processes caused the game to be offline only. I will be running battlenet and having it fail so that I can run soju d2r and hopefully get online content. It could also be a network issue on my end. |
|
Tried to reproduce the Play path here with the region switched to Asia, launched from Battle.net (REGION=KR in the launch options, same as yours). The game came up and stayed up, so the region itself is not it. One thing stands out in the order of events on your side: the Play that failed was the very first time the game ran, and since |
|
It works from the play button! I have to pause then unpause the "update" so that the play button shows up, but when it does the game launches and connects to servers. |
|
Good to hear. That Update after a game exits (or after a launch that died) is Battle.net re-checking the install, and pause then resume is the way to get Play back here too. I put it in the README so the next person does not have to guess (#25). So the first Play dying looks like a one-off; if it ever comes back, the two lines above would still tell me where it stops. Thanks for reporting back. |
|
Can confirm D2R also runs on macos 27 too, fully online |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
pressing enter after downloading the toolkit from apple returns "Not found yet - make sure the dmg is mounted", should I restart the process again with the DMG already mounted?
To be clear I downloaded the toolkit and then mounted the dmg and then pressed enter and it still gives me that same message.
All reactions