[wow] team doesnt fully launch

[hpavc]

When I launch my teams, often the whole team wont launch.

The problem is always with the newest runtime wow-64.exe that is very small in memory usegae compared to its other pids that are at the login screen.

I have a powershell script to kill the youngest wow-64.exe and then "d:\InnerSpace\InnerSpace.exe run isboxer -launch "teamname" over again, but its sort of chore.

Is there a innerspace / isboxer setting to work through this? I thought there was a thread on this already (maybe its on d-b.com) where the discussion was on taskmgr and killing that pid.

Thanks!

[bob]

Are you on Windows 10? If so, then you should set Inner Space to be 64bit or use the 32bit WOW. Windows 10 has (had?) an issue launching 64 bit processes from a 32 bit process. This may have been attempted to be "fixed" in the latest W10 update. You can always try the below anyway!

Setting Inner Space to 64 bit can be achieved by selecting the ISBoxer node in top left pane, and ticking the "Use 64bit Inner Space" tick box. To use 32bit WOW set the -noautolauch64bit parameter to your game profile http://isboxer.com/wiki/Game_Profile, or delete/rename the wow-64.exe (this get re-installed on patching I believe).

If that doesn't work, try the Development Build of Inner Space. Right click the Inner Space icon, select Patcher, tick (red dot) the option for Development patches. Exit Inner Space and restart it to allow it to patch. If you are already on the Development build, then untick, exit and restart and let it patch back to release.

If that doesn't work, you should provide a Diagnostic http://isboxer.com/wiki/Diagnostics

I had a few times where it would only launch one or two of my wow instances as well.
To remedy that I found that while switching teams/or loading up a set I always just re-export to IS first then que up the team.

No issues since then.

Windows 7 here.

[hpavc]

Sorry for the delay, using Windows 7.

I have changed the game profile a few times.