FD is working on Vive visual quality fixes.

Frontier has the Vive logo on their web page which tells you they are dedicated to sorting out the issues.

It may take them a while, but I'm confident they'll work this through. They have a lot of smart people working for them.
 
Last edited:
I hope they fix the performance issues as well, I get some woeful shudder at times. One time it was so bad my head tracking was rubber-banding.
 
Try running the game without SteamVR, and ensuring you have HMD Headset in the graphics options. These two things helped me.
 
Try running the game without SteamVR, and ensuring you have HMD Headset in the graphics options. These two things helped me.

I'm trying to see whether when launching the game from SteamVR, it is passed different command line parameters to when it is launched from Steam or the Frontier launcher. Could someone with a Vive and a Steam-bound copy of ED please use Windows Task Manager to check the command line for both SteamVR and Frontier launcher starts, and post both here? You should obfuscate the token command line argument before doing so, as this is derived from your ED login details.
 
Try running the game without SteamVR, and ensuring you have HMD Headset in the graphics options. These two things helped me.

If I run my standalone ED with HMD selected in the graphics section, it just displays on the monitor without accessing the Vive. I need to preload steamVR for it to work, so how do I run ED in the Vive without loading steam?

Perhaps ED is loading the Oculus runtime, and with no Rift (yet), it defaults to the monitor.
 
Last edited:
Make sure you have steam VR running. Launch Elite Dangerous from the FD Launcher. In the graphics options within ED choose HMD Headset option and that should do it.
 
If I run my standalone ED with HMD selected in the graphics section, it just displays on the monitor without accessing the Vive. I need to preload steamVR for it to work, so how do I run ED in the Vive without loading steam?

Perhaps ED is loading the Oculus runtime, and with no Rift (yet), it defaults to the monitor.

I think by "running the game without SteamVR", JonnyBigBoss meant "launch it from the Frontier Launcher, not from Steam[VR]".

My suspicion is that the metadata for running Elite natively in Steam tells the Steam launchers to pass a /vr switch, whereas running it from the Frontier launcher does not. Would one of you help me test this hypothesis?

- - - - - Additional Content Posted / Auto Merge - - - - -

Nevermind, suspicion proven: https://steamdb.info/app/359320/config/

Code:
[TABLE="class: table table-bordered table-fixed, width: 100%"]
[TR]
[/TR]
[TR]
[TH]DESCRIPTION[/TH]
[TH]EXECUTABLE[/TH]
[TH]ARGUMENTS[/TH]
[TH="class: span1"]TYPE[/TH]
[TH="class: span1"]OS[/TH]
[TH="class: span3"]EXTRA INFO[/TH]
[/TR]
[TR]
[TD]Elite Dangerous[/TD]
[TD]EDLaunch.exe[/TD]
[TD]/Steam[/TD]
[TD]Option1[/TD]
[TD="class: nowrap"][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]Launch[/TD]
[TD]Elite Dangerous Launcher.app[/TD]
[TD]-Steam[/TD]
[TD][I]Default[/I][/TD]
[TD="class: nowrap"][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]Elite Dangerous - Dev[/TD]
[TD]EDLaunch.exe[/TD]
[TD]/Steam[/TD]
[TD]Option1[/TD]
[TD="class: nowrap"][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]Elite Dangerous: Horizons[/TD]
[TD]EDlaunch.exe[/TD]
[TD]/EDH /steamid 441340[/TD]
[TD]Option1[/TD]
[TD="class: nowrap"][/TD]
[TD]64-bit DLC [URL="https://steamdb.info/app/441340/"]441340[/URL][/TD]
[/TR]
[TR]
[TD][I]None[/I][/TD]
[TD]EDLaunch.exe[/TD]
[TD]/Steam /VR[/TD]
[TD]Vr[/TD]
[TD="class: nowrap"][/TD]
[/TR]
[/TABLE]

See that last line there? Anyone want to compare the Vive visuals when running EDLaunch.exe with and without that /VR flag?
 
I think by "running the game without SteamVR", JonnyBigBoss meant "launch it from the Frontier Launcher, not from Steam[VR]".

My suspicion is that the metadata for running Elite natively in Steam tells the Steam launchers to pass a /vr switch, whereas running it from the Frontier launcher does not. Would one of you help me test this hypothesis?

- - - - - Additional Content Posted / Auto Merge - - - - -

Nevermind, suspicion proven: https://steamdb.info/app/359320/config/

Code:
[TABLE="class: table table-bordered table-fixed, width: 100%"]
[TR]
[/TR]
[TR]
[TH]DESCRIPTION[/TH]
[TH]EXECUTABLE[/TH]
[TH]ARGUMENTS[/TH]
[TH="class: span1"]TYPE[/TH]
[TH="class: span1"]OS[/TH]
[TH="class: span3"]EXTRA INFO[/TH]
[/TR]
[TR]
[TD]Elite Dangerous[/TD]
[TD]EDLaunch.exe[/TD]
[TD]/Steam[/TD]
[TD]Option1[/TD]
[TD="class: nowrap"][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]Launch[/TD]
[TD]Elite Dangerous Launcher.app[/TD]
[TD]-Steam[/TD]
[TD][I]Default[/I][/TD]
[TD="class: nowrap"][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]Elite Dangerous - Dev[/TD]
[TD]EDLaunch.exe[/TD]
[TD]/Steam[/TD]
[TD]Option1[/TD]
[TD="class: nowrap"][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]Elite Dangerous: Horizons[/TD]
[TD]EDlaunch.exe[/TD]
[TD]/EDH /steamid 441340[/TD]
[TD]Option1[/TD]
[TD="class: nowrap"][/TD]
[TD]64-bit DLC [URL="https://steamdb.info/app/441340/"]441340[/URL][/TD]
[/TR]
[TR]
[TD][I]None[/I][/TD]
[TD]EDLaunch.exe[/TD]
[TD]/Steam /VR[/TD]
[TD]Vr[/TD]
[TD="class: nowrap"][/TD]
[/TR]
[/TABLE]

See that last line there? Anyone want to compare the Vive visuals when running EDLaunch.exe with and without that /VR flag?

Is that good news? Does it mean there's more likely to be a software fix to all of this, rather than it be hardware?
 
Last edited:
Frontier has the Vive logo on their web page which tells you they are dedicated to sorting out the issues.

It may take them a while, but I'm confident they'll work this through. They have a lot of smart people working for them.
excellent. My rig is strong enough to run it at 1.5x but it's hot and loud doing so. Hopefully their solution will be done in a month of two.

Yes, smarter than Valve's team.
let's not get carried away.
 
Is that good news? Does it mean there's more likely to be a software fix to all of this, rather than it be hardware?

I don't *think* so; I just had a play starting EDLaunch.exe with and without the /VR switch, and it does make no difference in-game as far as I can tell. I was hoping there would be some dumb bug that if /VR was passed to the launcher it forced some Rift graphics configuration that messed up IQ on the Vive. But all /VR does is tell the launcher to immediately launch the game. The EliteDangerous64.exe command line does not change.

The more interesting thing is that the /Steam switch tells the launcher to open a directory called 'Products' in its working directory for writing. This is probably so that either it can install ED there (as opposed to the AppData location used by launcher when run standalone) and so it can write the StereoscopicMode config to Options\Graphics\Settings.xml so that the game comes up in VR mode on first run.

Potentially this could be writing a bad/Vive-unfriendly value there, however, I'd be surprised if this was the case as other users would surely have already discovered this by fiddling with the options in game and discovering improvements. And I don't want to generate a Steam key to test this theory as it would give Valve a slice of my ED spend with FDEV going forwards and backwards.

If anyone wants to reinstall the game with Steam, start it with a clean Settings, and send me a zip of the Options folder tree, I'd be very grateful. PM me if interested.
 
Last edited:
Back
Top Bottom