ISBoxer opening sessions with wrong ID

Hello,

Recently I am starting to have issues when opening my group on ISBoxer. I have configured a team of 5 a while back with Windowlayout like Mirai had. 5 slots + 1 dxnothing slot where you insert the VXFeed for each session. The issue is, ISboxer should startup opening sessions in this order: is1, is2, is3, is4, is5. is6 being dxnothing. It worked without issues till last week, when it started doing odd stuff. ISboxer opens sessions skipping some numbers. And its not always the same.

For example right now it opened is1, then skipped is2 and opened is3 instead of 2. obviously isboxer gives a warning stating this sessions should have character for is3 not is2. When I close is3, and re-run to team again sometimes it works. This time it failed again. It opened is1, is2, then skipped is3 and opened is4. On the third restart it opened is1, is2, is3, is4, skipped is5 and opened is6.

Sometimes it works right on the first go. Right now I am on my 5th restart (I have closed innerspace and isboxer as well) and still giving me trouble. Any had issues like this before?

P.S. On the 9th try it all opened as it should... I have not changed any configuration since I made my team to work as I wanted. Thats being almost 4 months ago.

When you're all the way out of the game on all clients, do any still show up in the process list?

Normally this only happens when you have processes from a previous session that have not closed correctly and the process is still actually running (you can see this in Task Manager), or, perhaps the game you are playing has had a patch update, and the devs have introduced a secondary process, usually a "monitor" type process that ISBoxer does not know about, so it counts that secondary process as a second slot launch.

I will have to check them out. On the previous session not closed correctly I have to check but it does happen when I open up the game fresh from a restart too. Ughmahedhurtz I don't really understand your question. When all my clients are started up, on process it shows all 5 wow clients if that is what you mean. It could have been the patch 6.2.4 but am uncertain on that.

I will keep trying on the work around but its annoying none the less. It was working fine till now.

Right-click the taskbar -> Task Manager -> Details tab -> should see no "Wow.exe" or "Wow-64.exe" processes in the list. (Sort by name for easier viewing)

Just making sure it isn't leaving an orphaned wow process behind due to some other bug, which is still associated with an is2, is3, etc. instance.

Same problem here, when i start a 5 box team mostly 2 of 5 are started while the 3rd instance is only loaded like 26 mb in taskmanager. so i have manually kill this instance in the taskmanager an launch again. why does this happen ? note this happens on fresh booted pc so no wow processes are online

I've never had this problem with wow instances, but have you tried changing "launch each character x seconds" to something more like 5 or 6? or 10? (I think it is 1 second by default).

Yes I have changed that. It was indeed set into 1. I have changed it to 3 and to no avail. I will try to delay a bit more see if it gets better.

Edit: Ok I just came back and with 5 seconds it still happened. Fresh from restart (had chrome opened with 5-7 tabs open. could this be the culprid? been doing this for a while and never had issues). I have changed it to 10 second delay and now it worked ok but I am uncertain. (too scared to try again. Will inform if it happens tommorrow as well).

Here is my config should I have something strange that is causing this:

http://pastebin.com/yCtdWRjs

Quote:

---

Originally Posted by Enoah35

Yes I have changed that. It was indeed set into 1. I have changed it to 3 and to no avail. I will try to delay a bit more see if it gets better.

Edit: Ok I just came back and with 5 seconds it still happened. Fresh from restart (had chrome opened with 5-7 tabs open. could this be the culprid? been doing this for a while and never had issues). I have changed it to 10 second delay and now it worked ok but I am uncertain. (too scared to try again. Will inform if it happens tommorrow as well).

Here is my config should I have something strange that is causing this:

http://pastebin.com/yCtdWRjs

---

I'd probably recommend changing your CPU affinity and assign all slots to all cores to see if that changes anything, but you can also open up the in-game Inner Space console (enable it in your Character Set) and then type sessions. Copy and paste what it shows and share it here (you can copy the console by simply holding the left mouse button and dragging the cursor across the text you wish to highlight).

Will do and let you guys know when I get back from work. Thanks.

Edit: Ok today it worked just fine. Did as you asked on changing the cpu cores from 2 to every core on each character. Also delayed the instance start to 10 second. Will see if this issue is now fixed.

I can confirm that I too see this problem way more than I would like to. I don't make use of DXDIAG windows, just straight up IS1-5 client windows, all on one monitor and use window swapping (wheel switcher enabled with the 'c' key).

Too often, after logging in I'll go to switch characters and it will be messed up. Going from IS1 to IS5 instead of IS2, plus many more different scenarios of improper switching.

This is a problem I had when I picked up boxing again last year. CPU changes does nothing, extending client launch time does nothing. I can even launch clients by a 'per slot basis' and after all 5 are loaded this way the order will still be wrong switching switching screens.

Very, very frustrating! The only fix I have found (which is mostly luck) is to test switching clients after everything is loaded in. If it worked that time I can play, if not I'll close down and reload the clients.

Or, not tested thoroughly enough as it might just be coincidence, but it seems a couple of times when I deleted the config.wtf files for the individual characters and then tried again everything booted up just fine.

Would love to find a solution to this problem!

Yeah thats what I have been doing too. Maybe yesterday I was lucky. Will check if today after work if things go bonkers again. Normally with 1 restart after finding out that ISboxer has opened the wrong session, closing and stopping the opening sequence and reloading did the trick. But the day I posted I had to do it 9 times. Took like... an hour to open all sessions correctly.

P.S. if it happens again, going to post on the ISBoxer forums, see if anyone in there can give me a hand on understanding what is going on.

P.P.S. Tried today too and it worked fine. Unsure the cause but the delay + CPU is working for me. for now.

I think I may have found the problem. Need another IsBoxer update to test.

So setting all clients to use all CPU's instead of an 'per' core basis did not work.
Setting the startup time from '1' to 5, 10, 15 seconds did not work.

However, I think the problem is when IsBoxer updates itself it re-installs a shortcut on my desktop. When that shortcut is re-created, the shortcut itself loses the Admin settings.

As soon as I changed the shortcut to 'run as administrator', like it was when I first installed IsBoxer all my client switching worked like a charm. Multiple client startups.

I believe this is what the problem was (windows 7, 64). I'll double check the next time I get an IsBoxer update to see if it is in fact removing Admin privileges. As a quick test though, I did remove admin privileges and sure enough my window swapping sequence did not work anymore.

​It happened again. Although this time it work on the second run. I will check the shortcut if its runing as admin or not.

Ok I managed to find the Console activation in ISBoxer. However when I type sessions, it returns me with unknown command.

Quote:

---

Originally Posted by Enoah35

Ok I managed to find the Console activation in ISBoxer. However when I type sessions, it returns me with unknown command.

---

Sorry, my instructions were incorrect. It actually has to be the main Inner Space console (right-click on the crosshairs tray icon and choose Console from there).

Hello.

Today it worked properly. Not sure what is causing it but when it is working properly in the console the sessions shows up like this.

is6 - PID 2404 - C:\InnerSpace\dxNothing.exe
is1 - PID 9752 - C:\World of Warcraft\Wow-64.exe
is2 - PID 10800 - C:\World of Warcraft\Wow-64.exe
is3 - PID 9128 - C:\World of Warcraft\Wow-64.exe
is4 - PID 1040 - C:\World of Warcraft\Wow-64.exe
is5 - PID 7040 - C:\World of Warcraft\Wow-64.exe
6 sessions

I will try to run the same when it opens the wrong sessions. Will keep you updated.

Update. IS5 got skipped and opened IS6, Dxnothing opened IS7. Here is the console result:

