Oculus 0.7 SDK update

CMDR CPT. Boris

CMDR CPT. Boris
mattfor wehram said:
I have managed to get rift working with ED on windows 10 with 0.6.0.1 . I found a link on line how to do it (unfortunately I have lost the link but I will try to explain).
Basically remove all Rift software and install runtime 0.6.0.1. Errors will appear in windows 10 saying rift disconnected and rift will not attach.

Go into the program files where Runtime was installed and find the file OVRServer_86.exe. Check the properties of this file and ensure it is set to run in compatability mode for windows 8.

Then create a shortcut for this file on your desktop.

Click the shortcut before using Rift. The rift should now be attached and you can use the test screen and ED.

As I say this is from memory. If I find the link I will repost.

Safe flying :)
Click to expand...

Thanks for the info, so it's not complety lost, we still have a chance to rift ED on WIN10.
What about your drivers ? do you know what version do you have ?

By the way, are you using AMD ? (you said /.../86.exe)
I'm using Nvidia, so i should do it with the OVRserver_64.exe.

i will try to make it work, if you find the way to fix this please let us know.

Thanks

------------------
How could it work :
------------------

Os : windows 10
Runtime : 0.6.0.1
SDK : ??
drivers : ??
 

Juniper

Juniper
jabokai said:
Not sure how you got into the situation of not being able to boot at all but the whole process was a non-event for me. Had a PC with Win 8 and 0.5 SDK - upgraded to W10 - everything still just worked. Not saying you did anything wrong, but the old SDKs do work on W10... somehow! But it obviously varies from PC to PC. ;)
Click to expand...

The "upgrade" from 8.1 failed spectacularly & wholly unsurprisingly, so I had to wipe clean and do a fresh install.

It complained bitterly about "rift.sys", and left me with a blank screen on boot. Could not even delete this file. I got back in by booting into Safe mode (Microsoft don't like you to do that any more it seems... they've made that procedure very complicated now if you don't have a working system to boot from) twice - first to uninstall the Oculus runtime, and then again to manually delete "rift.sys".

I won't be doing that again.

Glad you got it running though. :)

mattfor wehram said:
I have managed to get rift working with ED on windows 10 with 0.6.0.1 . I found a link on line how to do it (unfortunately I have lost the link but I will try to explain).
Basically remove all Rift software and install runtime 0.6.0.1. Errors will appear in windows 10 saying rift disconnected and rift will not attach.

Go into the program files where Runtime was installed and find the file OVRServer_86.exe. Check the properties of this file and ensure it is set to run in compatability mode for windows 8.

Then create a shortcut for this file on your desktop.
Click to expand...

Thanks, yes I tried all of that... it left the machine unable to boot because of the Oculus display driver. I'm running an AMD Crossfire system (2 x 7870s).
 
Last edited:

mattfor wehram

M
Cmdr CPT boris

I currently run an nivdia gtx 970 with 350.12 driver installed as advised by Oculus. Turn off auto update for graphics drivers.

I'm not very technical so just followed the instructions on line when I had them and it seemed to work. So couldn't possibly comment about 64 or 86. I use the 86 and it works for me with no issues. My advice would be to try it and if not then shortcut the 64 file and make it windows 8 compatible.

I couldn't find the exact website I was using but have found something similar. Hope it helps http://www.vrbites.com/tech-howto/run-oculus-0-6-0-1-in-windows-10/
 

mattfor wehram

M
Juniper said:
The "upgrade" from 8.1 failed spectacularly & wholly unsurprisingly, so I had to wipe clean and do a fresh install.

It complained bitterly about "rift.sys", and left me with a blank screen on boot. Could not even delete this file. I got back in by booting into Safe mode (Microsoft don't like you to do that any more it seems... they've made that procedure very complicated now if you don't have a working system to boot from) twice - first to uninstall the Oculus runtime, and then again to manually delete "rift.sys".

I won't be doing that again.

Glad you got it running though. :)



Thanks, yes I tried all of that... it left the machine unable to boot because of the Oculus display driver. I'm running an AMD Crossfire system (2 x 7870s).
Click to expand...

Sorry I don't know much about AMD or anything really but the following link says to delete a different file to rify.sys called riftenable.sys before installing.

Again it is the link provided http://www.vrbites.com/tech-howto/run-oculus-0-6-0-1-in-windows-10/
 

CMDR CPT. Boris

CMDR CPT. Boris
mattfor wehram said:
Cmdr CPT boris

I currently run an nivdia gtx 970 with 350.12 driver installed as advised by Oculus. Turn off auto update for graphics drivers.

I'm not very technical so just followed the instructions on line when I had them and it seemed to work. So couldn't possibly comment about 64 or 86. I use the 86 and it works for me with no issues. My advice would be to try it and if not then shortcut the 64 file and make it windows 8 compatible.

I couldn't find the exact website I was using but have found something similar. Hope it helps http://www.vrbites.com/tech-howto/run-oculus-0-6-0-1-in-windows-10/
Click to expand...

Thanks for the tips, have some rep :D
i will try all this at home

**************************

Edit : It's working fine, thanks a lot
 
Last edited:

SOTBMP

SOTBMP
I hope ED will be working on CV1 and 1.0 SDK.
Keep trying Frontier! Do your best!
I keep my fingers crossed for you.
 

rennarda

R
I don't really care which VR system ED supports - but I do wish Frontier would give a clear and unambiguous statement on their planned support, so that I can make the correct purchase decision. I currently have a DK2, but only ever saw that as temporary until the CK1 came out. Now Im confused as to whether Oculus will even be supported, going forward.
 

