Session Naming Issue

Hi,

I've been using ISBoxer with Tera for months now with no issues, but ever since a patch a few weeks ago, I've found that occasionally window swapping (using slot activation) for my second character fails. After debugging this further, I noticed the window names are no longer assigned in the proper order. 1st one is is1, 2nd one which needs to be is2 is actually is3. Using the console I've run the session command and see that there is an instance of is2 out there somewhere, but it's not either of the TERAs I have running on my PC. If using the console I do a kill is2 while the 2nd slot is loading, eventually I can get things to work but it's hit or miss. Sometimes I end up with a black screen and have to repeat the process, sometimes the game loads but on is3, and then finally when it works the game loads on is2. Is this a known issue? Thanks.

[Alge]

Sounds like an issue with the patch. Are you referring to an InnerSpace/ISBoxer patch or a TERA patch?

[lax]

I've been using ISBoxer with Tera for months now with no issues, but ever since a patch a few weeks ago, I've found that occasionally window swapping (using slot activation) for my second character fails. After debugging this further, I noticed the window names are no longer assigned in the proper order. 1st one is is1, 2nd one which needs to be is2 is actually is3. Using the console I've run the session command and see that there is an instance of is2 out there somewhere, but it's not either of the TERAs I have running on my PC. If using the console I do a kill is2 while the 2nd slot is loading, eventually I can get things to work but it's hit or miss. Sometimes I end up with a black screen and have to repeat the process, sometimes the game loads but on is3, and then finally when it works the game loads on is2. Is this a known issue? Thanks.

No this is not a known issue with TERA, this is the first report. Some games launch extra processes, and in these cases I just need to instruct ISBoxer/Inner Space to ignore the extra processes.

The main IS console you're looking at should specify which executables are launched, when they launch. Like this...

Code:

Session launched (is1): "D:/Games/SomeGame/Game.exe"

Let me know, and I can take care of it

Thanks Lax,

It's "Session launched (is2): "C:/Program Files (X86)/Tera/Client/Binaries/Tera.exe"

[lax]

Okay. In that case, it sounds like you still have a tera.exe running from earlier... you can use the Windows Task Manager to find/kill any of these, or from the IS console type in "kill is2"

Okay. In that case, it sounds like you still have a tera.exe running from earlier... you can use the Windows Task Manager to find/kill any of these, or from the IS console type in "kill is2"

That's the thing, I've verified is2 doesn't exist prior to launching the 2nd slot, here's the exact steps I've taken:

1. Run "session" in console, confirm there's 0 sessions.
2. Launch slot 1, game gets loaded as is1 which is correct.
3. Run "session", 3 instances exist: tera4924, tera4300, and is1.
4. Assuming tera4924 & tera4300 are related to the launcher, I kill those, leaving only is1 active.
5. Launch slot 2, game loads in is3 which is wrong.
6. Run "session", have Ter5892, is1, is2, and is3.

If I spam "kill is2" WHILE the 2nd copy of the game is launching, sometimes I can clear it up, but it's not 100% reliable as either the game loads in is3 anyways, or it loads in is2 but is a black screen.

[firescue17]

I may be missing something as I'm not familiar with Tera. If so, disregard my inexperience.

Why are you launching two individual Characters as opposed to launching a single Character Set which contains two characters? Unless there is something unique to Tera, launching a two box should only require a single launch step?

I may be missing something as I'm not familiar with Tera. If so, disregard my inexperience.

Why are you launching two individual Characters as opposed to launching a single Character Set which contains two characters? Unless there is something unique to Tera, launching a two box should only require a single launch step?

Fair question - before this problem surfaced (reminder this was working fine for months), I did just that. Shortcut on desktop, launches the set with 2 chars in 1 step, no problem. Once this started happening though, the 2nd character would no longer launch, and using the shortcut for the set meant that each time I'd try to fight this to get it to work, I'd have to kill all the sessions and launch BOTH characters each attempt and pray it works. At least this way I can launch the first one, and just repeatedly launch/kill the 2nd one until finally it works.

Thanks for the help though.

[lax]

Okay. It sounds like there are additional processes that need to be filtered out, and hopefully they're not all Tera.exe.

Inner Space build 5921 (now the development build of Inner Space) now lists the PID and executables when using the Sessions command. This should make the listing a little more helpful in diagnosing this issue.

To try it out, right click IS and select Patcher, check "Download development (test) patches" and then close and restart Inner Space to let it patch up. Then you can break it and let me know what the new output says, and hopefully that will give me something to work with

Okay. It sounds like there are additional processes that need to be filtered out, and hopefully they're not all Tera.exe.

Inner Space build 5921 (now the development build of Inner Space) now lists the PID and executables when using the Sessions command. This should make the listing a little more helpful in diagnosing this issue.

To try it out, right click IS and select Patcher, check "Download development (test) patches" and then close and restart Inner Space to let it patch up. Then you can break it and let me know what the new output says, and hopefully that will give me something to work with

Ah, definitely a handy addition. To keep things simple for now, I didn't do any session killing, here were my steps:

1. Confirmed 0 sessions in inner space
2. Launched slot 1 (right-clicked inner space tray icon to do so)
3. Launcher spawned, logged in and launched the game
4. Once game finished loading, results of session:

a. Tera5668 - PID 5668 - c:\program files (x86)\tera\tera-launcher.exe
b. Tera7228 - PID 7228 - c:\program files (x86)\tera\client\TL.exe
c. is1 - PID 7520 - c:\program files (x86)\tera\client\binaries\tera.exe

5. Closed launcher window
6. Launched slot 2 (via inner space again)
7. New launcher window spawned, logged in and launched other game account
8. One loaded, results of session:

a. Tera6164 - PID 6164 - C:\program files(x86)\tera\tera-launcher.exe
b. Tera7228 - PID 7228 - c:\program files(x86)\tera\client\TL.exe
c. is1 - PID 7520 - c:\program files (x86)\tera\client\binaries\tera.exe
d. is2 - PID 2880 - c:\program files(x86)\tera\client\TL.exe
e. is3 - PID 7976 - c:\program files(x86)\tera\client\binaries\tera.exe

Guessing TL.exe is the culprit, game still worked fine when I killed all but c + e