Trouble Launching Second Account From IS

Gorthu · Post by **Gorthu** » Thu Sep 10, 2009 2:27 am

I'm trying to launch multiple instances of SWG from innerspace using the "IS Boxer character set". (I can launch multiple copies manually.)

I can Launch the first instacnce, but the second instance does not even start up.

Also when I try to lauch across computers, the second computer does not respond.

I have the "Enable incoming connections on port 10101" turned on for both computers. I can export to both computers from ISBoxer.

No error messages. Just no visible action.

Gorthu · Post by **Gorthu** » Thu Sep 10, 2009 2:32 am

I have the second character Set in the Also Launch in the First character set.

First character set has 2 characters in it and the "also launch set" has one character.

Gorthu · Post by **Gorthu** » Thu Sep 10, 2009 2:38 am

I think the problem for the fist issue (launching multiple instnaces on the same computer from IS) is the delay between launching - I need a longer wait time to allow for logging in. Can this be changed?

The second issue: The 2nd computer not launching altogether, should not be affected by the above.

Post by **Lax** » Thu Sep 10, 2009 9:00 am

There is no delay between launching anymore. The way it works is once the game has fully launched, the next character on the same PC launches. If it takes you longer than 60 seconds to get to that point, you will need to manually launch the next character by launching the character set again (it will launch only the missing characters). That's not usually the case, though. Usually it's something like the game is in full screen mode and the second one can't launch because of that -- so first make sure the game is in windowed mode

As far as the second PC goes, on both PCs you can select "Console" from the IS menu to see the console in the main program. When you launch your character set, it logs what it is doing to that console. If there is a problem launching a character or the remote character set, you can find out what the problem is by watching the output. If it can't connect to the remote PC, it will tell you on the main PC. If it connects fine and tells the remote PC to launch, but that PC can't launch the characters (for example because the selected game or game profile doesn't exist on that PC), it will tell you on the remote PC.

Gorthu · Post by **Gorthu** » Thu Sep 10, 2009 11:09 am

OK. I launch the ISBoxer-Set. It starts the first intance, if i'm fast enough, the second instance starts. If not, then I launch the ISBoxer-Set again. The Console messages tell me it's launching the second instance, but it doesn't.

The 2nd computer, it appears that innerspace isn't communicating. ISBoxer communicates between the computers, but not IS. I have the option in the configuration "Enable ...." checked (red button showing). Both computers show the same port selected.

My other problem, the mouse does not match up with window selections (i.e., i have to point below and off to the side to select options in game) - also, I can not move the mouse over the full game window - it's like hitting the edge of the monitor too soon.

Post by **Lax** » Thu Sep 10, 2009 11:33 am

OK. I launch the ISBoxer-Set. It starts the first intance, if i'm fast enough, the second instance starts. If not, then I launch the ISBoxer-Set again. The Console messages tell me it's launching the second instance, but it doesn't.

Interesting... Okay. For now you can get around this by launching again as I described.

The 2nd computer, it appears that innerspace isn't communicating. ISBoxer communicates between the computers, but not IS. I have the option in the configuration "Enable ...." checked (red button showing). Both computers show the same port selected.

This option and the port only matter on the second PC. If it "isn't communicating" then this should be clearly indicated on the main PC: it would say something like this (note that I am making up a name for the second PC, you should interpret MYSECONDPC as the name of your second PC) "Connection to MYSECONDPC on port 10101 failed". If it says that, then one of the following conditions must be true:
1. On MYSECONDPC, the Enable incoming connections option is disabled, or Inner Space has not been restarted after enabling incoming connections
2. On MYSECONDPC, the configured port number does not match what is shown in the message
3. MYSECONDPC is not the hostname of the second PC according to Windows
4. On MYSECONDPC, a firewall is blocking the incoming connection on port 10101 (but not port 10102 which is used for the ISBoxer communications)

If you used the Multiple Computer Helper to create the Computer info in ISBoxer, then #2 and #3 should not be the issue because it will generate it with what is configured in Inner Space. So unless you copied your Inner Space folder from one PC to another, or changed the "Uplink Name" in Inner Space to not match the computer name and then didn't tell ISBoxer how to contact the other PC, it should already be correct.

If that message does NOT appear in the main PC's console, then this is probably not the issue.

My other problem, the mouse does not match up with window selections (i.e., i have to point below and off to the side to select options in game) - also, I can not move the mouse over the full game window - it's like hitting the edge of the monitor too soon.

Sounds like something related to your Window Layout. You may need to uncheck the "Remove border around main window" option. Some games (notably EVE Online) also have a problem if the main window size configured in ISBoxer does not match the game's configured resolution. That can be fixed by adjusting the size of the main window region in your Window Layout, or you can try setting "Desired Rendering Size" to the game's configured resolution

Gorthu · Post by **Gorthu** » Thu Sep 10, 2009 11:51 am

Ok, I got the first two problems with launching solved now. It appeared that My settings didn't change when I made changes (The character-set on the second computer got identified as being on the first computer).

However, the mouse problem persists. I am using a Logitech MX518 mouse and a G15 (game) keyboard.

The mouse problem is with pointing. The pointer does not match up to the game window. Thus, I am unable to point to a target (or menu option)and select it.

Post by **Lax** » Thu Sep 10, 2009 12:30 pm

The mouse thing is related to your Window Layout, did you try what I suggested in my previous post?

Gorthu · Post by **Gorthu** » Thu Sep 10, 2009 1:39 pm

It appears to be working now. This is for SWG.

This is what i did:

I have windows mode and borderless windows selected on the SWG set up. The resolution you pick on the SWG window size must be the same as you use in innerspace, so type the size into the innerspace block that corresponds to the window.

In the the other windows, I kept the exact same scaling. That is, my main window is 1280x800, I made the others 640x400.

ATM, I am only using repeater to pass keys. But I am very happy. One of the issues I was having, was settings that I would make, somehow did save, or reverted when i moved around on ISBoxer. So I may not have been "clicking right". So things I thought I changed, didn't.

Thanks Lax. Great system you got here.

I only have one request (and it's because of SWG and logging in), instead of IS just automatically launching the second window, you might give me a manual popup button to say when to launch the next character. The problem I am encountering now: If I don't get the account launched in time, and IS tries to launch the next character, SWG for that second (..third) character continues to run the program, but with no window or response...fooling IS into thinking it's running the character. So relaunching from IS doesn't get it going.

Post by **Lax** » Thu Sep 10, 2009 6:27 pm

I only have one request (and it's because of SWG and logging in), instead of IS just automatically launching the second window, you might give me a manual popup button to say when to launch the next character. The problem I am encountering now: If I don't get the account launched in time, and IS tries to launch the next character, SWG for that second (..third) character continues to run the program, but with no window or response...fooling IS into thinking it's running the character. So relaunching from IS doesn't get it going.

Gotcha, yeah I will have to add an option you can set that will require you to launch each one manually