@METALHEAD:
Hey again all!
We’ve synced with the devs and it looks like we’ve got enough reports now. Thanks for answering the call to action and getting us those DXDiags/Error reports. I’m editing the other messages to indicate that we no longer need more data. You are welcome to continue reporting issues or work arounds that you discover, but you can save yourself some time and stop gathering the previously requested logs now.
The devs are aware and looking into the issue now. We’ll let you know as we g…
Our team is still investigating the issue and they believe they found the source of whats been causing the issue. It’s a frustrating issue and these types of compatibility issues can take a bit of time to resolve.
Our team needs to run through testing and replicating the issue to find the cause, then work on a fix for the issue. Once a fix is in place, our QA and compatibility teams need to make sure the fix works. If they can test and verify the fix in place works, an update or hotfix will be …
Our team is still looking into the issue and still haven’t confirmed what exactly is causing the problem, but they do have a hunch to what the issue is. With it being the weekend, I may not be able to get more information until the weekday. I’ll check back to see if there’s any additional information to share on this issue.
Hey all,
Just poking our head in here. We bumped our thread on this to see if we can get any updates. Nothing yet other than the fact that the QA team is looking into it and has a few suspicions based on how this is all going down. Thanks so far for all the help gathering data.
Hey folks,
We still haven’t heard back from the developers with anything particularly useful for you all. We haven’t forgotten this, we just haven’t been bumping the thread since we try to avoid posting on known bugs when there isn’t important information to be communicated.
It seems like people are having some hit or miss behavior based on the most recent Windows updates. We’re working on the issue with Microsoft, and we expect that it will be fixed in a future build, but we haven’t gotten absolute confirmation that one fixes it yet. Once we get a bit more consistent behavior, we can give you all further instructions, but for now if you read recent posts you’ll find that some people are getting some luck with a more recent update.
(sorry - I got carried away)
No update since 10-Sept-2020.
Take a look here for a detailed description of what might be the problem…
Well this is not true. The real reason behind the problems is your Operating System (or parts of it). If you would google Fmod issues for development you would quickly realize that microsoft messed it up. In every developer space there is problems with it. Soundengineering, gamedevelopment etc.
First problems with diablo3 however showed up when microsoft introduced windows 1809 with an updated sound system. (oct 2018)
Back then setting the soundchannels to “lowest” ingame fixed the majority o…
I don’t know if all of that is factual… but it kind of make sense to me. It would explain why only players on recent Windows 10 builds are having this issue when others, such as me running 1803, don’t. It would also explain why players switching to Windows 7 or using a dual boot with a Windows 10 build prior to 2004 don’t have the problem. It could also explain why @Crinel and @Crusader are not seeing the issue in Windows 11.
Still enjoying D3 in Windows 11, shame I have to dual boot to play one game! No more micro stutter and no more freezing (FMOD issues). I was getting freezes all the time on Windows 10. My advice would be to install 11 on a spare HD and test yourself, no harm in trying
Hi Crinel,
with the W11 version 22000.1, Diablo 3 ran extremely well and very quickly, without errors.
With the W11 version 22000.65, Diablo also ran well, but I often noticed micro stutters.
Greetings from Germany.
The thing that bugs me is… why doesn’t Blizzard come out and say what the issue is… especially if it’s something they have no control over such as the various Windows 10 versions.
3 Likes