Can't instance with an alt on the same PC?

[Nadreck]

In my case, I bought my original game from Steam a couple of years ago (which is why it runs directly from a launcher rather than via Steam, this has since been changed), plus additional accounts directly from Frontier.

I didn't then need to "reinstall" the game, merely copying my existing folder was enough. I then activated a launcher in each new copy using the email address I'd used for each Frontier purchase.

If you've run multiple CMDR's on the same PC before, but not synchronously, you will probably have shortcuts that now point to the wrong place: to additional launchers in your original installation folder, rather than to the new folder. The location of the launcher in your file structure matters.

 

[Factabulous]

Pretty sure I have a weird file structure (it's an old old install) where the game files don't sit under the launcher. They call it the 'alternative' location in the support page - for some reason the game files are in C:\Users\%username%\AppData\Local\Frontier_Developments\Products\elite-dangerous-64\ (I know, I know - I didn't pick it - it is listed in the standard where to find stuff places so I guess it was the default at some stage).

If I could work out why it has chosen to do that .... don't fancy a full reinstall as 'something' will go missing.

Edit: Hmm, ok - think I'll try moving the game install to the 'normal' location and see if the launcher still works - as soon as I get to Hutton ...

 

[GroG79]

Do you use upnp? It might be that the routing to the other game is broken. Check what port numbers your .exe's are running. These ports should be open to the internet (ED servers)

 

[Globusdiablo]

...I then tested the effectiveness of this disappearing trick in a dangerous situation. When fuel-scooping in the Courier, I could menu-log immediately at low temperature, but was given the 15-second countdown when above 80% heat. So I tried again with a pending multicrew invitation, accepted the invitation when hot, and was given a 15-second countdown again: you can't immediately "multicrew-log" when in danger.

Nice find. So no new CL method then.

 

[Koben]

If I could work out why it has chosen to do that .... don't fancy a full reinstall as 'something' will go missing.

I have the very same old install and here what I do to get all CMDRs running simultaneously on the same PC:

1. A folder with game files for each commander;
2. A shortcut on desktop pointing to each launcher;
3. Open 1st account launcher, load the game and close the launcher after Elite starts running;
4. Open 2nd account launcher, load the game and close the launcher after Elite starts running;
5. All commanders shall share the same keybinds... as they will load up based on the settings on C:\Users\%username%\AppData\Local\...

 

[Biff Stryker]

I am running an Oculus launched version and a steam launched version at the same time. I am working on setting up a second HMD on another PC that will run the steam account in VR. My plan is to be able to multicrew up and have my daughter ride with me as she is learning to play. Unfortunately my wife cant stand to even watch the tv when I am in combat or screwing around, makes her motion sick so VR is out of the question She can play certain games but not like ED. If everything works out the way I want I'll probably get a third account to tinker in the bubble.

 

[Drelthar]

You just had an instancing issue. Nothing special.

 

[lenna]

Inclined to agree. Though I've never tested this out, it must be a bit strange for the system to try and manage two identical IPs in the same space.

Run them in virtual machines with dedicated pass-through graphics or each inside their own docker container and problem probably solved.

 

[Factabulous]

Run them in virtual machines with dedicated pass-through graphics or each inside their own docker container and problem probably solved.

... or just run them on the same box with none of that, just a sym link in the right place and looking at how wing beacons work - which I guess you'd need using your version too ....

But hey, if it works - all good

 

[John Stoutbeard]

Run them in virtual machines with dedicated pass-through graphics or each inside their own docker container and problem probably solved.

No need. As long as you have separated the installations (each character), and made different shortcuts for them you can run it on the same box.

 

[lenna]

No need. As long as you have separated the installations (each character), and made different shortcuts for them you can run it on the same box.

I was thinking about issues with network port conflicts - not necessarily an issue but I would not be surprised if it were.

 

[Factabulous]

I was thinking about issues with network port conflicts - not necessarily an issue but I would not be surprised if it were.

OP solved that issue some time ago

I used a nav beacon as a meeting-point, and had to get winged-up every time before approaching it in the second ship, despite both accounts being "friends" with each other: without the extra incentive from the wing, even friends in the same squadron don't seem to get instanced on the same PC. This time it worked (though it didn't work before even with the wing, must have been one of ED's "off days").