He's a good'un, that Zac!
Got that CV1 finally.
- Thread starter ghcannon
- Start date
A (little) bit of counterbalancing journalism: http://arstechnica.com/gaming/2016/01/dont-worry-elite-dangerous-is-still-coming-to-the-oculus-rift/
well fudge ... :|
I updated to the latest firmware and finally have 1.0 working as intended with the Rift.
I kind of wish I didn't do it.
Every time I startup SteamVR or ED, the Oculus HubApp starts up and steals focus from whatever I want to run.
Starting SteamVR seems to also cause an issue in a particular sensor in the 'Base station'.
Elite barely starts properly on every tenth attempt and when it does, the inverted fish-eye filter that I was hoping to have fixed is now doubled in intensity. I haven't been ingame - no point.
Updating to the new firmware made the unit incompatible with pre-0.9 runtime ... so I can't go back. Kinda sucks :/
I don't know how the other guy got it to work but for me it sure is a pain ..
I updated to the latest firmware and finally have 1.0 working as intended with the Rift.
I kind of wish I didn't do it.
Every time I startup SteamVR or ED, the Oculus HubApp starts up and steals focus from whatever I want to run.
Starting SteamVR seems to also cause an issue in a particular sensor in the 'Base station'.
Elite barely starts properly on every tenth attempt and when it does, the inverted fish-eye filter that I was hoping to have fixed is now doubled in intensity. I haven't been ingame - no point.
Updating to the new firmware made the unit incompatible with pre-0.9 runtime ... so I can't go back. Kinda sucks :/
I don't know how the other guy got it to work but for me it sure is a pain ..
![[VR] Mad Mike](https://forums-cdn.zaonce.net/data/avatars/m/27/27910.jpg?1553527108){kind=avatar}
Well that is a bummer.
Incidentally what is the game you are making to have gotten access to the cv1? Always good to support fellow forumers so will keep eye out for it.
Has the runtime broke your app or was it easy to convert?
Incidentally what is the game you are making to have gotten access to the cv1? Always good to support fellow forumers so will keep eye out for it.
Has the runtime broke your app or was it easy to convert?
Joys of bleeding edge... ;(
Can't say what it is as it's confidential, however I can say where I work. Think of a creative toy company. First thing that comes to your mind
I'll have to ask Unity for that one
They're doing all the SDK integration.P.S - the Oculus Runtime is doing a lot of LiquidVR function calls when I have crossfire enabled
Good sign right there.
Last edited:
P.S - the Oculus Runtime is doing a lot of LiquidVR function calls when I have crossfire enabled
That... is one really interesting piece of data .. err info.
P.S - the Oculus Runtime is doing a lot of LiquidVR function calls when I have crossfire enabled
From what I can tell reading http://developer.amd.com/tools-and-sdks/graphics-development/liquidvr/ , it's a PC implementation of the same async timewarp that's available on GearVR. It'll hopefully allow you to have periods of gameplay where you dip under the 90Hz without the nasty juddering you get with the DK2.
John Carmack gave a super awesome amazing talk at Oculus Connect 2014 about this and a bunch more things, and if you're at all nerdy about this stuff then I highly recommend watching it. The section on what he calls Existence Proofs was a particularly good bit of engineering culture that I think about constantly.
Anyway, thanks for sharing the info, ghcannon.
Last edited:
Very correct, accelerated timewarp is one of the nice features in the Crimson suite.
LiquidVR is the default driver API that Oculus uses on AMD hardware.
However, get this - the Runtime reacts differently when I plug out the HMD, depending on whether I have XFire enabled or disabled.
LiquidVR is the default driver API that Oculus uses on AMD hardware.
However, get this - the Runtime reacts differently when I plug out the HMD, depending on whether I have XFire enabled or disabled.
Hmm, interesting. I do wonder why Oculus have deliberately kept back the v1.0 SDK behind what I assume are NDAs and whatnot. Its possibly this that fdev are balking at.
When Oculus say "The Rift SDK 1.0 and runtime include features tied to the consumer product, so we’ve currently limited the release to developers putting final touches on launch titles." I'm curious as to what secrets they're wanting to sit on top of until the latest possible moment.
They haven't kept back the 1.0 SDK - anyone who can prove he's a developer and has at least a DK2 can get that SDK.
It is the Runtime they don't want to make public and that's because they have some additional stuff with it that they don't wanna show yet.
Going on windows 10 today. Maybe I have more success.
It is the Runtime they don't want to make public and that's because they have some additional stuff with it that they don't wanna show yet.
Going on windows 10 today. Maybe I have more success.
No it's not a secret, as such.
It's rather a bit of unpolished software that they don't want ppl to use/see before they sort out the last issues.
'Native' timewarp ? What is that ?
Their code is cpp. It's as native as you can get. Now .. if you say accelerated timewarp that's a different thing.
Timewarp is not a secret.
It's rather a bit of unpolished software that they don't want ppl to use/see before they sort out the last issues.
'Native' timewarp ? What is that ?
Their code is cpp. It's as native as you can get. Now .. if you say accelerated timewarp that's a different thing.
Timewarp is not a secret.
I am hoping for Asynchronous Timewarp built into the driver that works independently of the developer. So every app will have it as an option for those with less than optimal hardware. Even just for those occasional FPS drops in the game play that might occur.
http://www.vrcircle.com/post/what-is-asynchronous-timewarp-and-why-should-you-care
https://www.youtube.com/watch?v=WvtEXMlQQtI
http://www.vrcircle.com/post/what-is-asynchronous-timewarp-and-why-should-you-care
https://www.youtube.com/watch?v=WvtEXMlQQtI
Last edited: