160+ hours of gameplay lost (again) for known issue of game freezing in middle of GR pushing. I do not even want or need my necro back. but please!!!
edit #2 Lost the Witch Doctor to this now also, so total lost today by this bug 320+ hours
honestly–>
Fix the Diablo3/64x FMODEX64.DLL file causing this or atleast give us the option to bypass bnet launcher from overwriting that file on every launch.
I thought that you might have had it done now, since it has been almost full year of this happening continuously, regardless of the server or realm.
I am playing on EU, but i have seen many people complaining about this exact freeze issue on US servers also that it is impossible for this to be just EU or customer related issue. Even the same workaround/fix reportedly seems to work on different servers.
Game is NOT playable in Hardcore mode because of this and i am currently quite pissed off. OK, I note that it is my own fault to be such a dummy that i play hardcore, but its blizzard/bnet tech who manages to kill my charrecters. I JUST WANT TO BE ABLE TO KILL THEM MYSELF - by MY mistakes.
there is already a working method to do as your asking of the bnet app being bypassed and the file being overwrote every launch. if wanting help doing this please private message me. all it takes it having the FMODEX64.dll 1 file and using notepad to create a script that you type the code in youself so you know what’s happening. there are methods to bypass bnet app, also to use bnet app, let me know
I have used this method before, and i just wanted to believe it was fixed with the new bnet app and huge patch to the game, but it seems that i was wrong with my expectations. yet again…
updated bnet app just wont let me use the old script i had, or i have had it wrong all the time. 99% of times, when i replace the .dll file. Bnet tells me to update game which has not happened before.
but no stress and no rush with the messages…
i just got killed by this same damn freeze with my secondary WD. All gear and gems are gone, so i guess i just wait for next season anyway.
total of 320++ hours lost today.
i think i can call it for the day.
yea i lost my 10/13 140+ augged guy, it hurts
yea when doing it so you use the bnet app, you go to settings > downloads > under automatic updates select “never automatically apply updates” bubble, click done.
exit bnet app
replace dll
if prompts to update, either close bnet and reopen or update and re-replace the dll and try again, sadly this is what you gotta go through if you want bnet app to be launched and have the fix applied, you can make a batch file script with notepad like
line 1: echo y | copy “C:\fmodex64.dll” “C:\Program Files (x86)\Diablo III\x64”
line 2: start “Diablo III” “C:\Program Files (x86)\Diablo III\x64\Diablo III64.exe”
save that file as “whateveryouwant.bat” when the save prompt comes up, doesn’t matter what “type” you pick as you putting the “” around it forces it to be a batch file.
then just use that batch file to do the work, this assumes the fmodex64.dll is location at C:, if it’s not adjust that in line 1
it also assumes diablo 3 is installed at c:\program files (x86)\diablo III, again if not adjust that in line 2
this will automate the copying of the dll and start diablo, you still will come against the “update” issue, and you just have to do as stated above which is to close bnet app and relaunch or choose update then close and relaunch with batch file
this is the process to “use” the bnet app while automating as much as you can to get the fix applied, if you want the other way to do without using bnet app replace line 2 with
start “Diablo III” “c:\Program Files (x86)\Diablo III\x64\Diablo III64.exe” --launch
again assuming it’s installed at that location, if not adjust it to where your’s is installed
Slightly technical point here, but you’re better off saving it as…
“whateveryouwant.cmd”
.BAT files are Batch files and executed under COMMAND.COM which is the old 16-bit interpreter, so runs on WoW (Windows on Windows).
.CMD files are Command Files and executed under CMD.EXE which is the native CLI (Command Line Interpreter) of the Operating System, i.e. either 32-bit or 64-bit depending on O/S version.
If I remember rightly, the original US Thread also has some examples of .PS1 files, which are Windows PowerShell scripts, which is available from Windows 7 onwards.
i would still love to add to the topic that i have absolutely no idea is this method to bypass blizzard/bnet app, its launcher, and even messing around with the game files considered a violation to terms of use?
For that reason, i would love to have blizzard employee to comment on the issue at hand just to make sure it is not prohibited in this case.
My personal opinion about this clusterfck is that, community is doing the developers job currently, which is NOT the communitys job to do. at all.
true but nobody i know runs diablo 3 on windows 9x, .bat files are executed with cmd.exe automatically, so in this particular context it don’t matter as the end result is the scripts runs under the new 32/64 cmd.exe by default when using .bat or .cmd. if you play on windows 9x (if even possible) then this would become an issue, but good point
also this issue has been blue posted, can’t track it currently but know for 100% sure i’ve seen 2 blue posts saying this is the way to handle it in the interim until they fix
boubou, the differences is your version does not auto copy the fmod.dll with each run of the script, this helps solve the bnet updated the file and you didn’t notice or any other million of reasons the file could get overwritten or corrupted and this insures the fmod fix is applied each and every time you use the script not just the one time you manually put the file in the folder.
Without bnet.app (the most useless thing EVER!) You can start D3 with replacing “Battle.net Launcher.exe” with “Diablo III.exe” -launch" [depending where your software is installed] and sadly to say there is a negative thingy with this - You have to type your password for your account, but it wont start bnet.app and replace your dll…
