Important Notice Regarding Oculus 0.6 SDK
- Thread starter Frontier QA
- Start date
Im still using a the previous SDK (not 0.6.0.1) no problems.
Secondly, the DK2 is not a consumer product, so yes at this point they don't care about consumers.
This message has been displayed in big letters when you bought this device.
When i bought mine i expected these kinds of things, at least i have some virtual reality at home ;-)
Hopefully Elite will have the stuff working when the real oculus comes out
, because that's a consumer product.Im still using a the previous SDK (not 0.6.0.1) no problems.
Secondly, the DK2 is not a consumer product, so yes at this point they don't care about consumers.
This message has been displayed in big letters when you bought this device.
When i bought mine i expected these kinds of things, at least i have some virtual reality at home ;-)
Hopefully Elite will have the stuff working when the real oculus comes out
I know its not a consumer product. I've been used to kind of hacky work arounds and broken things since I got my DK1 2 years ago. I would still hope that Frontier would be working to get their product in some semblance of working order for when CV1 comes out. If they're not fixing bugs now, what will they do when the final product comes out and they waited to the last minute?
![[VR] Mad Mike](https://forums-cdn.zaonce.net/data/avatars/m/27/27910.jpg?1553527108){kind=avatar}
unless you are a dev, just roll back to SDK6 imo.
dont get me wrong i would love ED to use the new SDK properly, if it is anything like the improvements ETS2 saw when going to SDK 6 we will be in for a treat.
dont get me wrong i would love ED to use the new SDK properly, if it is anything like the improvements ETS2 saw when going to SDK 6 we will be in for a treat.
way off track now.... however i have not tried virtual desktop for maybe 6 months.
i dont suppose it supports playing 2D games from steam at all yet does it? everyone i tried last time crashed.
i would love to play a few of them on a cinema sized screen
way off track now.... however i have not tried virtual desktop for maybe 6 months.
i dont suppose it supports playing 2D games from steam at all yet does it? everyone i tried last time crashed.
i would love to play a few of them on a cinema sized screen
It certainly does, and does it very well for many games.
However (caviat) most will only run properly in window mode (or borderless window).
This is my issue as well... It is also keeping me from upgrading top Win 10, because the new SDK will more than likely also not be compatible with ED... Le sigh.
Any update on this Frontier please? Been quite a long while now.
I'm Running 6.0.0.1 in extended mode and it is running great, still on Win 8.1 mind you, I found I had to play around with one of the VR sliders in graphic settings ( it's near the bottom, sorry can't remember the name of it and i'm away from home atm on business so no access to the game ) to get rid of some station stutter but once i did that it now runs perfect.
I'm running a GTX 970
Edit: There is a strange sweet spot in the slider for me, If i lower it to much i get stutter and to high is the same ( no idea how this works ) but for my rig I found the sweet spot was around 1/2 to 3/4 on the bar.
Hope this helps some people suffering big stutter on 6.0.0.1
I'm running a GTX 970
Edit: There is a strange sweet spot in the slider for me, If i lower it to much i get stutter and to high is the same ( no idea how this works ) but for my rig I found the sweet spot was around 1/2 to 3/4 on the bar.
Hope this helps some people suffering big stutter on 6.0.0.1
Last edited:
I'm running Oculus SDK 0.6.0.1 in extended mode. Windows 7. Running GTX770's in SLI. Using Nvidia drivers 347.52. Elite dangerous works fine in oculus rift with rift as primary monitor.
What is the issue people are having? Did you hit F12 to reset the view? Because sometimes the view is totally screwed up and you think you can't see anything!
What is the issue people are having? Did you hit F12 to reset the view? Because sometimes the view is totally screwed up and you think you can't see anything!
Forget 0.6 - 0.7 is inbound.
tl;dr: 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.
tl;dr: 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.
i thought anything built with 0.5 or upwards WOULD be supported?
edit, may mistake, so it needs to be 0.6 at least. I hope this is inhand over at FD otherwise a lot of people will no longer be able to play ED!.
Last edited:
Why? Won't be an issue if users don't upgrade to the 0.7 drivers...
To be able to use the new OR driver, applications need to be built around at least the 0.6 runtime. If FD don't have an update out in time for the release of the 0.7 driver then stick with version 0.6 or whatever's working now and nothing changes.
true enough, and that will be fine until other apps start to migrate over to the 0.7 branch. Whilst ED is my most played game in VR, it isnt my only one
I am guessing (so may be wrong) that once apps are updated to 0.7 they will no longer play nicely with the older SDKs.
I am guessing (so may be wrong) that once apps are updated to 0.7 they will no longer play nicely with the older SDKs.
Fair point, this is likely to be the start of a rocky road between now and the launch of the CV1.
That's the problem with being at the bleeding edge of the bleeding edge, I guess.
I can see a future with lots of reinstalling of SDKs to suit the game of choice at that moment, or multi-boot with several different Windows partitions (and maybe versions) with different SDKs and different games on each.
I only got back into PC gaming for ED so there's nothing pushing me to move away from the tried and tested, but for those of you playing different games with different requirements it must be a bit of a headache already - this fork at 0.7 (well 0.6 really) is going to make it really fun for you!
That's the problem with being at the bleeding edge of the bleeding edge, I guess.
I can see a future with lots of reinstalling of SDKs to suit the game of choice at that moment, or multi-boot with several different Windows partitions (and maybe versions) with different SDKs and different games on each.
I only got back into PC gaming for ED so there's nothing pushing me to move away from the tried and tested, but for those of you playing different games with different requirements it must be a bit of a headache already - this fork at 0.7 (well 0.6 really) is going to make it really fun for you!
Would not be much of an issue if it did not also happen at the same time that Windows 10 is being pushed very hard.
Essentially all previous versions of .7 - and even that version is not supported - will be incompatible with the new operating system and Oculus has stated that previous versions to .6 in older versions of Windows will be deprecated.
As many people that use a DK do so for far more than just play Elite, this inconsistent break between versions means that one has to restrict the DK usage to specific applications, and possibly hold on upgrading OSes or using newer versions of VR software and utilities.
Not a nice situation to be in.
My hope is that Oculus will provide the SDK .7 that will be compatible with Win10 (even if not supported) and that FD adapt that SDK (since reports are that .6 broke the game) for at least release 1.5.
That way, I won't have to invest in the wizardry of having multiple or virtual OS just to enjoy the ever increasing facets of VR.
Essentially all previous versions of .7 - and even that version is not supported - will be incompatible with the new operating system and Oculus has stated that previous versions to .6 in older versions of Windows will be deprecated.
As many people that use a DK do so for far more than just play Elite, this inconsistent break between versions means that one has to restrict the DK usage to specific applications, and possibly hold on upgrading OSes or using newer versions of VR software and utilities.
Not a nice situation to be in.
My hope is that Oculus will provide the SDK .7 that will be compatible with Win10 (even if not supported) and that FD adapt that SDK (since reports are that .6 broke the game) for at least release 1.5.
That way, I won't have to invest in the wizardry of having multiple or virtual OS just to enjoy the ever increasing facets of VR.
upgraded to 0.6.0.1 for other new demos. Just tested Elite - glad to report everything still runs smoothly.