Oculus Rift SDK update

I think the key here is it does work therefore commitment for filled. It may not work the way you want it to but Waite for the public realease of any of the consumer headsets and frontier will make it work your DK2 should be able to assess whatever software the consumer product can and therefore operate the way you invigined. Or there are several work arounds just check the forum is your impatient.
 
Elite-1.jpg
Here is one image of Elite Dangerous being demonstrated with an Oculus Rift at a games convention,
It's images like this, convinced me that i should by purchase Elite.
 
You ever thought some of us are developers? We are a little caught between wanting to keep this game working and needing to upgrade the SDK and driver version to the latest Beta version so we can actually work on the latest version?

I assume that as a developer, you know about VM's, right? VMWare/VirtualBox is great for this.

From experience, if you find yourself developing on your primary gaming box, it ends in pain!

To the rest of you:

I personally don't see why some of you are getting so excited about this - I mean, it's currently unreleased hardware. Yes, they have it on their product information. So what? Are you really so mad at FD that you want a refund NOW for not fully supporting something that's not yet released?

If they don't add support when it goes to the commercial product, come back here and whine about it. As for now, all your legal bluster is putting across an ugly sense of entitlement that - quite frankly - contributes negatively to this community. Threatening legal action... Shameful behaviour.

/Rant
 
Last edited:
The question I have is, being one that upgraded to .6. And the old driver is no longer available on the oculus website.. Any know a link to reaquire the version that still works....prefer posted in this forum.....

Never mind went through this long kind of unnecessary thread and found a link..... Now real question does .5 work on windows 10? My luck no.......
 
Last edited:
The question I have is, being one that upgraded to .6. And the old driver is no longer available on the oculus website.. Any know a link to reaquire the version that still works....prefer posted in this forum.....

Never mind went through this long kind of unnecessary thread and found a link..... Now real question does .5 work on windows 10? My luck no.......

Links still available from the first one to the latest one here : https://developer.oculus.com/downloads/
 
If FD weren't "pushing" it, why associate with Oculus in the first place by using the Oculus to promote their product? As was the case at the launch.

Just saying.

Ok, how about this? Everyone who bought ED under the impression that it was a VR product as a result of FD advertisement/promotion, are reimbursed the price of purchase?

I'm sure you're just doing your job, but from a legal perspective, it's a perfectly reasonable argument worth pursuing.

Armchairs are for amateurs, and it may not be my last post.

Hats off to Brett, btw.


You are on the right track. Imagine this fictional scenario: customers of company P purchased the product based on VR support V1, and then the V1 support is removed, or worse, if P switches to a different VR platform V2 exclusively, then P would likely have to give refunds or face damages, given that V1 was the basis for the sale. In some countries, this is a form of "bait and switch" marketing (ie. feature X used to sell product, then feature X removed after the sale).

Arguments about the basis for the Oculus development agreement are way off, contracts between P and customer C (P<-->C) are different than contracts between C and the VR company O (C<-->O). Don't fret that people don't understand that.
 
Now real question does .5 work on windows 10? My luck no.......


Some people claim to have 0.5 working on Windows 10 with some hacking around. Regardless, 0.5 is not officially supported on Windows 10 so you are on your own if you go that path. Microsoft and Oculus both officially support SDK 0.7.


From Oculus website:

Preliminary support for Windows 10, which requires Direct Driver Mode [SDK 0.7]. If you are using Windows 10, make sure to get the recommended drivers.

Source - https://developer.oculus.com/downloads/pc/0.7.0.0-beta/Oculus_Runtime_for_Windows/
 
Some people claim to have 0.5 working on Windows 10 with some hacking around. Regardless, 0.5 is not officially supported on Windows 10 so you are on your own if you go that path. Microsoft and Oculus both officially support SDK 0.7.


From Oculus website:

Yea but that one is not working on elite d for me.....the reason for the roll back
 
FD have posted an FAQ about the recent vive announcement that says a few things about their plans for the rift.

https://support.frontier.co.uk/kb/faq.php?id=206

They will continue to support sdk 0.5 until the consumer rift is ready for launch. It seems a safe bet (not 100% certain, but very good odds) that they will announce updated rift support at that time.

- - - Updated - - -

Oh, and I have sdk 0.5, DK2 and ED working just fine together on win10 with no hacks. It upgraded very cleanly from win 8. CQC rocks!
 
Last edited:
- - - Updated - - -

Oh, and I have sdk 0.5, DK2 and ED working just fine together on win10 with no hacks. It upgraded very cleanly from win 8. CQC rocks!


SDK 0.5 is unsupported on Windows 10. Further, you can't use any of the other Oculus games or tools in VR that are built for SDK 0.7 if you run 0.5 in compat mode.


https://support.oculus.com/hc/en-us...s-Rift-Development-Kit-2-PLEASE-READ-UPDATED-

Preliminary support for Windows 10 has been included with the Oculus 0.7 SDK/Runtime, which requires Direct Driver Mode. If you are using Windows 10, please make sure to get the recommended drivers.

It is important to note that the Oculus 0.7 Runtime is the only version that is compatible with Windows 10. You can, however, run content compiled in Oculus SDK 0.6 or higher, if the Oculus 0.7 Runtime is installed. If you wish to continue running content compiled in earlier versions of the SDK (pre-0.6), you should NOT upgrade to Windows 10 at this time.
 
Just managed to get my DK2 going again since upgrade to win 10, works a real treat with dirt rally, shame I can use it with elite, Im off for more rallying, plz reconsider and patch a 0.7 version if not im not too worried i've got dirt to play in
 
SDK 0.5 is unsupported on Windows 10. Further, you can't use any of the other Oculus games or tools in VR that are built for SDK 0.7 if you run 0.5 in compat mode.


https://support.oculus.com/hc/en-us...s-Rift-Development-Kit-2-PLEASE-READ-UPDATED-

Several CMDR reported here they can use ED with SDK 5.0 and Win 10 without any specific tricks. I guess they are lucky and it depends the exact computer configuration. I can't imagine which benefit all those persons will have to lie here. I can also assure you I use SDK 0.6.0.1 (with Win 7 64 bits) with ED for month even if FD said it's not recommended and could not work.
 
Several CMDR reported here they can use ED with SDK 5.0 and Win 10 without any specific tricks. I guess they are lucky and it depends the exact computer configuration. I can't imagine which benefit all those persons will have to lie here. I can also assure you I use SDK 0.6.0.1 (with Win 7 64 bits) with ED for month even if FD said it's not recommended and could not work.

Cheers CMDRs
I play ED in Oculus DK2 using SDK 0.6.0.1 in a Windows10 with the 347.52 Nvidia driver, and thats the trick (old Nvidia drivers that dont use DirectX12, you can even install any of the 64bit win8.1 drivers). That Nvidia driver doesnt recognize incompatability with Win10 and installs. Then I just need to re-install oculus SDK (0.6.0.1) and despite of the warning message it works like it used to or even better). And VorpX and all the other stuff works aswell! The only thing thats annoying is that despite cancelling all auto-updates and installs my Win10 seems to override my instructions and from time to time (like 2 days or so) auto-installs the updated (forWin10) Nvidia drivers.. Takes about 5 minutes to re-install the old one and re-install de dk2 SDK back again. Doesnt even needs rebooting :)

Fly safe CMDRs!
 
This ED VR forum is essentially a forum where we all learn to become experts in the micro details of OS management from drivers, BIOS level and hardware specifics,
Someone needs to put together this list of requirements again?
Someone at ED must have read that article, 'How to maximise user value by introducing vaporware'
 
Agree. until CV1 and Vive is officially out we are in a slippy and difficult road for sure ;) After that all will be fine, casual consumer ready.
 

Slopey

Volunteer Moderator
Slopey, before you go any further with your commentary, can you let the users of this forum know what your position with Frontier is? Are you a representative or agent of the company? Are you employed by Frontier, Inc? Do you receive any kind of compensation from Frontier, or act as an agent of Frontier?

I'm a volunteer, not an agent, not employed, not renumerated in any way. And my comments were made as a customer and player of the game, nothing more (/mod hat off). Also Frontier are a UK plc, not a US entity. I'll leave the legal debate to others. :)

Meanwhile, I'm off to play CQC :)
 
Last edited:
Oculus SDK 1.0 has been given a Firm release date for Nov, I would assume FD may get their hands on it sooner ?
 
Last edited:
Oculus SDK 1.0 has been given a Firm release date for Nov, I would assume FD may get their hands on it sooner ?

i did not see the connect stream

is it still November or has it slipped to December? (ages ago it was said on the forums they hoped to have 1.0 out for November however i have noticed December now being thrown around. Just wondering what the official date is

thanks.
 
Back
Top Bottom