Close
Page 1 of 2 1 2 LastLast
Showing results 1 to 10 of 11
  1. #1

    Default ISBoxer loads only 4 instances instead of my 5 suddenly

    Well up till now innerspace seems to only want to load 4 of my 5 wow's. Tried loading the team again but to no avail. Up to now it was fine, and suddenly it decided to not load them all. I did notice a patch when I started innerspace wonder if it is connected?

  2. #2

    Default

    Hmm, updated ISBoxer Toolkit now and seems to have made things work now obviously did a export to inner space, hope this helps out someone who has the same issue though.

  3. #3

    Default

    Same Issue here. Most happens if i play my 5box team and then switch to 8box team. Only 7 WoWs will be loaded. I closed all windows try again... only 7 WoWs .. i restart my computer and all works fine.

  4. #4
    Multiboxologist MiRai's Avatar
    Join Date
    Apr 2009
    Location
    Winter Is Coming
    Posts
    6815

    Default

    If you have any Agent.exe processes hanging around in your Task Manager (before or after playing) then that can easily cause game clients to not load.
    Do not send me a PM if what you want to talk about isn't absolutely private.
    Ask your questions on the forum where others can also benefit from the information.

    Author of the almost unknown and heavily neglected blog: Multiboxology

  5. #5

    Default

    Right click Inner Space and select Console.

    In this Console window enter in "sessions" with no quotes. This will tell you all of the processes that Inner Space is handling. If it's not loading the 5th window, it likely already has something labelled as "is5" that shouldn't be, and it will be in this list.

    It might help to paste me that info for a permanent solution. You can Copy from the console by just click and drag -- highlight a rectangle of text and let go, and the highlighted text (and only that highlighted text) will be Copied for you to Paste.
    Lax
    Author of ISBoxer
    Video: ISBoxer Quick Start

  6. #6

    Default

    Ok, if that happens again then i will paste the console sessions.

    Just now though before I checked the forums one client loaded when i stepped away from the computer, when I came back and saw this selected the team again and the rest of the four loaded. If it helps I am running 64 bit clients, would running 32 bit clients be better?

  7. #7
    Multiboxologist MiRai's Avatar
    Join Date
    Apr 2009
    Location
    Winter Is Coming
    Posts
    6815

    Default

    Quote Originally Posted by drarkan View Post
    If it helps I am running 64 bit clients, would running 32 bit clients be better?
    It doesn't make much of a difference unless your computer, for some reason, specifically has a problem with one version of the client.
    Do not send me a PM if what you want to talk about isn't absolutely private.
    Ask your questions on the forum where others can also benefit from the information.

    Author of the almost unknown and heavily neglected blog: Multiboxology

  8. #8

    Default

    So here it is. I loaded a 5 man team, left it to load for a few, then I come back and opened the console. Says there's 2 instances, so I'm guessing one for the open window, and one for the console? Or it might be hanging trying to load the next wow? I don't have problems running 64 bit programs, I can run wow normally and play it and sometimes it loads the rest when I try to load the team again. Something is catching and saying "nope, not this time"

    I did reload the team and it seemed to load a couple more, says there's 5 processes but only 3 loaded

    1st try
    left monitor processes.jpgright monitor processes.JPG

    2nd try
    left monitor processes 2nd try.jpgright monitor processes 2nd try.JPG
    Last edited by drarkan : 11-09-2014 at 06:41 AM Reason: Tried to reload the team again, posted results

  9. #9

    Default

    Did a complete readout from the console, tried a 3rd time, no change. Seemed to think all 5 loaded then when I loaded the team again it recognized the 4th and 5th sessions weren't loaded, and failed to load them. I am noticing that my 4th instance Drarkantotem is trying to load wow.exe instead of the 64 bit version. I think I will try to redo the team in isboxer, and see how that goes. Not tonight however, time for bed.

    I do appreciate the responses thus far, I am confident we will sort this out.

    Code:
    [console] [`] Command (Release): console "toggle" 
    /====================================================
    |
    | 21:40:37 ISBoxer: Settings imported from ISBoxerToolkit.GeneralSettings.XML
    | 21:40:37 ISBoxer: Adding ISBoxer Character Sets menu
    | 21:40:37 ISBoxer: Adding Character Set 'Hyjal Team 2'
    | 21:40:37 ISBoxer: Adding Character Set 'Hyjal Druids'
    | 21:40:37 ISBoxer: Adding Character Set 'Shamans'
    | 21:40:37 ISBoxer: Adding Character Set '90 Dungeon Run'
    | 21:40:37 ISBoxer: Adding Character Set 'Main Instance Running'
    | 21:40:37 ISBoxer: Adding Character Set 'Hunter with Team'
    | 21:40:37 ISBoxer: Adding Character Set 'This is the real thing'
    | 21:40:37 ISBoxer: Instructions completed.
    |
    \====================================================
    There are 0 Inner Space files available for patching.
    /====================================================
    |
    | 02:14:49 ISBoxer: Preparing to launch Character Set 'Hyjal Team 2'
    | 02:14:49 ISBoxer: Settings imported from ISBoxerToolkit.GeneralSettings.XML
    | 02:14:49 ISBoxer: Making sure Characters in Character Set 'Hyjal Team 2' are valid...
    | 02:14:49 ISBoxer: Good!
    | 02:14:49 ISBoxer: Launching Character Set 'Hyjal Team 2' all slots...
    | 02:14:49 ISBoxer: Launching Slot 1 Character 'Drarkansan-Hyjal'
    Successfully executed '"I:\World of Warcraft\WoW.exe"'.
    Session launched (is1): "I:/World of Warcraft/WoW-64.exe"
    | 02:15:08 ISBoxer: Launching Slot 2 Character 'Drarkanbeef-Hyjal'
    Successfully executed '"I:\World of Warcraft\WoW.exe"'.
    | 02:18:09 ISBoxer: Character from Set 'Hyjal Team 2' not fully launched after 3 minutes.
    Select again to continue launching additional slots.
    | 02:18:09 ISBoxer: Instructions completed.
    |
    \====================================================
    Inner Space sessions
    ------------------
    is1 - PID 14056 - I:\World of Warcraft\Wow-64.exe
    World of Warcraft11328 - PID 11328 - I:\World of Warcraft\Wow-64.exe
    2 sessions
     
    /====================================================
    |
    | 02:35:35 ISBoxer: Preparing to launch Character Set 'Hyjal Team 2'
    | 02:35:35 ISBoxer: Settings imported from ISBoxerToolkit.GeneralSettings.XML
    | 02:35:35 ISBoxer: Making sure Characters in Character Set 'Hyjal Team 2' are valid...
    | 02:35:35 ISBoxer: Good!
    | 02:35:35 ISBoxer: Launching Character Set 'Hyjal Team 2' all slots...
    | 02:35:35 ISBoxer: Slot 1 already launched. Updating it to character
    'Drarkansan-Hyjal' in Character Set 'Hyjal Team 2'
    | 02:35:35 ISBoxer: Launching Slot 2 Character 'Drarkanbeef-Hyjal'
    Successfully executed '"I:\World of Warcraft\WoW.exe"'.
    Session launched (is2): "I:/World of Warcraft/WoW-64.exe"
    | 02:35:48 ISBoxer: Launching Slot 3 Character 'Drarkanstorm-Hyjal'
    
    Successfully executed '"I:\World of Warcraft\WoW.exe"'.
    Session launched (is3): "I:/World of Warcraft/WoW-64.exe"
    | 02:36:02 ISBoxer: Launching Slot 4 Character 'Drarkantotem-Hyjal'
    Successfully executed '"I:\World of Warcraft\WoW.exe"'.
    Inner Space sessions
    ------------------
    is1 - PID 14056 - I:\World of Warcraft\Wow-64.exe
    World of Warcraft11328 - PID 11328 - I:\World of Warcraft\Wow-64.exe
    is2 - PID 13388 - I:\World of Warcraft\Wow-64.exe
    is3 - PID 12708 - I:\World of Warcraft\Wow-64.exe
    World of Warcraft14416 - PID 14416 - I:\World of Warcraft\Wow-64.exe
    5 sessions
    | 02:39:03 ISBoxer: Character from Set 'Hyjal Team 2' not fully launched after 3 minutes.
    Select again to continue launching additional slots.
    | 02:39:03 ISBoxer: Instructions completed.
    |
    \====================================================
     /====================================================
    |
    | 02:42:12 ISBoxer: Preparing to launch Character Set 'Hyjal Team 2'
    | 02:42:12 ISBoxer: Settings imported from ISBoxerToolkit.GeneralSettings.XML
    | 02:42:12 ISBoxer: Making sure Characters in Character Set 'Hyjal Team 2' are valid...
    | 02:42:12 ISBoxer: Good!
    | 02:42:12 ISBoxer: Launching Character Set 'Hyjal Team 2' all slots...
    | 02:42:12 ISBoxer: Slot 1 already launched. Updating it to character
    'Drarkansan-Hyjal' in Character Set 'Hyjal Team 2'
    | 02:42:12 ISBoxer: Slot 2 already launched. Updating it to character
    'Drarkanbeef-Hyjal' in Character Set 'Hyjal Team 2'
    | 02:42:12 ISBoxer: Slot 3 already launched. Updating it to character
    'Drarkanstorm-Hyjal' in Character Set 'Hyjal Team 2'
    | 02:42:12 ISBoxer: Launching Slot 4 Character 'Drarkantotem-Hyjal'
    Successfully executed '"I:\World of Warcraft\WoW.exe"'.
    | 02:45:12 ISBoxer: Character from Set 'Hyjal Team 2' not fully launched after 3 minutes.
    Select again to continue launching additional slots.
    | 02:45:12 ISBoxer: Instructions completed.
    |
    \====================================================

  10. #10

    Default

    Says there's 2 instances, so I'm guessing one for the open window, and one for the console? Or it might be hanging trying to load the next wow?
    No, the console you're screenshotting is running in InnerSpace.exe, not in wow.exe or wow-64.exe. What you're seeing is that sometimes something on your PC is making it hang when the game instance is trying to load up.

    I am noticing that my 4th instance Drarkantotem is trying to load wow.exe instead of the 64 bit version.
    That's normal and it is doing it for all 5 instances. wow.exe auto re-launches as wow-64.exe.

    .. like this!
    Code:
    | 02:14:49 ISBoxer: Launching Slot 1 Character 'Drarkansan-Hyjal'
    Successfully executed '"I:\World of Warcraft\WoW.exe"'.
    Session launched (is1): "I:/World of Warcraft/WoW-64.exe"
    So we need to determine why it's hanging for you. At this point I want both kinds of ISBoxer's Diagnostics from you. Diagnostics for game crashes from any wow launched by IS, and Diagnostics for game freezes specifically from a hung instance (you can close the ones that are not hung to narrow it down). One thing to note, you will have to either rename wow-64.exe temporarily (launch your team after) or tell the game not to relaunch as 32-bit via a setting, because ISBoxer is currently unable to do the diagnostics on a 64-bit process.
    Lax
    Author of ISBoxer
    Video: ISBoxer Quick Start

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •