Diablo 3 using battle.net app

Hi,

I have a problem getting multiboxing with diablo 3 to work. I have 3 different accounts each using the authenticator, therefore I would like to use the launcher.

I have setup 2 accounts for now, using different virtual files in ISBoxer and I can launch each one of them separately from innerspace. But when I try to launch both accounts the second one logs into battle.net app fine but states "Game is running" and the play button is greyed out.

How should I proceed to get this working? What more information is needed from my side?

Code:

/====================================================
|
| 13:07:35 ISBoxer: Preparing to launch Character Set 'd3'
| 13:07:35 ISBoxer: Settings imported from ISBoxerToolkit.GeneralSettings.XML
| 13:07:35 ISBoxer: Making sure Characters in Character Set 'd3' are valid...
| 13:07:35 ISBoxer: Good!
| 13:07:35 ISBoxer: Launching Character Set 'd3' all slots...
| 13:07:35 ISBoxer: Launching Slot 1 Character 'jonte'
Successfully executed '"C:\Program Files (x86)\Diablo III\Diablo III Launcher.exe" -launch'.
Session launched (is50): "C:/Program Files (x86)/Battle.net/Battle.net.5383/Battle.net.exe"
Session launched (is1): "C:/Program Files (x86)/Diablo III/Diablo III.exe"
| 13:09:01 ISBoxer: Launching Slot 2 Character 'sebbe'
Successfully executed '"C:\Program Files (x86)\Diablo III\Diablo III Launcher.exe" -launch'.
| 13:12:01 ISBoxer: Character from Set 'd3' not fully launched after 3 minutes. Select again to continue launching additional slots.
| 13:12:01 ISBoxer: Instructions completed.
|
\====================================================
Session launched (is50): "C:/Program Files (x86)/Battle.net/Battle.net.5383/Battle.net.exe"


Thanks
Jonatan

[MiRai]

The -launch parameter is used for D3's executable file to bypass the launcher, not for use on the BattleNet Launcher itself, but that probably isn't the issue. Very few people report the "Game is running" issue, but I imagine it's a either a problem with not having the correct virtual files configured and/or assigned properly, or not completely closing the BNet Launcher between each character.

You can share your profile for us to see if the problem lies in there, but have you seen this video?

Thanks for your answer. I added the -launch to see if it made any difference, but no change ofc

Here is my config: http://www.privatepaste.com/306d902fe0

I'm running windows 8.1 if that makes any difference. I think I have verified that the different battle.net config files are used, if I have them opened in notepad++ at launch time it says that the config file of each character has been modified after battle.net for that character is launched. I have also verified that the settings in the battle.net launcher are different between the different characters.

I tried to change profile on the second character to skip battle.net launcher and then diablo launches fine, so as you say, it is probably a launcher issue.

I didn't see the video but I followed the how to guide linked in the description.

[MiRai]

Unfortunately, I can only test on Windows 7, but maybe Lax will have to look at in on his Windows 8 machine.

Does skipping the launcher force you to continually enter your authenticator information? I would think that if the launcher doesn't require it then the game client wouldn't either, seeing as the 'trigger' for asking for the code should be the same between each, no?

Unfortunately it do require me to enter authentication for each account on startup if I skip the launcher.

I will reinstall my comp back to Win 7 and give it a try, sick of windows 8 anyhow

Back on windows 7, get the same issue with the launchers in win 7 as well. If I launch diablo directly and log in there is no issue.

New configuration: http://privatepaste.com/18241d4468

[bob]

What about this process?

http://isboxer.com/wiki/HOWTO:Autologin ... Battle.net

You can probably ignore the "Adding this capability to an existing Character Set" section. Just follow along with the "The game launching process" section.

Hi,

I have followed that guide but when the second account is logged into battle.net I get "Now playing - game is running" and I'm unable to start Diablo 3 on that account.

It also seems like sometimes the original battle.net launcher is opened as I don't get any overlay features on it. I'm not 100% sure but I think this happens when a battle.net update agent is still running in the background after battle.net launcher have been closed.

[MiRai]

I have followed that guide but when the second account is logged into battle.net I get "Now playing - game is running" and I'm unable to start Diablo 3 on that account.

I was able to reproduce the issue and have told Lax about it. There is currently no ETA on when it will be fixed, and your best bet is to just skip the launcher for now.

It also seems like sometimes the original battle.net launcher is opened as I don't get any overlay features on it. I'm not 100% sure but I think this happens when a battle.net update agent is still running in the background after battle.net launcher have been closed.

You shouldn't be seeing any "overlay features" on the launcher itself, but ever since it recently had an update the overlay stuff has been showing up on it (when it's normally supposed to be hidden) -- This is also on Lax's todo list.

I was able to reproduce the issue and have told Lax about it. There is currently no ETA on when it will be fixed, and your best bet is to just skip the launcher for now.

Already done, good to know that I can stop trying to figure out what is wrong then

Will it say in release notes when it is fixed?