/================================================== ==
|
| 06:48:46 ISBoxer: Preparing to launch Character Set 'FullGroup'
| 06:48:46 ISBoxer: Settings imported from ISBoxerToolkit.GeneralSettings.XML
| 06:48:46 ISBoxer: Making sure Characters in Character Set 'FullGroup' are valid...
| 06:48:46 ISBoxer: Good!
| 06:48:46 ISBoxer: Launching Character Set 'FullGroup' all slots...
| 06:48:46 ISBoxer: Launching Slot 1 Character 'Katejina-Runetotem'
Session name 'Battle Net Launcher7756' accepted for process C:World of WarcraftWorld of Warcraft
Launcher.exe
Session name 'is50' accepted for process C:World of WarcraftWorld of Warcraft Launcher.exe
Session name 'Battle Net Launcher7524' accepted for process C:ProgramDataBattle.netAgentAgent.exe
Session name 'is51' accepted for process C:ProgramDataBattle.netAgentAgent.exe
Session name 'Battle Net Launcher6476' accepted for process
C:ProgramDataBattle.netAgentAgent.4908Agent.exe
Session name 'is52' accepted for process C:ProgramDataBattle.netAgentAgent.4908Agent.exe
Session name 'Battle Net Launcher10540' accepted for process C:Program Files
(x86)Battle.netBattle.net.exe
Session name 'is51' accepted for process C:Program Files (x86)Battle.netBattle.net.exe
Session name 'Battle Net Launcher3740' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net.exe
Session name 'Battle Net Launcher6256' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net Helper.exe
Session name 'is1' accepted for process C:Program Files (x86)Battle.netBattle.net.7113Battle.net
Helper.exe
Session name 'Battle Net Launcher6492' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net Helper.exe
Session name 'Battle Net Launcher5268' accepted for process C:World of WarcraftWow-64.exe
Session name 'is1' accepted for process C:World of WarcraftWow-64.exe
Session launched (is1): "C:/World of Warcraft/Wow-64.exe"
| 06:49:32 ISBoxer: Launching Slot 2 Character 'Elliera-Runetotem'
Successfully executed '"C:\World of Warcraft\World of Warcraft Launcher.exe"'.
Session name 'Battle Net Launcher13136' accepted for process C:World of WarcraftWorld of Warcraft
Launcher.exe
Session name 'is50' accepted for process C:World of WarcraftWorld of Warcraft Launcher.exe
Session name 'Battle Net Launcher9816' accepted for process C:ProgramDataBattle.netAgentAgent.exe
Session name 'is51' accepted for process C:ProgramDataBattle.netAgentAgent.exe
Session name 'Battle Net Launcher12004' accepted for process
C:ProgramDataBattle.netAgentAgent.4908Agent.exe
Session name 'is53' accepted for process C:ProgramDataBattle.netAgentAgent.4908Agent.exe
Session name 'Battle Net Launcher10500' accepted for process C:Program Files
(x86)Battle.netBattle.net.exe
Session name 'is51' accepted for process C:Program Files (x86)Battle.netBattle.net.exe
Session name 'Battle Net Launcher10368' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net.exe
Session name 'is50' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net.exe
Session name 'Battle Net Launcher11052' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net Helper.exe
Session name 'is2' accepted for process C:Program Files (x86)Battle.netBattle.net.7113Battle.net
Helper.exe
Session name 'Battle Net Launcher452' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net Helper.exe
Session name 'Battle Net Launcher9052' accepted for process C:World of WarcraftWow-64.exe
Session name 'is2' accepted for process C:World of WarcraftWow-64.exe
Session launched (is2): "C:/World of Warcraft/Wow-64.exe"
| 06:50:31 ISBoxer: Launching Slot 3 Character 'Ayaka-Runetotem'
Successfully executed '"C:\World of Warcraft\World of Warcraft Launcher.exe"'.
Session name 'Battle Net Launcher5740' accepted for process C:World of WarcraftWorld of Warcraft
Launcher.exe
Session name 'is50' accepted for process C:World of WarcraftWorld of Warcraft Launcher.exe
Session name 'Battle Net Launcher6860' accepted for process C:ProgramDataBattle.netAgentAgent.exe
Session name 'is51' accepted for process C:ProgramDataBattle.netAgentAgent.exe
Session name 'Battle Net Launcher6268' accepted for process
C:ProgramDataBattle.netAgentAgent.4908Agent.exe
Session name 'is52' accepted for process C:ProgramDataBattle.netAgentAgent.4908Agent.exe
Session name 'Battle Net Launcher8532' accepted for process C:Program Files
(x86)Battle.netBattle.net.exe
Session name 'is51' accepted for process C:Program Files (x86)Battle.netBattle.net.exe
Session name 'Battle Net Launcher3988' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net.exe
Session name 'is50' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net.exe
Session name 'Battle Net Launcher5788' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net Helper.exe
Session name 'Battle Net Launcher12860' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net Helper.exe
Session name 'Battle Net Launcher8260' accepted for process C:World of WarcraftWow-64.exe
Session name 'is3' accepted for process C:World of WarcraftWow-64.exe
Session launched (is3): "C:/World of Warcraft/Wow-64.exe"
| 06:51:54 ISBoxer: Launching Slot 4 Character 'Maanya-Runetotem'
Successfully executed '"C:\World of Warcraft\World of Warcraft Launcher.exe"'.
Session name 'Battle Net Launcher6148' accepted for process C:World of WarcraftWorld of Warcraft
Launcher.exe
Session name 'is50' accepted for process C:World of WarcraftWorld of Warcraft Launcher.exe
Session name 'Battle Net Launcher3568' accepted for process C:ProgramDataBattle.netAgentAgent.exe
Session name 'is51' accepted for process C:ProgramDataBattle.netAgentAgent.exe
Session name 'Battle Net Launcher11064' accepted for process
C:ProgramDataBattle.netAgentAgent.4908Agent.exe
Session name 'is53' accepted for process C:ProgramDataBattle.netAgentAgent.4908Agent.exe
Session name 'Battle Net Launcher4420' accepted for process C:Program Files
(x86)Battle.netBattle.net.exe
Session name 'is51' accepted for process C:Program Files (x86)Battle.netBattle.net.exe
Session name 'Battle Net Launcher5716' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net.exe
Session name 'is50' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net.exe
Session name 'Battle Net Launcher260' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net Helper.exe
Session name 'Battle Net Launcher7176' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net Helper.exe
Session name 'is4' accepted for process C:Program Files (x86)Battle.netBattle.net.7113Battle.net
Helper.exe
Session name 'Battle Net Launcher9872' accepted for process C:World of WarcraftWow-64.exe
Session name 'is4' accepted for process C:World of WarcraftWow-64.exe
Session launched (is4): "C:/World of Warcraft/Wow-64.exe"
| 06:54:21 ISBoxer: Launching Slot 5 Character 'Manaka-Runetotem'
Successfully executed '"C:\World of Warcraft\World of Warcraft Launcher.exe"'.
Session name 'Battle Net Launcher3328' accepted for process C:World of WarcraftWorld of Warcraft
Launcher.exe
Session name 'is50' accepted for process C:World of WarcraftWorld of Warcraft Launcher.exe
Session name 'Battle Net Launcher10452' accepted for process
C:ProgramDataBattle.netAgentAgent.exe
Session name 'is51' accepted for process C:ProgramDataBattle.netAgentAgent.exe
Session name 'Battle Net Launcher5740' accepted for process
C:ProgramDataBattle.netAgentAgent.4908Agent.exe
Session name 'is52' accepted for process C:ProgramDataBattle.netAgentAgent.4908Agent.exe
Session name 'Battle Net Launcher10088' accepted for process C:Program Files
(x86)Battle.netBattle.net.exe
Session name 'is51' accepted for process C:Program Files (x86)Battle.netBattle.net.exe
Session name 'Battle Net Launcher7500' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net.exe
Session name 'is50' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net.exe
Session name 'Battle Net Launcher9400' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net Helper.exe
Session name 'is5' accepted for process C:Program Files (x86)Battle.netBattle.net.7113Battle.net
Helper.exe
Session name 'Battle Net Launcher8236' accepted for process C:Program Files
(x86)Battle.netBattle.net.7113Battle.net Helper.exe
Session name 'Battle Net Launcher5980' accepted for process C:World of WarcraftWow-64.exe
Session name 'is6' accepted for process C:World of WarcraftWow-64.exe
Session launched (is6): "C:/World of Warcraft/Wow-64.exe"
| 06:55:05 ISBoxer: Launching Slot 6 Character 'dxnothing'
Successfully executed '"C:\InnerSpace\dxNothing.exe"'.
| 06:55:05 ISBoxer: ... no more Slots to launch
| 06:55:05 ISBoxer: Character Set 'FullGroup' launched
| 06:55:05 ISBoxer: Instructions completed.
|
\================================================= ===
Session name 'dxnothing12412' accepted for process C:InnerSpacedxNothing.exe
Session name 'is7' accepted for process C:InnerSpacedxNothing.exe
Session launched (is7): "C:/InnerSpace/dxNothing.exe"
Inner Space sessions
------------------
is7 - PID 12412 - C:\InnerSpace\dxNothing.exe
is1 - PID 5268 - C:\World of Warcraft\Wow-64.exe
is2 - PID 9052 - C:\World of Warcraft\Wow-64.exe
is3 - PID 8260 - C:\World of Warcraft\Wow-64.exe
is4 - PID 9872 - C:\World of Warcraft\Wow-64.exe
is6 - PID 5980 - C:\World of Warcraft\Wow-64.exe
6 sessions