Herne

Herne
I think to be fair, until they have the sdk 1.0 in their hands, it would be foolish to say yes don't worry, it will definitely work. It's understandable though that they may want to wait for the sdk 1.0 given that all future SDK's will be backward compatible to 1.0.

Oculus do need to get their act together, and publish the release SDK, otherwise I will be buying the HTC Vive just for the ED VR experience, which is already great with a Dk2
 
Last edited:

Whiteball

Whiteball
Herne said:
I think to be fair, until they have the sdk 1.0 in their hands, it would be foolish to say yes don't worry, it will definitely work. It's understandable though that they may want to wait for the sdk 1.0 given that all future SDK's will be backward compatible to 1.0.
Click to expand...
Yes, well said.

Most people here seem to be forgetting that the DK2 is a devkit and Oculus were stressing the point themselves that only devs should buy them not end users.
You can't really complain if something works or not when you've ignored all the warnings and caveats in the first place.

And just for the record, I had a DK2 myself and really find it hard playing Elite now without it. It truly is the only way to experience it.
However, common sense prevailing, I sold it in order to wait for finished and finalised hardware AND software before making my final VR purchasing decision when all the dust has settled.
 

MainframeCN

M
Actually they have previously stated they plan to support de final rift product.

Mind the statement is still ambiguous.
A quote of frontier:
"I can confirm for you now that we do plan to support the full release of Oculus Rift, although as you're aware, we don't support SDK version above 0.6. currently."
 

grammatonfeather

grammatonfeather
I think the news could have been delivered in a less cryptic way. Almost as if he is wanting to create a sense of mystery, fear and dread. I guess there are issues with 0.7 runtime just as there were bugs with 6.0.1. I noticed 6.0.1 is more juddery but it works with Steam VR. 5.0.1 is better with Elite but doesn't work with SteamVR.

Elite D is absolutely amazing with Oculus and I hope that continues. Star Citizen is apparently broken with VR support now after a Crytek engine change/update.

0.7 Runtime works with hardly any Oculus demos. It gets rid of extended mode which is a good thing.
 

seanwasere

seanwasere
Gee, did you here that Oculus released a new runtime called 0.7. I can't wait for it to be supported in E:D. That will be amazing. Does anybody have the latest news when it will be ready. I'm so excited. I just found out. I'm all updated and ready. Here's hoping. Hope i didn't miss anything.
 

negatron99

negatron99
Coming from a developer's point-of-view, it got developed on 0.5. It got developed using the "quick-and-dirty"... "get it working" system.

This was the extended mode. The mode that makes the Oculus present itself as another monitor.

The problem is, these quick-and-dirty systems have a habit, once they 'just work', of becoming the permanent system.

Because no one wants to, has the time to, has the budget to, go back and use the correct way of implementing it. I mean, what's the point... it's "working fine for me".

"Extended mode" has been totally removed. Because, well, it was a poor hack.

And well... the people who haven't had the chance to fix their code, are now annoying the people who are using their code.

I can't understand the technical issues why the upgrade to 0.7 won't happen. I understand there were problems getting 0.6 working in Direct Mode. Maybe it's a similar problem.

However, 0.7 is supposed to fix one major issue... Windows 10 compatibility. It does work on Windows 10, I had to install it to get the measurements for my eyes so ED wouldn't look like a rainbow, before uninstalling it and putting 0.6 back in.
 

justintime

J
I'm just praying to the thargoid gods that .5/.6 works with horizons. I got my system hacked just right to make ed work on win 10... I can't go back to a monitor... I won't go back to monitor!
 

tommywright

tommywright
ED is placing it's bet on the Vive which is fine but I sure wish we could play right now with the Oculus because it's all that most of us have. I'm sure to buy the Vive when it comes out. That's when I'll pick up ED again. :)
 

grammatonfeather

grammatonfeather
Zac Antonaci said:
Hi everyone,

We’ve had a number of requests for an update regarding the Oculus SDK 0.7. Over the recent weeks we have been working closely with Oculus to investigate the subject and we’re now able to give you an update. We understand that this news may disappoint some of you but we wanted to make sure you had the information at the earliest available opportunity.

We have supported Oculus as far as we can, but Elite: Dangerous is not compatible with Oculus SDK version 0.7, and 1.4 doesn’t change that. We hope a future version of their software can be made to work and we are continuing to work with them on this. Elite: Dangerous 1.4 does continue to work with Oculus SDK 0.5 and 0.6, but we continue to ask that players do not upgrade their Oculus SDK beyond 0.6 if they want to continue to play Elite: Dangerous. Our VR support continues to improve and we now also have support for SteamVR and the htc Vive.

I’m going to be checking in on the thread regularly so please do let me know if you have any questions.

Thanks,

Zac
Click to expand...

But SteamVR also supports Oculus. I can play HL2 and TF2 through steamvr so does this mean that ED will also run via steamvr now and in the future?

Actually... I can't play HL2 or TF2... Apparently valve have updated steam and now steamVR is broken again (people have reported) and I can't get the games to work.

Edit: SteamVR works - just a bit weird the way it runs. The steam menu on VR is behind me. Also HL2 looks amazing on oculus but when I get in a vehicle I'm facing the wrong way. I have to issue a VR-Reset command on HL2 console in game.

Anyway... never mind... I am rambling like a mad person.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom