Oculus App vs SteamVR vs desktop link

[Spectre-63]

Hi guys -

apologies if this a documented issue - for one of the few times I could not come up with an idea how to search for the solution.

Here's the issue: a week or so ago, I sat down to launch Elite as normal (thru the Oculus Library) and I got an error about not being able to contact the license server. I backed out, rebooted, retried - no difference. I launched it from my existing link on my desktop (Steam App) and it launched without issue, but VR was not activated. I backed out, launched direct from SteamVR and it worked. I'm trying to figure out how to get all this "in sync" since I'm guessing the Oculus app is launching directly to EliteDangerous64.exe rather than using the launcher.

Thanks in advance for any assistance!

Mike

 

[Crank Larson]

I found that if I have the SteamVR application open when I run E: D then the performance in-game is noticeably worse and stutters. I run E: D from the launcher with just the Oculus software running, and that works fine.

I also haven't been able to run from the Oculus library, though - not sure if it is expected to work that way.

 

[mahoon]

I think OP is right in that Oculus Home links direct to the exe, which ED doesn't like. I don't believe there's anyway to select the path the link on Oculus Home points to at the moment. I can't run it from Oculus Home because I just use the desktop version (not Steam or Oculus version). I'm sure they (Oculus devs) will add a way to select the path for the link in the future, but for now, no joy.

 

[heretowatch]

Back in the days of 2D, I ran ED through Steam. After getting the Rift I was experiencing unpredictable results so I got my feature key from Frontier and installed the game from the Oculus store. Running it from the Oculus library works perfectly, no issues. However, it opens directly into the game so I'll have to figure out how to get the launcher to show up if I want to try the beta.

 

[CMDR Oilik]

Same issue as you. FDEV must something changed, because now i'm not able to start ED from Oculus library (steam version). I tryed EDprofiler and if i have VR enabled profile and launch it from this utility - it works.

 

[Moonax IRL]

I just start from the ED launcher itself as always (non steam version) and oculus will fire up itself, but I have the debug tool running to boost the pixels. Never have any issue.

 

[Mxpower76]

Oculus home launch for ED only worked for me once or twice right after the Oculus update. I have the steam version and I get the login error. Guessing Frontier did something with the servers after that.

 

[Spectre-63]

This is one of the things that has me confused: If I launch from the desktop icon (which points to Steam), it doesn't see the Oculus, even if I have the Oculus tool running - there is no option to select the HMD. At the moment, the only option to launch and get VR is to launch from the SteamVR app.

 

[Hiluksi]

Try launching EDLaunch.exe directly from your Elite install folder. Should be under steamapps if steam-version.

 

[Crank Larson]

so I got my feature key from Frontier and installed the game from the Oculus store. Running it from the Oculus library works perfectly, no issues.

This appears to be the key to it (see what I did there? ). I went to Frontier Store and generated my Oculus key too (same place you get your Steam key from, though I've not done that). You can then redeem the Oculus key in the Oculus software, and it will download and install E: D. You can then run that installation from Oculus.

 

[Spectre-63]

Using EDLauncher seems to have resolved the launching issue - I guess the part I"m still confused by is how many configuration files are currently in place? It sounds almost as if Oculus, Steam, and SteamVR are each holding their own configuration?

 

[VR andysonofbob]

I find launching the game direct from Frontier Launcher is the best all round experience: least number problem, best performance (compared to SteamVR).

 

[TorTorden_VR]

I found that if I have the SteamVR application open when I run E: D then the performance in-game is noticeably worse and stutters. I run E: D from the launcher with just the Oculus software running, and that works fine.

I also haven't been able to run from the Oculus library, though - not sure if it is expected to work that way.

First time you launch from home it starts the launcher that you have to login into with your frontier account.
This doesn't work inside the HMD.
If you abort and close oculus will also close the launcher.

All subsequent times oculus still start the launcher. It just uses the stored login and autostart ed horizons. And close the launcher when you exit the game.