Launch speed?

Hey,

In games with launchers (LOTRO, specifically) the launcher runs, verifies the patch, checks the server availability and then green-lights the play button. When you multiply this by 6, the launch process can take several minutes. Alternatively, you can individually launch each window one after the other (ISBoxer Character Set Slots > *Team > *Character), let them all load together, then press play. The process is much quicker.

So, is there a way to configure ISBoxer to launch each slot immediately one after the other? I'm aware of the "Launch each character X seconds . . ." setting but that doesn't seem to do what I'm looking for. It still waits for the launcher to run the actual game client before starting the subsequent launcher.

Cheers.

[bob]

That's the nature of the most MMO launchers. You can only have one instance of the launcher running at a time. Some games, like WoW havea login process built into the client. LOTRO does not, so you are stuck with the launcher. ISBoxer2 will speed this process up a bit, but the actual login process will still take some time.

You can however use third party launchers, like pyLotro or similar. I ended up writing one myself because of other issues with the Turbine Launcher (and their nosey monitoring process). There is some detail on this post. They way it works currently means there is a little setup needed in InnerSpace, and setting your characters to use the appropriate game profile. I have 14 separate profiles currently (ISBoxer2 will allow me to revert to one hopefully). Because it has all the necessarily login info setup then I can start the team, and they will all load and login themselves to the char select screen.

LOTRO does let you run multiple instances of the launcher. If you launch each slot manually through Innerspace, you can run all 6, let them load and then click play all at once.

I just can't figure out how to configure ISBoxer to do this when I launch the team, so I don't have to click through each slot manually.

[bob]

There is no setting in ISBoxer for you to do this, because the launcher previously did not let you load multiple instances of it at the same time (unless you had separate game installs). It also allows detection of when a character fails to load, and prevents further loading, and stops InnerSpace/ISBoxer from getting confused as to which slot is which, and because ISBoxer is coded to load the team sequentially.

ISBoxer2 speeds up the launch process quite significantly, and may even be able to do what you want. That is just a waiting game.

In the meantime you can use other methods to speed up the process.

Fair enough, thanks for the info.

The custom launcher does look interesting. I'll check it out.

Tried your launcher. It just crashes immediately when you attempt to launch. There have been some changes to the Turbine servers as well as to the launcher and client over the last 12 months that might not be compatible.

Code:

Problem signature:
  Problem Event Name:   BEX
  Application Name:   cmdlineTurbineLauncher.exe
  Application Version:   1.0.0.0
  Application Timestamp:   56171bed
  Fault Module Name:   StackHash_c6a8
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   00000000
  Exception Offset:   775764a0
  Exception Code:   c0000005
  Exception Data:   00000008
  OS Version:   6.1.7601.2.1.0.768.3
  Locale ID:   3081
  Additional Information 1:   c6a8
  Additional Information 2:   c6a803a74771486bff3065c4c68369d9
  Additional Information 3:   8e27
  Additional Information 4:   8e2776385c184ea72c913d7b6983d29f

[lax]

The launcher works fine; is this crash when used with Inner Space/ISBoxer or without?

If you're using the Inner Space development build, then you need to let Inner Space update to build 6120 to fix the crash. 6119 will cause a crash with this launcher.