Oculus Rift 0.7.0 SDK

Hé hé, all that is speculation and imagination. Nobody knows what they will do at the end. People talk like if it was fact, it's annoying...

Now, let me play the same Crystal Ball game: the question is not if they will update ED to be compatible with 0.7.0.0, the question is: When?
 
I don't think we'll see any further support on Oculus in ED until at least 30 April 2016, that is the date the original Microsoft context sensitive menu system patent expires,
http://www.google.co.uk/patents/US5664133
and since ED uses context menus triggered by a HMD, there will be other patents on top of that.
Don't hold your breath people, unless someone such as FD or Facebook, or even the customer, can come up with the money to pay off that backlog of patent violation claims.
 
I don't think we'll see any further support on Oculus in ED until at least 30 April 2016, that is the date the original Microsoft context sensitive menu system patent expires,
http://www.google.co.uk/patents/US5664133
and since ED uses context menus triggered by a HMD, there will be other patents on top of that.
Don't hold your breath people, unless someone such as FD or Facebook, or even the customer, can come up with the money to pay off that backlog of patent violation claims.

You certainly know your stuff Sean. Do you think the Oculus/Microsoft business acquisition for selling Xbox controllers with the public release of the oculus headset next year, will essentially allow specific usage rights to the context menu system prior to multiple patent expiry dates? Maybe a deal was made no?

Probably talking out my ass, but just a thought :)
 
I don't think we'll see any further support on Oculus in ED until at least 30 April 2016, that is the date the original Microsoft context sensitive menu system patent expires,
http://www.google.co.uk/patents/US5664133

First, that patent expired Dec 13, 2013 (20 years from date of priority). Second, infringement of a patent would be irrelevant of SDK version unless you are thinking of a feature that specifically was added in 0.7. The main change in 0.7 is direct mode support.


and since ED uses context menus triggered by a HMD, there will be other patents on top of that.

This is nonsense. What patents are you talking about that are blocking HMDs? Who are the patent holders that you are worried about?


Don't hold your breath people, unless someone such as FD or Facebook, or even the customer, can come up with the money to pay off that backlog of patent violation claims.

You obviously don't understand how patent infringement (not violation) works.

The likely reason that Frontier is not supporting 0.7 SDK is because either (1) they have struck a deal with HTC Vive to move Elite to that platform, or (2) the Elite engine is completely incompatible with Direct Mode rendering and Frontier is too busy working on Horizons to bother spending dev cycles fixing it.
 
Well, who knows??? Maybe for the Glorious Release of HORIZONS we'll be getting something... even if we wont, I'll be happy when I can still use my DK2!
 
First, that patent expired Dec 13, 2013 (20 years from date of priority). Second, infringement of a patent would be irrelevant of SDK version unless you are thinking of a feature that specifically was added in 0.7. The main change in 0.7 is direct mode support.




This is nonsense. What patents are you talking about that are blocking HMDs? Who are the patent holders that you are worried about?




You obviously don't understand how patent infringement (not violation) works.

The likely reason that Frontier is not supporting 0.7 SDK is because either (1) they have struck a deal with HTC Vive to move Elite to that platform, or (2) the Elite engine is completely incompatible with Direct Mode rendering and Frontier is too busy working on Horizons to bother spending dev cycles fixing it.

I predict (1) they have struck a deal with HTC Vive to move Elite to that platform
 
First, that patent expired Dec 13, 2013 (20 years from date of priority). Second, infringement of a patent would be irrelevant of SDK version unless you are thinking of a feature that specifically was added in 0.7. The main change in 0.7 is direct mode support.




This is nonsense. What patents are you talking about that are blocking HMDs? Who are the patent holders that you are worried about?




You obviously don't understand how patent infringement (not violation) works.

The likely reason that Frontier is not supporting 0.7 SDK is because either (1) they have struck a deal with HTC Vive to move Elite to that platform, or (2) the Elite engine is completely incompatible with Direct Mode rendering and Frontier is too busy working on Horizons to bother spending dev cycles fixing it.

Absolutely. If context menus were a violation/infringement then surely FD would have to take them out or pay up and as far as I know they are doing neither. I suspect it will be simply your number 2. They will likely be waiting to see how the whole VR implementation works. Nvidia are pushing for a common standard (similar to DirectX) so that game developers would not need to specifically support the Oculus Rift, Vive or any other HMD as they will all work with a common API. If I were FD I'd be waiting to see what happens in this space and certainly would wait for Oculus to get closer to 1.0 of the SDK (where you'd expect the flux in the API to have settled down) before expending valuable development cycles on something only 10% of the user base have any use for.
 
Only 228 days to go, before we get our next word on the future of Oculus in Elite Dangerous.

Patently has absolutely NO idea what he is spruiking about. Probably thinks that making such ridiculous claims will force Frontier to make some statement. They are much smarter than that !
 
The problem I have is this; I use Windows 10 and cant use 0.7.0 runtime since ED doesnt support it, and all other titles now support latest version to cater for Windows 10 compatibility.
 
Just got a twitter response from Elite Dangerous official account: "We're still working with Oculus. We'll keep everyone informed once we have more information." at least is an answer.
 
Just got a twitter response from Elite Dangerous official account: "We're still working with Oculus. We'll keep everyone informed once we have more information." at least is an answer.

Actually it isn't an answer at all. Could mean "we don't have decided whether we'll support the Rift further", could mean "we won't support the DK2 any futher but are talking with Oculus about CV1 support later next year" or even "we are currently not planning to support Oculus any further right now. We keep in touch with Oculus to try to work out some contract all parties can agree upon."
 
Actually it isn't an answer at all. Could mean "we don't have decided whether we'll support the Rift further", could mean "we won't support the DK2 any futher but are talking with Oculus about CV1 support later next year" or even "we are currently not planning to support Oculus any further right now. We keep in touch with Oculus to try to work out some contract all parties can agree upon."

In conjunction with what they've said previously - "We’re working with Oculus to try and resolve this and will let you know when there is news on that." - and the fact the tweet says "still working with Oculus"... well, you can do your scary conspiracy, abandoment dance but the rest of us can read it for what it is. :)
 
Actually it isn't an answer at all. Could mean "we don't have decided whether we'll support the Rift further", could mean "we won't support the DK2 any futher but are talking with Oculus about CV1 support later next year" or even "we are currently not planning to support Oculus any further right now. We keep in touch with Oculus to try to work out some contract all parties can agree upon."

I think you are reading too much negativity in to their reply.
They have said dozens of times they are committed to VR

- - - Updated - - -

Just got a twitter response from Elite Dangerous official account: "We're still working with Oculus. We'll keep everyone informed once we have more information." at least is an answer.

Awesome news
 
Back
Top Bottom