Oculus Core 2.0 Beta issues

conceit

conceit
As many of you might have noticed, the whole Oculus Home application + API currently gets a major overhaul which is now in public beta (can be activated within the settings menu of the Oculus Home desktop application).

I would like to know if anyone else is having issues starting ED with Oculus Core 2.0. Here, I cannot launch ED. I get an error message saying "No 3D-accelerated display mode available". It works as usual if I switch back from beta.

Someone already posted a bug report, but I'd like to estimate how many Oculus Rift users are having similar issues when switching to Oculus beta. Is this a configuration problem with only few affected users, or is it a more general bug in either Oculus or ED?

If this is a general problem, potentially many Oculus users might be affected when the Oculus Beta goes live. Please try the Oculus beta if you can find the time and share your experiences. Thank you.

Config here: CV1, ED 64bit/Horizons (steam installation), launched either from Oculus home or ED-Profiler, not Steam-VR, GTX1070, latest drivers, Win 10
 

The Lawful

The Lawful
Zero problems with Oculus 2.0 & ED 2.4, launching from "inside" Oculus 99% of times because of laziness. The 3.0 beta I start from the standalone launcher, so not integrated into Dash. Here, it seems to be important to start Oculus before the launcher, otherwise it starts in 2D and only shows the game inside a window on the VR desktop. If I start Oculus first, the game gets detected and boots up as usual, just the game logo appears as 'broken image' in that cyberspace environment that comes up before the game is actually launched. Think it's an Oculus issue. Wouldn't consider going back to pre-2.0, Dash is so much better.

O7,
[noob]
 

Athracht

Athracht
Have you tried downloading and running the non-Steam ED from the Frontier site? I don't know if it would make a difference, but you might give it a shot. If your Steam ED installation is somehow corrupted, at least this would give you the benefit of a fresh install, in addition to not having to bother with Steam VR PLUS Oculus. I'm running Oculus 2.0 Beta with no such issues, but I've seen that error with Steam games outside of Oculus. In my case, it seemed to be related to corrupted MS C++ runtime installations.

For myself, I'm running the standalone version, not Steam, and starting it from the Frontier launcher. When I try to start it from within Oculus, I get a connection error. This also happened when I was running the Steam version. But no errors beyond that, in either version of Oculus.

I'd try running the non-Steam version and see if it helps.

Good luck!
 

conceit

conceit
Thank you guys for sharing your wisdom. First, it's good to know that it is not a general problem with Oculus Core 2 and Elite Dangerous. I will try your suggestions next weekend.
 

conceit

conceit
So, I uninstalled ED-Steam and re-installed from the Oculus store, with the exact same result. Will try further work-arounds and report in.
 

Athracht

Athracht
Rather than the Oculus or Steam version, try downloading and installing directly from Frontier, and launching directly from the Frontier launcher with Oculus running. This is what I have to do, and it works perfectly. Of course, your mileage may vary, but it's worth a try!

o7
 

conceit

conceit
Finally, I was able to fix this issue. And, as it came out, there is another solution to it than any other I've found as of yet in the forums and on reddit. Actually, in the nVidia settings panel, there is a tab (translated from a German install, so might be worded differently): "Display / Set up multiple displays". In my case, whith Oculus Core 2 active, it showed two displays: "NVIDIA VR-DESKTOP" and my actual monitor.

Now the important part: In the area titled like "Order the symbols according to your actual setup", both screens were in a enlarged desktop side-by-side setup, showing as "1|2" instead of seperate symbols. I deactivated the VR-Desktop in the top area of the dialog, and after hitting apply, I immediately was able to launch ED. I could open the dash within ED, but not the desktop. It just showed an exclamation mark.

This was resolved by simply switching off the Oculus beta program and back on (this didn't help before). Now, everything works as supposed. In the nVidia multiple-displays settings, now both screens show up, but as seperate symbols "1" and "2", and with different size, according to their respective screen resolutions.
 

vic

V
wait a minute, if nvidia now sees both your monitor AND the rift, then can you adjust the color/contrast/brightness in the nvidia settings for the rift(this had no effect previously on the rift)?
 

[VR] Muskoka

[VR] Muskoka
vic said:
wait a minute, if nvidia now sees both your monitor AND the rift, then can you adjust the color/contrast/brightness in the nvidia settings for the rift(this had no effect previously on the rift)?
Click to expand...

I can see both on my system, monitor and the rift, but making changes does nothing. I can change brightness, contrast, gamma, vibrance....etc, and nothing visually changes in the rift within Ed. It's listed as Nvidia Vr-Desktop, alongside my Tv/monitor.
 
Last edited:

conceit

conceit
Muskoka said:
I can see both on my system, monitor and the rift, but making changes does nothing. I can change brightness, contrast, gamma, vibrance....etc, and nothing visually changes in the rift within Ed. It's listed as Nvidia Vr-Desktop, alongside my Tv/monitor.
Click to expand...

I think they only render the virtual desktop using this device. However, maybe this still opens a door to use post processing effects like EDFX now.
 

Absenta

A
Same issue here. I had this problem before the last update of ED yesterday and it still remains. ED only works if I switch off the new version of DASH but the old version won´t be available forever. Elite is the only game I had this problem with
 
You must log in or register to reply here.
Back
Top Bottom