Oculus home version of Elite no longer bypassing launcher

dinknip · Dec 13, 2018

I have been messing around with keybinds for my new HOTAS setup, and have been doing so in normal desktop mode.
VR still works fine but now I have to take off my HMD and click start in the launcher as well, normally launching Elite from Oculus Home would bypass it, anyone have any idea how I can fix this? Can't seem to find any people with similar problems.
(More of an annoyance than an actual problem, but still)

Pallam93 · Dec 13, 2018

dinknip said:
I have been messing around with keybinds for my new HOTAS setup, and have been doing so in normal desktop mode.
VR still works fine but now I have to take off my HMD and click start in the launcher as well, normally launching Elite from Oculus Home would bypass it, anyone have any idea how I can fix this? Can't seem to find any people with similar problems.
(More of an annoyance than an actual problem, but still)

I have the same problems. I made a fresh install of windows and the game. the oculus libary won´t start the game anymore in VR. It opens the launcher, you click the game button and the game will start in Desktop mode. There must be something like a bug. Youre not alone.

Marcus Machiavelli · Dec 13, 2018

That was me yesterday, but today it just goes to 2D desktop mode! HELP!

Started through steam instead, all good.

TorTorden_VR · Dec 14, 2018

dinknip said:
I have been messing around with keybinds for my new HOTAS setup, and have been doing so in normal desktop mode.
VR still works fine but now I have to take off my HMD and click start in the launcher as well, normally launching Elite from Oculus Home would bypass it, anyone have any idea how I can fix this? Can't seem to find any people with similar problems.
(More of an annoyance than an actual problem, but still)

There is a brand new launcher, it most likely want's you to log in again.

And oculus doesn't bypass anything, it simply starts the launcher with the " /vr ", if you have the regular non oculus, non steam install you can make a desktop shortcut and appending that to the target box will work the same.

dinknip · Dec 14, 2018

TorTorden said:
There is a brand new launcher, it most likely want's you to log in again.

And oculus doesn't bypass anything, it simply starts the launcher with the " /vr ", if you have the regular non oculus, non steam install you can make a desktop shortcut and appending that to the target box will work the same.

Previously when Elite needs a new login one time was usually enough, and I am aware of the fact that it doesn't bypass anything, only runs it in the background and autoconfirms login details, but my point still stands.
Launching from Oculus Home no longer gets me directly into the game, not a huge problem, but an annoyance nonetheless.
Is there any way to change/edit launch options for games in Oculus Home?

LockOn · Dec 14, 2018

I cant start the game from the Oculus Home. It tells me that Log In failed. Nothing comes up that allows me to log in. How do I get to a log in screen from the oculus home that allows me to log in? Just really annoying once more.

Daddio · Dec 14, 2018

Seems I can not put the oculus home desktop into my game to watch my twitch chat anymore. Can bring it up, pin it, but when in game I am getting a big yellow ( ! ) instead of chat. Did oculus do something or is it on Elites end? Also same as above, I have to take off my rift and use my desktop after the rift brings up the Elite launcher to get the game started. Was not like this before.

Henri · Dec 15, 2018

had the same, nvidia drivers solved that but it's really annoying if i switch to Elite from something else in VR because i do not always run with monitor on.
So then i have to take off the Oculus, switch on the monitor and click run on the launcher, quite annoying

UmbraRex · Dec 15, 2018

Pallam93 said:
I have the same problems. I made a fresh install of windows and the game. the oculus libary won´t start the game anymore in VR. It opens the launcher, you click the game button and the game will start in Desktop mode. There must be something like a bug. Youre not alone.

This, exactly.

Select ED in Oculus home library and it opens the launcher but does nothing more. Select play horizons and it comes up in 2D

Use the … to select 'play in VR' and same results.

Wasp0 · Dec 15, 2018

Same here, but slightly different, when i press ED in the VR Library it does nothing, no launcher, no game no nothing. Done a fresh install of Oculus, fresh install of ED..... Nothing. ED works fine in VR if i start it from the Desktop Launcher, but starting that way and not through Oculus, means i can't pin anything.

Can someone, ANYONE throw a solution to this. Tried googling, nothing, tried OR forum, nothing!!

Appreciate any help from learned cmdrs on here!

Thanks

Dooguk · Dec 16, 2018

Both the ED patch 3.3 and the Oculus update 1.33 got released on the same day. So who do you blame?

My bet is the Oculus update as ED still works as normal from the launcher.

CMDR TerrBear · Dec 16, 2018

Having the same issue after attempting to install a second copy of ED to verify keybinds in 2D without knowing about "Desktop Mode". I agree, it's pretty annoying that it no longer skips the launcher versus it going straight into the game before. It feels like something was overwritten.

Someone above mentioned appending "/vr" to a target somewhere? I was also looking at the launch json file via Oculus Tray Tool's access to the Oculus Home library to see if maybe something was overwritten that disables the launcher bypass, but I'm not that fluent in locating where in that code it would be to tweak.

Hopefully someone can locate a fix for this. I'd imagine it's some simple tweak somewhere.

SimonNQ · Dec 17, 2018

Hi guys, I have had the same issue. I have found a workaround, it works for me, but would like someone else to test it before I say it is a fix etc...

Bacically, we edit the frontier-developments-plc-elite-dangerous.json.mini file and modify the start parameters as follows...

"launchParameters2D": "ED /vr /autoquit",

The original line is

"launchParameters2D": "ED",

My theory is that the launcher is incorrectly starting the game in 2d mode. By adding the above changes it is now passing the correct /vr to the launcher as it was before etc... There is a separate line that starts the game in VR mode, "launchParameters" but placing these changes on this line has made no difference.. Hence the "launchParameters2D" seems to be the correct line etc..

The file is located in the oculus direrctory/software/manifests and you can edit it with a txt editor.

Let me know if this works for anyone else...

Older Gamer · Dec 17, 2018

I play in a hotas chair so I launch the game from the app while I'm sliding the chair into position. This does work but I do have to press the play button on the monitor.

heretowatch · Dec 17, 2018

Dooguk said:
Both the ED patch 3.3 and the Oculus update 1.33 got released on the same day. So who do you blame? My bet is the Oculus update as ED still works as normal from the launcher.

Exactly. I blame Oculus in this case because Dash has been very unreliable since the update. I've had quite a few hard crashes.

dinknip · Dec 17, 2018

SimonNQ said:
Hi guys, I have had the same issue. I have found a workaround, it works for me, but would like someone else to test it before I say it is a fix etc...

Bacically, we edit the frontier-developments-plc-elite-dangerous.json.mini file and modify the start parameters as follows...

"launchParameters2D": "ED /vr /autoquit",

The original line is

"launchParameters2D": "ED",

My theory is that the launcher is incorrectly starting the game in 2d mode. By adding the above changes it is now passing the correct /vr to the launcher as it was before etc... There is a separate line that starts the game in VR mode, "launchParameters" but placing these changes on this line has made no difference.. Hence the "launchParameters2D" seems to be the correct line etc..

The file is located in the oculus direrctory/software/manifests and you can edit it with a txt editor.

Let me know if this works for anyone else...

Unfortunately this didn't work for me.
Been having a lot of other problems with Oculus Home as well since the update, floating hands, loss of tracking, HMD disconnects etc, going to try a clean install of everything next.

ganderbag · Dec 17, 2018

I followed your advice SimonNQ and had a look at an August 2018 copy of the 'frontier-developments-plc-elite-dangerous.json.mini' file that I had saved. My current Oculus app version is 1.33.0.750915. The CURRENT version of the file has the following 3 lines towards the bottom of the file:

"launchParameters": "ED",
"launchFile2D": "ORID.exe",
"launchParameters2D": "ED",

I substituted the above 3 lines with the 3 corresponding 3 lines from my August copy of the file - which I know was working at the time:

"launchParameters": "ED /vr /autoquit",
"launchFile2D": "ORID.exe",
"launchParameters2D": "ED /novr",

Once I had done this and restarted my PC, clicking on the Elite Dangerous app icon in the Oculus Home screen library launched the VR Elite version, bypassing the Frontier load screen.
Similarly, clicking on 'Start in desktop mode' bought up the Frontier load screen and clicking on this loaded Elite in Desktop mode.

I know nothing about coding and SimonNQ did all the brain work - I just followed the clues and struck lucky.

Goes without saying, but I'll say it anyway, back up any files your going to tinker with and remember, it worked for me but it may not for you.

Wasp0 · Dec 18, 2018

ganderbag said:
I followed your advice SimonNQ and had a look at an August 2018 copy of the 'frontier-developments-plc-elite-dangerous.json.mini' file that I had saved. My current Oculus app version is 1.33.0.750915. The CURRENT version of the file has the following 3 lines towards the bottom of the file:

"launchParameters": "ED",
"launchFile2D": "ORID.exe",
"launchParameters2D": "ED",

I substituted the above 3 lines with the 3 corresponding 3 lines from my August copy of the file - which I know was working at the time:

"launchParameters": "ED /vr /autoquit",
"launchFile2D": "ORID.exe",
"launchParameters2D": "ED /novr",

Once I had done this and restarted my PC, clicking on the Elite Dangerous app icon in the Oculus Home screen library launched the VR Elite version, bypassing the Frontier load screen.
Similarly, clicking on 'Start in desktop mode' bought up the Frontier load screen and clicking on this loaded Elite in Desktop mode.

I know nothing about coding and SimonNQ did all the brain work - I just followed the clues and struck lucky.

Goes without saying, but I'll say it anyway, back up any files your going to tinker with and remember, it worked for me but it may not for you.

Great write up Ganderbag, but unfortunately for me this also failed to work. Still the hunt goes on.

May i ask everyone on here, when in VR and you use the little remote control or the hand grips to go into dash and select Monitor to see what is on your desktop screen, does this work also for you? as for me, this has also stopped working. When i get into ED in VR by the normal desktop launcher way, i used to go to my desktop to read the 3rd party apps. This was a feature since Dash, but after this update, this has stopped working as well?

Thanks

He$$eeTant · Dec 18, 2018

ganderbag said:
I followed your advice SimonNQ and had a look at an August 2018 copy of the 'frontier-developments-plc-elite-dangerous.json.mini' file that I had saved. My current Oculus app version is 1.33.0.750915. The CURRENT version of the file has the following 3 lines towards the bottom of the file:

"launchParameters": "ED",
"launchFile2D": "ORID.exe",
"launchParameters2D": "ED",

I substituted the above 3 lines with the 3 corresponding 3 lines from my August copy of the file - which I know was working at the time:

"launchParameters": "ED /vr /autoquit",
"launchFile2D": "ORID.exe",
"launchParameters2D": "ED /novr",

Once I had done this and restarted my PC, clicking on the Elite Dangerous app icon in the Oculus Home screen library launched the VR Elite version, bypassing the Frontier load screen.
Similarly, clicking on 'Start in desktop mode' bought up the Frontier load screen and clicking on this loaded Elite in Desktop mode.

I know nothing about coding and SimonNQ did all the brain work - I just followed the clues and struck lucky.

Goes without saying, but I'll say it anyway, back up any files your going to tinker with and remember, it worked for me but it may not for you.

Yup this worked for me too. Had to re-start the machine but after that all good. Thanks

[VR] Muskoka · Dec 18, 2018

ganderbag said:
I followed your advice SimonNQ and had a look at an August 2018 copy of the 'frontier-developments-plc-elite-dangerous.json.mini' file that I had saved. My current Oculus app version is 1.33.0.750915. The CURRENT version of the file has the following 3 lines towards the bottom of the file:

"launchParameters": "ED",
"launchFile2D": "ORID.exe",
"launchParameters2D": "ED",

I substituted the above 3 lines with the 3 corresponding 3 lines from my August copy of the file - which I know was working at the time:

"launchParameters": "ED /vr /autoquit",
"launchFile2D": "ORID.exe",
"launchParameters2D": "ED /novr",

Once I had done this and restarted my PC, clicking on the Elite Dangerous app icon in the Oculus Home screen library launched the VR Elite version, bypassing the Frontier load screen.
Similarly, clicking on 'Start in desktop mode' bought up the Frontier load screen and clicking on this loaded Elite in Desktop mode.

I know nothing about coding and SimonNQ did all the brain work - I just followed the clues and struck lucky.

Goes without saying, but I'll say it anyway, back up any files your going to tinker with and remember, it worked for me but it may not for you.

Same at my end, didn't work until after a reboot. Thanks for the fix guys.