![]() Hopefully this helped a few of you get over the Diablo 3 patching woes! If nothing else, it allowed me to create that Diablo mushroom cloud graphic.ĮDIT: For those that don’t want to re-install, you can try editing the patch_url manually. That said, the actual BEST solution, is for Blizzard to fix this problem, or failing that, roll out all the patches at once! Granted, this is a giant pain in the backside, especially if your internet connection has usage caps! However, the *best* solution, is to reinstall using the client native the server you are playing on. It may be possible to work around the problem by manually editing the patch_url in your agent.db file, I had some initial success this way. The problem is, the US patch is released first, causing all the people connecting to the US servers with a non-US client to crash until the other servers are patched. This is all fine and good, until Blizzard releases a patch. So if you are unable to log in to Diablo after a server patch, or the patcher is giving you “Diablo III is already running” or “Diablo III has stopped working”, this might be the fix to your problem.īasically what it boiled down to is the Blizzard installer gave me the en-GB ( Great Britain ) installer instead of the en-US one. To people having this problem, this post is a much more concise description of the problems I had, and the fix. It would appear the server patch crashes are still occurring. I wrote that when I was experiencing crashes when they last patched the Diablo 3 servers. I can always tell when Diablo 3 servers are being patched as I get an influx of visitors viewing this page. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |