Oculus Rift 0.7.0 SDK

Rick_Black

R
Ok so I was at Elite Meet and one of the things they said was that "they are working on it, but stick with O.R. driver 5.0.1 and they did not have a time frame for when it would be done."
My opinion is that I would not expect an update soon and I think that is completely understandable.
Over the next months O.R. will update their drivers multiple times before cv1 launch, it would be impossible for them to keep up with the changes. The game is huge and with the horizons update right around the corner not to mention CQC update they are also working on and to try and update the driver support right now with all that in active development, no I don't think that would be possible not without possibly messing something up. It would make more sense that we wont see a real update until horizons is out of beta and the cqc is released on pc.
 

SlackR

Banned
SlackR
Rick_Black said:
Ok so I was at Elite Meet and one of the things they said was that "they are working on it, but stick with O.R. driver 5.0.1 and they did not have a time frame for when it would be done."
My opinion is that I would not expect an update soon and I think that is completely understandable.
Over the next months O.R. will update their drivers multiple times before cv1 launch, it would be impossible for them to keep up with the changes. The game is huge and with the horizons update right around the corner not to mention CQC update they are also working on and to try and update the driver support right now with all that in active development, no I don't think that would be possible not without possibly messing something up. It would make more sense that we wont see a real update until horizons is out of beta and the cqc is released on pc.
Click to expand...

The biggest issue thus far has been implementing direct mode. For whatever reason Frontier couldnt get it working properly and insist that the issue lies on oculus' side and not theirs. My hope is that .7 will bypass this issue and hopefully make impemetation easier and faster, not harder and further. They have been working closely with oculus for some time on this issue and my guess is that .7 is oculus answer to the problem.
 
Last edited:

Caspar

Caspar
SlackR said:
The biggest issue thus far has been implementing direct mode. For whatever reason Frontier couldnt get it working properly and insist that the issue lies on oculus' side and not theirs. My hope is that .7 will bypass this issue and hopefully make impemetation easier and faster, not harder and further. They have been working closely with oculus for some time on this issue and my guess is that .7 is oculus answer to the problem.
Click to expand...

Please let this be true :)
 

AndreyATGB

AndreyATGB
Seeing as they have the Oculus logo on the store and community site, I'd say Elite will definitely support OR. Hopefully it'll also support DK2 until then, but it's clear there will be no extended mode anymore as it's just too clunky and buggy.
 

Bevz

B
Caspar said:
Please let this be true :)
Click to expand...

+1
Good news is that Extended Mode is gone... That really needed to happen to get a seamless and idiot-proof VR experience. I'm surprised it lasted as long as it did, but i guess it served a purpose. Very excited about 0.7... A lot of stuff did update to 0.6 so those will just run "out the box". The real question is whether ED will... Hence the +1 as i really hope they support DK2 until CV1 is released, at the very least they should see it as an extended beta test and a way of getting it absolutely bang on ready for CV1. Let's hope!
 
Last edited:

atlas974

atlas974
News from reddit :
Hey all,

As you know we are working with Oculus to fix this but from what I have been told there were some major changes between the 0.5.x and 0.6.x driver that have caused these issues. I don't believe we had any heads up warning us of these changes either.

Hopefully when Oculus do release their 0.7.x driver this will help and we can then work on getting Elite: Dangerous working with it asap.

(Sidenote: I borrowed a colleague's DK2 just a few days ago to try and get it working with ED only to find out that there is no Windows 10 driver either. Really hoping the driver situation with Oculus improves soon.)

Fly safe,

CMDR Falcon
Click to expand...

http://www.reddit.com/r/EliteDangerous/comments/3gb4th/frontier_and_oculus_owners/
 

Thoemse

T
Hmm that is not really all that encouraging. One would think oculus would work closely with the devs considering this is pretty much the best VR title out there right now!

Right now i hope FD got a vive dev kit more than everything else. If oculus doesn't even work with FD to solve this issue i have no high hopes about them anymore.
 

=AH= Sid

=AH= Sid
From the email Oculus sent out to developers, I'd say they sound fairly keen to help.
.
If you’re a developer with questions about updating to 0.7, please reach out to us through the Oculus Developer Forums. We’re here to help!
Click to expand...
 

SlackR

Banned
SlackR
Oculus and Frontier have been working on a fix for .6 for ages. I think the reason there was no "heads up" from Oculus was becasue they didnt forsee the issues it would create with the cobra engine implementation. I hope that .7 is the answer to this problem.
 
Last edited:

Mazhurg

Mazhurg
My understanding of .7 is that it does away with the extended mode altogether, finally hides the display from the OS and uses a new framework provided by both NVIDIA and AMD (intel needs not apply) to render.

A mouthful... What has not been said is it is very possible that the date was chosen (20 Aug) to coincide with new driver releases from AMD and NVIDIA.

Hopefully, these changes are enough to enable FD to fix whatever issue(s) they encountered in .6
 

JediMstr

JediMstr
Mazhurg said:
My understanding of .7 is that it does away with the extended mode altogether, finally hides the display from the OS and uses a new framework provided by both NVIDIA and AMD (intel needs not apply) to render.

A mouthful... What has not been said is it is very possible that the date was chosen (20 Aug) to coincide with new driver releases from AMD and NVIDIA.

Hopefully, these changes are enough to enable FD to fix whatever issue(s) they encountered in .6
Click to expand...

Hoping the new Oculus framework that abstracts HD access and utilizes different paths for AMD and nVidia's VR Frameworks will actually enable the full on SLI capable VR without any additional game/engine specific development. Less work for FD in the future and more capability through Oculus managed APIs. *crossing fingers*
 

dementia

dementia
JediMstr said:
Hoping the new Oculus framework that abstracts HD access and utilizes different paths for AMD and nVidia's VR Frameworks will actually enable the full on SLI capable VR without any additional game/engine specific development. Less work for FD in the future and more capability through Oculus managed APIs. *crossing fingers*
Click to expand...

Indeed. ED needs VR SLI capable graphics hardware as using even a single 980Ti or Titan X with the Rift still doesn't allow anything much above low/off GFX settings when using SS 1.5 or 2.0 (SS being a must of OR users as the visibility is dramatically improved).
 

[VR] Mad Mike

[VR] Mad Mike
lol i wouldnt yet. extended mode is gone and Elite is rubbish in direct. so even IF it worked - which i doubt it will, anything not built to 0.6 sdk just comes up with incompatible error i believe - but even if it did, it woudl be in direct mode, which for now is a bit pants in elite.
 

Thoemse

T
Someone on reddit reported that ED doesn't work.

Lets hope the devs update as soon as possible.
This is the biggest step and they have to do it anyways. Extended mode is dead.
This SDK is the biggest step to CV1 compatibility considering it runs with AMD Liquid VR and Nvidia Gameworks VR drivers.
 
You must log in or register to reply here.
Back
Top Bottom