Today is the day...... SDK 0.7 launches.

It boggles me that FD have not been given preview drivers in advance (what the hell are oculus thinking?, ED is a shining VR example) , but from what the devs have said that seems to be the case.

is it possible that someone over at FD towers could post back once they have had a look and give us an idea if they think ED is likely to get updated to use it any time "soon"

Thanks
 
Last edited:
Working on Direct Mode display seems lot of work comparing the current extended mode which is "just" an extra monitor where you display your 3D SBS with the good fov (taking tracking API apart). I don't expect to see it implemented in ED quickly :(
 
"Advance access" lol

If the SDK isn't finished yet what good do you think it will do Frontier? I wouldn't even look at it until it was publicly available. In fact I might go a step farther and not update from 0.5 at all until the 1.0 SDK is publicly released.
 
"Advance access" lol

If the SDK isn't finished yet what good do you think it will do Frontier? I wouldn't even look at it until it was publicly available. In fact I might go a step farther and not update from 0.5 at all until the 1.0 SDK is publicly released.
really? no wonder you are not a developer. All developers working on products that tie in together share information prior to release. MS and Intel, Apple and ARM, virtually every game developer and nVidia, etc. No one waits for a final product to get started on something like this, you will be way behind at the onset.
 

SlackR

Banned
The whole thingie very messy to be honest. Youd think this wouldve be tied up weeks ago in time for windows 10.
 
really? no wonder you are not a developer. All developers working on products that tie in together share information prior to release. MS and Intel, Apple and ARM, virtually every game developer and nVidia, etc. No one waits for a final product to get started on something like this, you will be way behind at the onset.

But it's an SDK, not a driver. This is not consumer hardware, it is a development platform. The purpose of releasing an SDK at all is to permit developers to develop with it, after which they can release their application to take advantage of it. By purchasing a development kit, we've all jumped into the same boat as FDev with regards the Rift. Oculus draw no distinction between publishers that want to use their SDK and us, who're really just too impatient to wait for the consumer version.
 
It boggles me that FD have not been given preview drivers in advance (what the hell are oculus thinking?, ED is a shining VR example) , but from what the devs have said that seems to be the case.

is it possible that someone over at FD towers could post back once they have had a look and give us an idea if they think ED is likely to get updated to use it any time "soon"

Thanks


What's more likely:

A. Oculus Rift won't supply Frontier Development, currently the only developer doing something worthwhile with the Rift, with the most up to date SDK.

Or

B. Frontier Development holds the console release as a higher priority than the minority of users that have an Oculus Rift and have therefore diverted resources away from it.
 
Quote from Ed

As long-time supporters of VR and early adopters of Oculus, we remain in close communication with them as they work towards a production version of their SDK, but want to be open that without that SDK in hand, we cannot guarantee future compatibility.

I read that quote as referring to the production version that does not even exist yet.
 
The whole thingie very messy to be honest. Youd think this wouldve be tied up weeks ago in time for windows 10.

I'm not sure why you think that. Any one with any common sense wouldn't be blindly upgrading to Win 10 on day 1 or even for a few months yet.
 
What's more likely:

A. Oculus Rift won't supply Frontier Development, currently the only developer doing something worthwhile with the Rift, with the most up to date SDK.

Or

B. Frontier Development holds the console release as a higher priority than the minority of users that have an Oculus Rift and have therefore diverted resources away from it.

A. Because FD need the final released SDK not a preview.
 
But it's an SDK, not a driver. This is not consumer hardware, it is a development platform. The purpose of releasing an SDK at all is to permit developers to develop with it, after which they can release their application to take advantage of it. By purchasing a development kit, we've all jumped into the same boat as FDev with regards the Rift. Oculus draw no distinction between publishers that want to use their SDK and us, who're really just too impatient to wait for the consumer version.

This is how I've always interpreted the Rift rollout approach.
 

SlackR

Banned
@cylonsurfer ... Because its not like windows 10 came out of the blue ... You wouldve thought oculus wouldve been privy to the beta and had ample time to get the SDK up and running
 
Last edited:
Back
Top Bottom