Hope it clarifies something.

It can be seen in the log where it goes wrong..

Quote:

---

<snip>
Session name 'is5' accepted for process C:Program Files (x86)Battle.netBattle.net.7113Battle.net
Helper.exe
<snip>

---

For some reason, this helper process got picked up as initialising D3D so was given a session name.
You could try having Inner Space launch WoW-64.exe directly, rather than use the World of Warcraft Launcher.exe. This might alleviate the problem.
This seems to have begun recently for the odd user when Inner Space was changed to load 64bit when it was on an appropriate OS. This was to prevent a regular issue for people on Windows 10 and WoW. If you did not have any issue with Inner Space loading 32bit, but WoW being 64bit, you could try using forcing 32bit Inner Space. Details can be found here.. http://www.isboxer.com/forum/viewtop...p=36827#p36827


The other choice would be to set up your configuration to not be slot specific, or, where it is, use other targeting methods to determine the loading order, but without being slot numbers.

e.g.
Don't use the Wheel Switcher bind in the Window Layout, use the Always On -> Next Window mapped key (you should probably set the Filter Target for this to "@isboxer&~dxnothing" w/o the quotes, or just "@isboxer" if you want to be able to switch to the dxnothing)
Set your mapped key targets, are set to something like "(@isboxer)#1" when you want the first loaded slot or "(@isboxer)#6" for the sixth slot, rather than using "1" or "6".

More info on Targets can be found here.. http://www.isboxer.com/wiki/Target

nb. If you are using the slot variables in the Game Helper WoW macros, these should still work as they are evaluated on export.

Quote:

---

@isboxer&~dxnothing

---

.... You just made my setup 2% cleaner. I've been creating action groups that do nothing but exclude dxnothing for years.

Quote:

---

Originally Posted by luxlunae

.... You just made my setup 2% cleaner. I've been creating action groups that do nothing but exclude dxnothing for years.

---

Glad to help. While off topic, it may be more helpful to know that that target tends to assume you have a Character or ATG called dxNothing. Personally I create an ATG, and then drop my dxNothing characters into it; dxLeft, dxRight, dxBottom... etc. My most convoluted setup had 6 dxnothing surfaces. Works great.