I’m seeing FMOD errors in my D3Debug.txt. I disabled my onboard sound card. Currently using a USB DAC in my Vanatoo T0 speakers.
|2020.07.04 16:40:42.630513600|Disposing UI for World|
|---|---|
|2020.07.04 16:40:42.639467900|Disabling loading screen for 1, 4|
|2020.07.04 16:40:42.646602500|Disabling loading screen for 2, 4|
|2020.07.04 16:40:42.647247900|Disabling loading screen for 4, 0|
|2020.07.04 16:40:58.757027000|FMOD Error sound not ready in 200ms|
|2020.07.04 16:41:01.918029500|FMOD Error sound not ready in 200ms|
|2020.07.04 16:41:05.065028300|FMOD Error sound not ready in 200ms|
|2020.07.04 16:41:20.079321500|I 23:41:20.079279 [BGS] |event=rich_presence_failure|key=id: 50522657, id: 12418524 program: 17459 region: 1|missing_presence_unique_id=0 (src\low\service\presence\rich_presence.cpp:156)|
|2020.07.04 16:41:21.513033200|I 23:41:21.513280 [BGS] |event=rich_presence_failure|key=id: 50522657, id: 11380478 program: 17459 region: 1|missing_presence_unique_id=0 (src\low\service\presence\rich_presence.cpp:156)|
|2020.07.04 16:41:28.868177200|[Telemetry] (TELE): Requested sending batch messages by multi-part http POST messages count 1|
|2020.07.04 16:41:46.721070900|Enabling loading screen for 4, 4|
|2020.07.04 16:41:46.722448400|Initializing client world X1_LR_Level_03...|
|2020.07.04 16:41:46.723368100|Enabling loading screen for 4, 4|
|2020.07.04 16:41:46.726261500|Disposing UI for World|
|2020.07.04 16:41:46.741568100|Disabling loading screen for 1, 4|
|2020.07.04 16:41:46.813808400|Disabling loading screen for 2, 4|
|2020.07.04 16:41:46.814295000|Disabling loading screen for 4, 0|
|2020.07.04 16:42:11.701041400|FMOD Error sound not ready in 200ms|
|2020.07.04 16:42:14.847041000|FMOD Error sound not ready in 200ms|
|2020.07.04 16:42:17.997018300|FMOD Error sound not ready in 200ms|
|2020.07.04 16:42:36.872067700|Received achievement awarded notification for 12544844|
|2020.07.04 16:42:50.983019200|FMOD Error sound not ready in 200ms|
|2020.07.04 16:42:54.135016800|FMOD Error sound not ready in 200ms|
|2020.07.04 16:42:57.291042000|FMOD Error sound not ready in 200ms|
|2020.07.04 16:43:28.870184200|[Telemetry] (TELE): Requested sending batch messages by multi-part http POST messages count 1|
|2020.07.04 16:43:34.585055300|FMOD Error sound not ready in 200ms|
|2020.07.04 16:43:37.731039400|FMOD Error sound not ready in 200ms|
|2020.07.04 16:43:40.875016900|FMOD Error sound not ready in 200ms|
EDIT: Okay. It looks like this was causing the freeze the entire time. I ended up replacing the 64bit fmodex64.dll in the x64 folder of the Diablo III game directory and the game doesn’t freeze anymore. I don’t know if it messes up the sound or not but I play the game without sound anyway.
EDIT 2: Replacing the fmodex64.dll will disable game sound. Make sure you backup the original fmodex64.dll (rename it to fmodex64.bak). It’s worth not having the game freeze every few minutes though.
EDIT 3: I reenabled my Realtek onboard audio and installed the latest drivers from Asus (December 2019) and tested the original fmodex64.dll and the game still freezes. It’s definitely not my driver. For now i’m going back to using that 3rd party fmodex64.dll
Here’s the file I used:
https://drive.google.com/file/d/1MUhzqQIR_YVn7xKQ7WhKj8gTgnc3G-hg/view?usp=sharing
Rename the fmodex64.dll to “fmodex64.dll.new” and move it to the Diablo 3 x64 folder.
Create a .bat file with the following lines:
@echo off
copy /Y "C:\Program Files (x86)\Diablo III\x64\fmodex64.dll.new" "C:\Program Files (x86)\Diablo III\x64\fmodex64.dll"
cd "C:\Program Files (x86)\Battle.net\"
Battle.net.exe --exec="launch D3"
That will replace the dll file and launch Diablo 3 via the battle.net launcher. This will bypass the D3 login screen.