Dev's can I assume no further OCULUS support will be done until SDK 1.0 is released?

After reading past notices from the DEV's is it safe to assume FDEV will not be doing any further development for VR until oculus SDk 1.0 is released? Your lack of openness as to what is happening has a lot of us worried as for many of us not having oculus support long term completely breaks the game for us. This is something that non oculus users may not understand as using the rift profoundly changes the game for us that I cant go back to using a monitor anymore.
 
To be honest I don't know how big the changes between SDK versions are, but I, too, would not be spending dev time on that until the SDK is finalized.
Technically all current Rift owners could be thought of as developers and not consumers (even though everyone knows that's not true, and it's never
a good idea to alienate enthusiasts).

Personally, I'm ordering the Rift (CV) as soon as ongoing ED support is confirmed.
 
probably. The lack openness may be down to Frontier signing NDA with Oculus, Frontier being the first or among the first to have a commercial game with VR make them prime target to sign up as a launch title for Oculus.
 
.
Technically all current Rift owners could be thought of as developers and not consumers ).


Glad someone gets it.

However, I think it's only a case of recompiling with the new oculus SDK, and that can only be done once the SDK is released.
TBH I wouldn't worry, FD are committed to VR and are likely to add support as soon as the SDK is available.

Edit. Assuming that the SDK is out in time for the 1.4 release. I would doubt they would do a special VR release if they were unable to meet the deadline
 
Last edited:

SlackR

Banned
probably. The lack openness may be down to Frontier signing NDA with Oculus, Frontier being the first or among the first to have a commercial game with VR make them prime target to sign up as a launch title for Oculus.

I would love this to be true but i dont believe it will happen for a second.
 
Glad someone gets it.

However, I think it's only a case of recompiling with the new oculus SDK, and that can only be done once the SDK is released.
TBH I wouldn't worry, FD are committed to VR and are likely to add support as soon as the SDK is available.

Edit. Assuming that the SDK is out in time for the 1.4 release. I would doubt they would do a special VR release if they were unable to meet the deadline

Huh?

ED can be updated to the latest available SDK 0.6.0.1 which is compatible with 0.7 but the devs have chosen to not support anything after 0.4 until, it seems, 1.0 which unfortunately is 6-7 months away.

The DK2 is a dev kit but FD marketed ED as a VR supported title which people have paid real money for regardless of whether they are developers or not. I don't really see your point as even if you are a dev, you're not developing ED itself, you're playing it like everyone else. I think it's reasonable to expect continued VR support in ED and if also reasonable to be disappointed if that is not the case.
 
Huh?

ED can be updated to the latest available SDK 0.6.0.1 which is compatible with 0.7 but the devs have chosen to not support anything after 0.4 until, it seems, 1.0 which unfortunately is 6-7 months away.

The DK2 is a dev kit but FD marketed ED as a VR supported title which people have paid real money for regardless of whether they are developers or not. I don't really see your point as even if you are a dev, you're not developing ED itself, you're playing it like everyone else. I think it's reasonable to expect continued VR support in ED and if also reasonable to be disappointed if that is not the case.

But they are continuing support, they have never claimed otherwise. They have said numerous times they are committed to VR.

0.7 as I understood it is not backwards compatible and if installed cannot be downgraded, which is why they said do not upgrade if you want to keep playing with the rift.
 
I play Elite in the DK2 (extended mode) on a clean installed Windows 10 (not upgraded) with SDK 0.6.0.1 (980 Ti) latest Nvidia drivers and it works very well. Only thing is you have to start the Oculus service manually through a shortcut. This is the workaround I used: http://epicindustries.co.uk/2015/08/10/oculus-rift-windows-10/

This fact (that it works, even in Win 10, even with 0.6.0.1) kind of reveals that the problem shouldn't be extremely hard to solve for Frontier. But without more information from Frontier, Rift+Elite fans like myself, who essentially bought an Oculus because of Elite (and the other way around), feels a little worried that something else is going on behind the curtains. Many of us are tech-junkies and it wouldn't hurt to have some technical explanation of the issue.
 
I play Elite in the DK2 (extended mode) on a clean installed Windows 10 (not upgraded) with SDK 0.6.0.1 (980 Ti) latest Nvidia drivers and it works very well. Only thing is you have to start the Oculus service manually through a shortcut. This is the workaround I used: http://epicindustries.co.uk/2015/08/10/oculus-rift-windows-10/

This fact (that it works, even in Win 10, even with 0.6.0.1) kind of reveals that the problem shouldn't be extremely hard to solve for Frontier. But without more information from Frontier, Rift+Elite fans like myself, who essentially bought an Oculus because of Elite (and the other way around), feels a little worried that something else is going on behind the curtains. Many of us are tech-junkies and it wouldn't hurt to have some technical explanation of the issue.


You have the same setup as me. Bar a lot more lag in the galaxy map, it works fine.

The problem as I understand it: Oculus are releasing a 0.7 version of the SDK and it will have compatibility changes.

"0.7 of the Oculus PC SDK will launch on August 20th, and introduces architecture changes that bring increased stability, performance, and a new ‘Direct Driver Mode’ developed in collaboration with NVIDIA and AMD. However, as a result of these updates, the 0.7 runtime won’t support applications built with 0.5 or earlier, including all content built with Unity 4.x. This means the majority of existing Rift games and applications will need to be updated to 0.7 (or at least 0.6.0.1) to work with the new 0.7 runtime." : https://developer.oculus.com/blog/upcoming-oculus-pc-sdk-0-7-compatibility-changes/


FD have said do not upgrade until they have built the game using the new SDK. If you do, you will hit the problem above.
I believe that FD use 0.5 which is compatible with 0.6. However 0.7 is not compatible with content built using 0.5 - if that makes sense. So, stick with what you have and all will continue to work. Upgrade and you'll be dusting the cobwebs off your monitor.

You will only break the game if you ignore FDs advice and upgrade the runtime.
 
Last edited:
To be honest I'd be happier if they left VR as it is until the consumer release now. If Frontier update to 0.7 I'll have an extremely hard choice to make:

Upgrade to 0.7 and loose loads of games which rely on extended mode but still have E: D or forget E: D until the consumer release and continue to enjoy great VR experiences such as Alien Isolation....

E: D in its current state (not VR wise) is starting to loose my attention, I'm a little fed up with the limited game play, ie. "What shall I do tonight? Farm RES sites or spam trade routes" both are getting a little tiresome. For such an epic game it can be a little thin at times.
 
Last edited:
I assume SDK 0.7 comes with a firmware (hardware) update for the DK2 itself, once you've updated the firmware you won't be able to roll back to an earlier version of the firmware, hence you won't be able to use an earlier SDK (unless you have two DK2s).
.
I bought my DK2 to use with ED, so I'll take FD's advise and stick with SDK 0.5 (and Win7) for the foreseeable future.
.
.
Your lack of openness as to what is happening has a lot of us worried as for many of us not having oculus support long term completely breaks the game for us.
iced01, I don't see how you can accuse FD of 'lack of openness'. They posted two weeks ago a very frank and open statement on what the situation is.
.
Oculus Rift SDK update
.
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.
 
Last edited:
I assume SDK 0.7 comes with a firmware (hardware) update for the DK2 itself, once you've updated the firmware you won't be able to roll back to an earlier version of the firmware, hence you won't be able to use an earlier SDK (unless you have two DK2s).

Thankfully this is not the case and the Oculus community guy has confirmed there is no firmware update needed for 0.7 and we WILL be able to flip flop between drivers.
 
Its easy to accuse, its very simple. Despite what a few of you choose to believe no where has FDEV stated they intend to peruse future development regarding the SDK. they have simply said do not roll up to the latest build. A CLEAR statement from FDEV would have said something like " At present we cannot guarantee ED's compatibility with future SDK released but every effort will be made to ensure compatibility if possible. " There are those of you who like to think their statement "we are and have been early supporters of VR" to mean the same thing as we "intend to fully support oculus sdk in future if possible" are the same. There not! And this is my view as a software architect and developer for a large game studio. They could end any confusion over this with such a simple statement. The question is why have they not?
 
Thankfully this is not the case and the Oculus community guy has confirmed there is no firmware update needed for 0.7 and we WILL be able to flip flop between drivers.

Ok, thanks I'd missed that on the Oculus forum, now found cybereality post.
 
Its easy to accuse, its very simple. Despite what a few of you choose to believe no where has FDEV stated they intend to peruse future development regarding the SDK. they have simply said do not roll up to the latest build. A CLEAR statement from FDEV would have said something like " At present we cannot guarantee ED's compatibility with future SDK released but every effort will be made to ensure compatibility if possible. " There are those of you who like to think their statement "we are and have been early supporters of VR" to mean the same thing as we "intend to fully support oculus sdk in future if possible" are the same. There not! And this is my view as a software architect and developer for a large game studio. They could end any confusion over this with such a simple statement. The question is why have they not?

Personally I thought this was very clear.

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.

 
Glad someone gets it.

However, I think it's only a case of recompiling with the new oculus SDK, and that can only be done once the SDK is released.
TBH I wouldn't worry, FD are committed to VR and are likely to add support as soon as the SDK is available.

Edit. Assuming that the SDK is out in time for the 1.4 release. I would doubt they would do a special VR release if they were unable to meet the deadline


I've never written for the Oculus but I do write code professionally. There's no such thing as 'just a recompile'. It's highly unlikely that Oculus hasn't bent over backwards trying to accommodate FD, Elite Dangerous is one of the few games for the Rift which isn't just a novelty. So the excuse of 'We don't have the sdk' is pretty hard to swallow. My take on this:

The same skill set that you would need for working with the dk2 is the same skill set that you could use for porting this game to a console. More people own consoles than VR headsets by several order of magnitudes so that's what gets prioritized. And you could hardly blame them. FD is a business. We can only hope that once the console release gets off the ground that VR will become a priority again.
 
I've never written for the Oculus but I do write code professionally. There's no such thing as 'just a recompile'. It's highly unlikely that Oculus hasn't bent over backwards trying to accommodate FD, Elite Dangerous is one of the few games for the Rift which isn't just a novelty. So the excuse of 'We don't have the sdk' is pretty hard to swallow. My take on this:

The same skill set that you would need for working with the dk2 is the same skill set that you could use for porting this game to a console. More people own consoles than VR headsets by several order of magnitudes so that's what gets prioritized. And you could hardly blame them. FD is a business. We can only hope that once the console release gets off the ground that VR will become a priority again.

I gave up writing code. Much easier to just manage devs :)

I agree with you 100% that oculus and valve will be bending over backwards to ensure the devs have everything they need. ED will be responsible for the sale thousands of VR units worldwide, I'm sure they won't be left behind.

When I said just a recompile, of course that's an over simplification. But it was also on the assumption that they have done most of the work already and just need the released SDK for the last 10%. I'd hope that come release the dev isn't looking through the SDK release notes for the very first time.

In RL we have an SDK and every time Apple bring out an updated OS, we get the exact same issue and get hammed by customers. You need the final release to be sure.
 
don't forget you're getting the SDK at the same time as the developers are getting it. The DK2 is a developer kit, it is not a consumer product. There is no SDK before you get the SDK. There is no way to get it to Elite sooner than you get it because it simply is not ready.
 
0.7 is now in final testing after the last blocker bug was squashed. Cybereality was careful not to give exact times, but he said it would be very soon and not to worry.

It looks like the issue was with the nvidia drivers which nvidia have now confirmed is also fixed (so if that wasnt the blcoker then that is another bug dodged). Many are hoping they 0.7 will be released today (assuming it did not happen last night as they are 8 hrs behind us i think).** update no it didnt.

This has not been confirmed... but it has not been refuted either last ime i looked

due to time zone differences i will look back again after 5pm blighty time
 
Last edited:
Back
Top Bottom