Oculus Rift SDK update

Edward Lewis

Edward Lewis
Hi everyone,

Oculus are about to release SDK 0.7 for the Oculus Rift which removes the ability to roll back to 0.5, so we wanted to make you all aware of some important information.

Players using Oculus Dev Kits should continue to use the 0.5. Oculus Runtime for Elite: Dangerous. Upgrading to the upcoming 0.7 release will not be compatible with our game.

As long-time supporters of VR and early adopters of Oculus, we remain in close communication with them as they work towards a production version of their SDK, but want to be open that without that SDK in hand, we cannot guarantee future compatibility.

We will keep you posted.

Thanks.
 

Edward Lewis

Edward Lewis
Hi everyone,

Oculus are about to release SDK 0.7 for the Oculus Rift which removes the ability to roll back to 0.5, so we wanted to make you all aware of some important information.

Players using Oculus Dev Kits should continue to use the 0.5. Oculus Runtime for Elite: Dangerous. Upgrading to the upcoming 0.7 release will not be compatible with our game.

As long-time supporters of VR and early adopters of Oculus, we remain in close communication with them as they work towards a production version of their SDK, but want to be open that without that SDK in hand, we cannot guarantee future compatibility.

We will keep you posted.

Thanks.
 

wstephenson

wstephenson
Might it be worth posting this in the VR Discussion and Support forum as previous SDK PSAs have been? Or even in the launcher, so non-forum reading Oculus users see it?
 

wstephenson

wstephenson
Might it be worth posting this in the VR Discussion and Support forum as previous SDK PSAs have been? Or even in the launcher, so non-forum reading Oculus users see it?
 

atlas974

atlas974

SlackR

Banned
SlackR
C'thulhu said:
Understood, thanks. When the new SDK comes available will FDEV's work on it with Elite?
Click to expand...

You understood? Could you explain it to me then? :p they will work on .7 when it arrives or will wait until 1.0?

I feel a VIVE steam "exclusive" coming on! ... Lol
Watch this space boys and girls!
 

[VR] Mad Mike

[VR] Mad Mike
I had kind of hoped with FD being one of the only AAA titles to be 100% fully playable in VR without ever using a monitor, that you would have had a pre-release of the 0.7 SDK so as to be able to hit the ground running.

fingers crossed it gets fixed sooner rather than later
 

atlas974

atlas974
Mad Mike said:
I had kind of hoped with FD being one of the only AAA titles to be 100% fully playable in VR without ever using a monitor, that you would have had a pre-release of the 0.7 SDK so as to be able to hit the ground running.

fingers crossed it gets fixed sooner rather than later
Click to expand...

I had kind of hoped the same thing, but seems oculus is too much into exclusive game (Eve V) instead of actual released game sadly.....
 

Voyager_NL

Voyager_NL
Mad Mike said:
I had kind of hoped with FD being one of the only AAA titles to be 100% fully playable in VR without ever using a monitor, that you would have had a pre-release of the 0.7 SDK so as to be able to hit the ground running.

fingers crossed it gets fixed sooner rather than later
Click to expand...

Simply: As far as I know thre is no "pre-release" as this is still SDK/DEVKIT timeframe oriented so OCULUS doesn't factor in there are customers already using their devkits. So they release an SDK which is for the devs and then the devs can start coding against that SDK. BUt the release is also available to the VR enthousiasts at home who bought a DEVKIT and want to play directly all the games using the new SDK they just installed on their PC. You cannot expect developers lik FD to have that build ready in 0 time. Specifically now with 0.6.0.2 and 0.7 axing the use of the standard monitor output and focussing on Direct mode.

Basically that is the risk end users took when buying a DEVKIT with the sole purpose to use it for playing the games instead of creating them.

You can't expect from Oculus to make a distinction between DEVKIT purchasers in the line of: Owh you are a real Developer, I'll get you the SDK a month earlier and Owh you are an Enthousiast Consumer so you will have to wait for the SDK to come out when the Devs have had their time with it. The devkit simply never was meant for that.
 

Alex Brentnall

Alex Brentnall
Probably also worth a post on Reddit and on Galnet otherwise Elite will be swamped by those saying "I updated and its now impossible to play".

Maybe support at Elite can keep a physical copy of 0.5 in a zip file or some such if it's small enough to allow them to supply it to any users that accidentally upgrade?
 

Dweezil_Moon

Dweezil_Moon
As far as I know, the 1.0 drivers should be released sometime in November, and Oculus already stated that, at least until 1.0, drivers would only be backward compatible (if at all) with the previous dot releae (so 0.5 was compatible with 0.4, 06 was compatible, more or less, with 0.5, 07 will be compatible with 0.6, and so on). It doesn't make sense for Frontier to invest in making the game compatible with 0.7, knowing that 1.0 is just around the corner. They probably have enough on their plate with Horizons.
Personally I would be really disappointed if Elite : Dangerous wasn't playable with 1.0x, as those drivers are supposedly the release ones, but I definitely can understand the decision not to support every version of the beta drivers.
 

[VR] Mad Mike

[VR] Mad Mike
Voyager_NL said:
Simply: As far as I know thre is no "pre-release" as this is still SDK/DEVKIT timeframe oriented so OCULUS doesn't factor in there are customers already using their devkits. So they release an SDK which is for the devs and then the devs can start coding against that SDK. BUt the release is also available to the VR enthousiasts at home who bought a DEVKIT and want to play directly all the games using the new SDK they just installed on their PC. You cannot expect developers lik FD to have that build ready in 0 time. Specifically now with 0.6.0.2 and 0.7 axing the use of the standard monitor output and focussing on Direct mode.

Basically that is the risk end users took when buying a DEVKIT with the sole purpose to use it for playing the games instead of creating them.

You can't expect from Oculus to make a distinction between DEVKIT purchasers in the line of: Owh you are a real Developer, I'll get you the SDK a month earlier and Owh you are an Enthousiast Consumer so you will have to wait for the SDK to come out when the Devs have had their time with it. The devkit simply never was meant for that.
Click to expand...

I see your point and even agree to some extent... that being said, my understanding is FD in the past got the DK2 before others. AFAIK in the past there have been Developers and "Developers" and the amount of support has differed slightly depending on which group you fall in. (I got my DK2 within a few weeks of launch and offered to loan it to them - they are only 3 miles from my work - however I was politely told there was no need as they were already covered, so it would seem they were given priority - and rightly so - over the jo averages... either that or DB was hammering the refresh button like i was on the day that pre-orders went live.... but i doubt it ;)

- - - Updated - - -

Dweezil_Moon said:
As far as I know, the 1.0 drivers should be released sometime in November, and Oculus already stated that, at least until 1.0, drivers would only be backward compatible (if at all) with the previous dot releae (so 0.5 was compatible with 0.4, 06 was compatible, more or less, with 0.5, 07 will be compatible with 0.6, and so on). It doesn't make sense for Frontier to invest in making the game compatible with 0.7, knowing that 1.0 is just around the corner. They probably have enough on their plate with Horizons.
Personally I would be really disappointed if Elite : Dangerous wasn't playable with 1.0x, as those drivers are supposedly the release ones, but I definitely can understand the decision not to support every version of the beta drivers.
Click to expand...

yeah i think oculus have stated that if your app works with 1.0 it will always be compatible going forward..... so so long as ED works on 1.0 then ultimately i can live with a few hitches in the road until then, it still does not mean we should not nudge them a little ;)
 
Last edited:

cmdr awesome

cmdr awesome
The 0.6 update included loads of cool stuff for optimising the frame rate and I was *wishing really hard* that support for it would come "soon", but at this point I guess it makes sense to wait and see what 0.7 looks like and update for that.
 

[VR] Mad Mike

[VR] Mad Mike
despite the official line, 6.0 works with ED. Albeit the framerate is not quite as good as if using 0.5 so the advice to stick with 0.5 is sound so long as you have no interest in any 0.6 only apps.

ETS2 is light years better in 0.6 than 0.5 however so I had no choice.
 
Last edited:

777Driver

777Driver
Mad Mike said:
despite the official line, 6.0 works with ED. Albeit the framerate is not quite as good as if using 0.5 to the advice to stick with 0.5 is sound so long as you have no interest in any 0.6 only apps.

ETS2 is light years better in 0.6 than 0.5 however so I had no choice.
Click to expand...

Workaround for me is a dual boot. Ed stays with 0.5 all my other games stay on the second boot with 0.7
 
You must log in or register to reply here.
Back
Top Bottom