ED works on SDK 0.8 using OpenVR (that's how I play on my DK2). Also, Frontier didn't say Elite won't be working with CV1 natively at launch, they said they *currently* don't have it working, but they are actively working with Oculus to try and make it happen.
In what way? The fact that they added Vive support when the Vive was supposed to be the first consumer VR device out, or the fact that they stopped working on Oculus support because Oculus announced that each SDK until 1.0 could break support for previous SDKs thus making them do extra work? Or maybe the fact that they were blindsided by the sudden preorder announcement? Yeah, you're right, there are no good reasons for the things they've chosen to do other than "Frontier and Oculus hate each other now".
Welp, Palmer just posted this to his twitter.
Might be nothing, but I have my fingers crossed.
For anyone that doesn't get it, the image means there's one more thing that hasn't been mentioned yet
Well, it kind of makes sense to prioritize OpenVR unless you are bought.
Yeah, because Oculus announced that 0.7 was going to break compatibility with 0.6 without extra work by the developer, and that 0.8, 0.9, and 1.0 probably would keep breaking support with each previous SDK as well, as the SDK and API changed. No real company with a real budget would do the extra work of supporting each update for little purpose except make a very very small market of people with development kits happier. Best to wait until it all stabilizes and do all the work at once.
Well yeah, because Vive was supposed to come out in 2015. Are you saying it was a bad business decision that nobody else would make, to support the first VR headset on day 1? That the only possible reason to make this business decision is that there's some sort of falling out with Oculus?
I guess this might be the real problem, you don't know what the term "fallout" means. In business terms, when two companies have a fallout, it means they used to be partners but are now having a huge quarrel or disagreement.
It was stated today that there would be NO Vive exclusives whatsoever.
Different kinds of games have different needs visually and positionally. Cockpit games like FSX work great with asynchronous time warp because near field objects such as your instruments do not move very much within your field of vision. In a traditional first person shooter however near field objects can parallax significantly, something asynchronous time warp does not handle well. In these cases you're better off without async because of the visual artifacts it could cause.
Ohhh of course. I can totally see how a fast paced fps game with moving objects that are close to you could have serious problems with the predictive method that Timewarp uses in altering the image from the previous frame. I guess it's probably going to be limited to cockpit based games mainly. It really does work amazingly well in this particular application.
Isn't it what we have been hearing for the past 4-6 month ?
We can only hope that we will know more about that tomorow.
