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

=AH= Sid

=AH= Sid
Just the driver from Nvidia and the SDK from Oculus won't make a difference, the GameWorks features need integrating into each game engine to make any use of them.
.
When can we expect a public release of VR SLI capable drivers?
Within the next few months. (However, drivers by themselves won’t automatically enable VR SLI—it will require integration into each game engine, so support for it will be up to individual developers.)
Click to expand...
See this four page article NVIDIA Takes the Lid Off ‘Gameworks VR’ – Technical Deep Dive and Community Q&A for full details.
.
Even once the 0.7 SDK is released it will take some time (IMHO) for developers to get their games updated to run with it, so don't rush out and buy a second card yet.
.
I've a vested interest here as I have two EVGA NVIDIA GTX TITAN X Hydro Copper Graphics Cards, but I'll be sticking with my currently working setup using the 0.5 SDK and a single card for now.
.
Once either ED or DCS get something working specifically with the new drivers, then I'll consider updating, for now I'm content to just sit on the sidelines watching.
.
As to whether VR SLI works with the single screen of the DK2 over the two screens of the CV1, I've no idea. Doesn't the CV1 still just have a single HDMI cable?
 

=AH= Sid

=AH= Sid
Cybereality puts it nicely;
.
Also, just to be 100% clear, a large portion of VR games were made with older SDKs and WILL NOT be compatible with the 0.7 Runtime. If you choose to update to Windows 10, you will NEED to use Runtime 0.7, which means you WON'T be able to play any of that content.
.
If you are a developer, it makes more sense to upgrade, since you can work on modifying your application to work with 0.7 and with Windows 10. As a gamer or enthusiast, it may make more sense to wait until more content has been updated with 0.7 compatibility.
Click to expand...
 

xondk

X
iced01 said:
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.
Click to expand...
Many people point out the advantages and disadvantages of the various stuff, but I think FDev has made it clear they want to support VR, however continually tweaking and updating to fit with what is still a beta product, and when the number of those users is small still then it makes no sense to invest a large amount of dev time when they can just wait until an official full release is out and adapt then. So while I agree it sucks, I would say, don't be too hard on Frontier because of it, their plan is to include it when it is released.
Instead urge Oculus to make a sort of patch or workaround to run games that use older stuff via with the latest SDK, oculus is the one that is developing the tech, they should be able to make it backwards compatible.
 

nightsmoke

N
xondk said:
Many people point out the advantages and disadvantages of the various stuff, but I think FDev has made it clear they want to support VR, however continually tweaking and updating to fit with what is still a beta product, and when the number of those users is small still then it makes no sense to invest a large amount of dev time when they can just wait until an official full release is out and adapt then. So while I agree it sucks, I would say, don't be too hard on Frontier because of it, their plan is to include it when it is released.
Click to expand...

What you're saying makes sense... But at the same time, I could see Frontier wanting to update in small increments along with the Oculus updates, rather than need a major update when 1.0 is released. Of course I have no idea how difficult it would be to make the changes. But since they supported older dev releases, supporting a new one doesn't seem that strange. Especially when it would immediately improve the user experience of their game with VR (Direct mode is so much nicer to start the game and more reliable in terms of which display is which, etc with Extended mode).
 

Star Lion

S
The thing is sdk 1.0 comes out in november so it makes sense to wait. What they should be investing time is in openvr sdk since the Vive is coming out this holiday
 
Last edited:

Star Lion

S
djbordie said:
by this holiday you mean 2016, same quarter as cv1...
http://www.digitaltrends.com/wearables/htc-vive-delayed-2016-news/
Click to expand...
I mean in 2 months. Expected release of Vive is November 2015. They said now limited quantities so it will be a race to get one

- - - Updated - - -

djbordie said:
by this holiday you mean 2016, same quarter as cv1...
http://www.digitaltrends.com/wearables/htc-vive-delayed-2016-news/
Click to expand...
Release date is november 2015 in limited quantities, those who cant get one will have to wait 2016 Q1. But even if The Vive is release in limited quantities in november the final consumer version and sdk must be available
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom