[Bug]: Diablo II Resurrected get freezed after a while

[larryisthere]

macOS Version

Sequoia (macOS 15)

Apple Silicon or Intel

Apple Silicon

Wrapper Version

Wineskin-3.1.0

Engine

WS12WineCX23.7.1_1

Application/Game Name

Diablo II Resurrected

Render Used

D3DMetal (64-bit only)

Description of problem

After playing the game for a variable period of time, it freezes - the screen becomes stuck and doesn't respond to any operation. This issue is difficult to reproduce consistently and can occur at any time. When this happens, the only solution is to force quit D2R.exe through Mac and restart the game.

This is my configuration of the wrapper.

Steps to reproduce

1. Use the configuration above.
2. Play the game as usual, or leave the game running for a while.
3. Then it gets freezed.

Expected behavior

The game won't get stuck.

LastRunWine.log

LastRunWine.log

Code of Conduct

• I agree to follow this project's Code of Conduct

[Gcenx]

You can remove export WINEESYNC=1 from Unix commands as that & msync are enabled by default.

How much ram does your system have exactly as Diablo2: Resurrected & Diablo 4 are ram hogs.

Also if noticed you claimed to be using Wineskin-3.1.0 yet the provided image shows Wineskin-3.0.9 so I’ve updated the issue. You should upgrade the wrapper to Wineskin-3.1.0 as that contains D3DMetal-v2.0 (non-beta)

[larryisthere]

You can remove export WINEESYNC=1 from Unix commands as that & msync are enabled by default.

How much ram does your system have exactly as Diablo2: Resurrected & Diablo 4 are ram hogs.

Also if noticed you claimed to be using Wineskin-3.1.0 yet the provided image shows Wineskin-3.0.9 so I’ve updated the issue. You should upgrade the wrapper to Wineskin-3.1.0 as that contains D3DMetal-v2.0 (non-beta)

Thank you for your detailed reply and reminder. I have just updated the wrapper to version 3.1.0 and removed 'export WINEESYNC=1' from the Unix commands. I will now observe the game's performance.
Additionally, I'm using a Mac with M1 Pro and 32GB RAM. Do I need to specifically configure any memory-related parameters somewhere?

[Gcenx]

You have a good amount of ram, if the wrapper grade and removal of export WINEESYNC=1 doesn’t help then it could be ether a memory leak in D2R.exe or related to the recent Argent.exe upgrade in Battle.net that’s been causing problems.

[larryisthere]

You have a good amount of ram, if the wrapper grade and removal of export WINEESYNC=1 doesn’t help then it could be ether a memory leak in D2R.exe or related to the recent Argent.exe upgrade in Battle.net that’s been causing problems.

Okay, I understand. Your explanation is very clear! Thank you very much. By the way, the recent Battle.net update caused CrossOver to be unable to run the game, but Kegworks performs as excellently as always, very powerful. Thank you for your efforts! Thumbs up!

[larryisthere]

Bad news, the game froze again with the background music still playing. Strangely, CrossOver doesn't have this issue, which is odd.

[Gcenx]

That’s odd, might be something with D3DMetal-v2.0 not being that great with wine-8.0

You could always fallback to D3DMetal-v1.1 by removing /Frameworks/render/d3dmetal/2.0 but there’s no guarantee it’ll work.

When I have time I’ll see if this happens in my M3 Max, I’ll test with CX23.7.1-1 and the unreleased CX24.0.5

[larryisthere]

Good news! After downgrading d3dmetal to 1.1, I've played for several hours without experiencing any lag/freezing. I think this might have solved the problem!

[rlarhsid]

Thought this was only my issue, but seems like someone else also has this problem.

I'm using M1 Max with 64GB RAM, so I guess this isn't the problem of the machine itself. I'm playing some rhythm games (DJMAX RESPECT /V, EZ2ON: REBOOT: R), and as they aren't a 3D-based game, they won't require much RAM and CPU power. However, the game often crashes / freezes with audio in background (same as the issue reporter), and the only way to fix this is entirely restarting the wine process by manually ending all .exe processes. Using D3DMetal 1.1 lowered the rate of this issue happening, but still didn't completely fix.

This issue didn't happen when using the old Wineskin Winery, and happened since using Kegworks.