Not sure, but MB. Warden replaced the files.
for me this is true:
With the old files (2015 Version) i have tons of freezes.
With the New Ones (2019 Version) None.
, but Position errors.
Click on runtime.DLL, show Details, 2015? , then Warden.
I know its konfusing, but Warden is also using these files…
Windows 10 will block the new files as they are from a different PC. To solve this just right click the files and tick Unblock at the bottom.
True, but thats a one time action.
1 Like
I can confirm I’m in gr115 with 3 good wiz and NO lag, no freezes and Sound works great!
1 Like
Can you update the instructions to include the unblocking files? cheers
Ok Been testing all evening and I have no issues to report. Logfile shows plenty of errors and game actually feels better in higher gr’s.
To Install I did:
1, Download the files from link at top.
2, Replace the files in D3 folder “Diablo III\x64”
3, Right click new files 1 by 1 and on click properties the bottom right of the properties box there is a tick box to unblock the files ( this is due to taking files from a different PC). Click this and then click apply then ok.
http s://ibb.co/HnqS3N1
4, Load the game as normal via the Launcher.
I’m not sure if this will persist or if we will need a simple bat file to repeat the file replacement on launch. Either way to play with sound and no issues this is worth a go.
This is the main error I have in Log now
|2021.05.01 00:30:48.125791800|FMOD Error during ‘FMOD_Channel_SetPosition’: An invalid seek position was passed to this function.
|2021.05.01 00:30:48.126094400|FMOD Memory - total: 178257920|
|2021.05.01 00:30:48.126302500|FMOD Memory - allocated: 53226392, - max allocated: 68540536|
I have removed my reply to this topic due to not following through with everything needed to do a proper evaluation. I failed to unblock the two files yet it still seem to work.
I have now unblocked the two files and am trying again.
Fingers crossed for you, ive enjoyed my night on D3 with sound, hope this works for all. Launcher does replace the bloody files though
Unfortunately the fix is not working for me. Too bad! I quite enjoy sound. Was doing a GR 113 and it froze up hard for quite some time. I confirmed I still have the two files there and were the same version as yours.
I have my sound in game set to Low (32) with default sound and Speaker set to 5.1
Logs show the following.
| 2021.04.30 19:56:19.287645400 | FMOD Error sound not ready in 200ms |
|---|---|
| 2021.04.30 19:56:22.364624900 | FMOD Error sound not ready in 200ms |
| 2021.04.30 19:56:25.440165400 | FMOD Error sound not ready in 200ms |
| 2021.04.30 19:56:28.516724500 | FMOD Error sound not ready in 200ms |
| 2021.04.30 19:56:31.593846000 | FMOD Error sound not ready in 200ms |
| 2021.04.30 19:56:34.685930700 | FMOD Error sound not ready in 200ms |
| 2021.04.30 19:56:37.761548000 | FMOD Error sound not ready in 200ms |
| 2021.04.30 19:56:41.067967700 | FMOD Error sound not ready in 200ms |
| 2021.04.30 19:56:41.115898300 | I 01:56:41.115902 [BGS] |
| 2021.04.30 19:56:41.209579100 | ERROR: Ran out of explosions processing Explosion ‘g_radial_10foot_100lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.209872500 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.210142200 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.210491400 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.210806900 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.211222700 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.211409800 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.211775800 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.212049500 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.212404600 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.212828900 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.213091700 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.213269700 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.213553200 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.213851200 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.214150800 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.214411000 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.214639700 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.214897500 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.215158700 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.215416000 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.216001200 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.216363900 | ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128). |
| 2021.04.30 19:56:41.242581900 | Received pong with old sequence! |
| 2021.04.30 19:56:44.327608700 | FMOD Error sound not ready in 200ms |
| 2021.04.30 19:56:47.403398500 | FMOD Error sound not ready in 200ms |
| 2021.04.30 19:56:50.479670700 | FMOD Error sound not ready in 200ms |
| 2021.04.30 19:56:53.570825300 | FMOD Error sound not ready in 200ms |
| 2021.04.30 19:56:56.646302700 | FMOD Error sound not ready in 200ms |
| 2021.04.30 19:56:59.723127500 | FMOD Error sound not ready in 200ms |
Unfortunately, got a freeze in the first GR 110 (solo) I ran.
5/2/2021: Ran GR 120’s last night with my zbarb - continuous freezes 
Unfortunately this fix dose not work for me the game is completely unplayable. It would have been nice to have sound again!
Guess I just have to stick to the fmodex64.dll fix for now till someone finds a fix that works for everyone!
This worked perfect for me started playing D3 again a few day’s ago and the mini stutter lag was driving me crazy.
1 Like
Can we have someone from Blizzard at least tell us something with respect to this issue that has been ongoing for 3 seasons now?
It really is a game breaking issue for the hardcore people and a frustration for us softcore people.
Can you at least, also, allow those that choose to use the fmod DLL fix to keep that DLL there that is provided by Hero’s of the Storm? I personally don’t use that fix due to my really liking the sound when I do GRs.
Thanks.
Ive not had an issue since using these new files, strange it does not work for some. Maybe user error. Still only getting the below fault in huge density fights.
| 2021.05.02 15:24:08.121415100 | FMOD Error during ‘FMOD_Channel_SetPosition’: An invalid seek position was passed to this function. |
|---|---|
| 2021.05.02 15:24:08.121714700 | FMOD Memory - total: 178257920 |
| 2021.05.02 15:24:08.121924900 | FMOD Memory - allocated: 50917680, - max allocated: 64412776 |
Could be that some of us play way too many hours at a time. I start in the morning and am almost done by the time evening supper is around.
I would have to say it seems to take about 1 to 3 hours before the first fault then it’s pretty common occurrence there after.
Can you please re-upload these files? Would greatly appreciate it!
I don’t think you need to download them; if you run fully patched Win10, the suitable versions of these DLLs should already be in your Windows\System32 directory. The exact version doesn’t have to match; it’s the first 2 numbers, which are Major.Minor parts, that are important.
On my machine, they are both 14.28.29334.0. As long as you see the “14.28.whatever”, it should be okay.
Just make sure you don’t accidentally delete or overwrite anything in the System32 directory. That might lead to unpredictable consequences.
Just delete the files in game directory before launch, easier.
The files don’t need to be downloaded.
The can be found in your system32 AND sysWOW64 directory.
If using the 64bit version of the game then search for the 2 files in the sysWOW64 directory.
If using the 32bit version search for the 2 files in the system32 directory.
After you find them in there they can be copied to the diablo3 folder. Make sure to put the 2 files in the correct diablo directory(x64 if using 64 bit)
I can confirm this has fixed my suttering/performance issues. I’ve been playing for just over a week with no issues.
It’s actually the other way around:
System32- 64-bitSysWoW64- 32-bit
Confusing, I know, but Microsoft had its reasons to set it up this way.
1 Like