Important Notice Regarding Oculus 0.6 SDK

Frontier QA

Frontier QA Team
Frontier
Hi everyone,

Just wanted to give you all a heads up to let you know that there are some issues that occur when running Elite: Dangerous with the latest Oculus 0.6 SDK, which we are currently investigating.

In the meantime, it may be best to not update to the latest SDK for optimal performance when running Elite: Dangerous on your Oculus Rift.

We will keep you posted with further updates as they become available.
 
thanks for your time, waiting more infos on the 0.6 sdk integration in ED futur updates (layers for HUD and time warping for better performances)
 
I'll stay on the previous version until you give the green light. Really appreciate you communicate on this, thanks! :)
 
Thank you very much for the info.
Your commitment to the Oculus Rift implementation in this incredible game is has always been unrivalled.
Can't wait to see all you can make with the new SDK's possibilities.
 
Can't wait to see all you can make with the new SDK's possibilities.

^This, it looks like 0.6 is a major milestone towards CV1 support because it moves distortion and time warp to the Oculus Service. It may take a while to upgrade a custom engine to the new SDK, but it will pay off.
 
It would be amazing if they'd render the UI and other 2D elements at 2x or more, that way we get the biggest advantages of SS without the massive FPS hit.
 
I just hope for real SDK 0.6 support. From what i read on reddit this one could be huge and prossibly remove any sort of judder.
 
No offense Fd but, we knew this day one.

Nice that it's a sticky thing and all but, it's a little late.....

No offense but wasn't the SDK released Friday afternoon UK time? I doubt they have a VR emergency team ready to push info like this out on a moments notice during weekends. Especially on hardware that is still in development...
 
No offense but wasn't the SDK released Friday afternoon UK time? I doubt they have a VR emergency team ready to push info like this out on a moments notice during weekends. Especially on hardware that is still in development...

Ahh Tinman, you're a gem.
 
Thanks for the update FD - much appreciated. It would be interesting to know if any of the new features are of any use to ED.
 
Any update on this.
I have been having problems with my DK2 and did a re-install only to see this!
I can't see version 0.5 to download
There is a 0.5.0.1 Beta and the 0.6 Beta
Any suggestions welcome :)
 
Any update on this.
I have been having problems with my DK2 and did a re-install only to see this!
I can't see version 0.5 to download
There is a 0.5.0.1 Beta and the 0.6 Beta
Any suggestions welcome :)
use the .0.5.0.1 beta. that's pretty much what everyone is using these days.
 
Yes can we all just take stock at the moment, those of us who bought a dev kit for playing games, the SDK release hits us the same time it hits devs. Getting a direct update from the dev like this within a couple of working days after the release puts most other devs to shame.

Much like if you are a developer working off nightly builds of another library, you typically don't know something's broken before it breaks; it's a caveat of being at the very edge of the, ahem, rift.

Personally I'd never install the latest version of something like this without a) checking first if the dev has posted about it's compability or, if not, b) checking if other people have had issues and, if not, c) fully expecting to have to revert the software in the likely case that it doesn't work.

So frustration, yes, but it's not the end of the world.

On another note, I'm really hoping for a 'proper' update to target this new SDK from FDev - much like everyone else - since it contains tech that could drastically improve the current experience.

That said, I've clocked a good few days' worth of game time now, only 5 minutes of which was without the DK2 :)
 
Yes can we all just take stock at the moment, those of us who bought a dev kit for playing games, the SDK release hits us the same time it hits devs. Getting a direct update from the dev like this within a couple of working days after the release puts most other devs to shame.

Much like if you are a developer working off nightly builds of another library, you typically don't know something's broken before it breaks; it's a caveat of being at the very edge of the, ahem, rift.

Personally I'd never install the latest version of something like this without a) checking first if the dev has posted about it's compability or, if not, b) checking if other people have had issues and, if not, c) fully expecting to have to revert the software in the likely case that it doesn't work.

So frustration, yes, but it's not the end of the world.

On another note, I'm really hoping for a 'proper' update to target this new SDK from FDev - much like everyone else - since it contains tech that could drastically improve the current experience.

That said, I've clocked a good few days' worth of game time now, only 5 minutes of which was without the DK2 :)

So even by your own admission here somebody has to be the canary right otherwise nobody ever knows it is broken and thus will not fix it. True but then again if everyone developed your reasoning there would be no need to ever upgrade anything as there would be nobody to test it so why create it. :rolleyes:
 
Last edited:
So even by your own admission here somebody has to be the canary right otherwise nobody ever knows it is broken and thus will not fix it. True but then again if everyone developed your reasoning there would be no need to ever upgrade anything as there would be nobody to test it so why create it. :rolleyes:

Yeah I know, it's a paradox! :)
 
Back
Top Bottom