Got that CV1 finally.

[jabokai]

I tested with runtime 0.8. I honestly don't think anybody has 1.0 yet since it just isn't ready. But you did give me an idea - I'll ask tomorrow if there's a newer dev. version.

It shipped to select developers according to a posting by Oculus on Dec 21st. At the same time they're probably still tweaking it, I'd guess.

 

[Asp Explorer]

A CD case and a drop of water will work

 

[ghcannon]

It shipped to select developers from Dec 22nd according to a posting by Oculus. At the same time they're probably still tweaking it, I'd guess.

Nice! Gonna see tomorrow

- - - - - Additional Content Posted / Auto Merge - - - - -

A CD case and a drop of water will work

Fair enough, I'll see if I can see it but, again, I really think I'll be keeping my mouth shut on this one. Sorry.

 

[vic]

Continuing the saga

Just revived the PC, put the old drivers and tried again with 0.6 runtime - no juice.
The HMD is simply not getting picked up by the service. Neither is the base station.

Going back after the hack with SteamVR. Have a chance to see how it is with the older drivers.

My DK2 works flawlessly with 0.6 playing ED. Have you tried your DK2 with 0.6?

 

[ghcannon]

Haven't tried it now, since as I stated in the linked thread above, I gave it to a friend while I have the real deal.
If I remember correctly the last runtime I played with was 0.4

But honestly it looks to be pretty much unsupported. Not that surprising really. It must be at a low level too, since messing around with hardware tags didn't trick it.

 

[Soda Popinski]

@ghcannon


Have you changed your mind in any way now you have played around with it for a few days?

Also, is it made up of 1 or 2 screens

Pretty sure it's confirmed to have 2 screens. They move along with the lenses when you do the IPD adjustment, I think.

Here's the exploded view of the CV1, and it looks like 2 screens to me.

 

[vic]

Haven't tried it now, since as I stated in the linked thread above, I gave it to a friend while I have the real deal.
If I remember correctly the last runtime I played with was 0.4

But honestly it looks to be pretty much unsupported. Not that surprising really. It must be at a low level too, since messing around with hardware tags didn't trick it.

Actually 0.6 skd is the only version actually supported according frontier. This was released from Frontier few days ago:

"Hey everyone,

With the news that Oculus are starting pre order of their consumer version tomorrow, I wanted to just make a quick post to confirm that we are still actively working with Oculus but currently the only SDK we are able to officially support is 0.6.

We wanted to make sure you had as much up to date information as possible and will let you know as soon as we have any more information.

Fly safe, Commanders!"


I have the feeling the problem is your amd card/drivers

 

[ghcannon]

Let me reiterate what the problem is : The Oculus Runtime 0.6 does not validate the CV1 HMD as a VRReady device.

I'm completely lost as to what you're trying to solve and why Elite and SDKs are in it at all.

 

[vic]

Let me reiterate what the problem is : The Oculus Runtime 0.6 does not validate the CV1 HMD as a VRReady device.

I'm completely lost as to what you're trying to solve and why Elite and SDKs are in it at all.

Sorry I was just trying to help you isolate the problem. But since you don't have the DK2 on-hand you cannot say for sure that 0.6 does not properly validate the CV1.. It still could be because something else got messed up somehow. You should go get back the DK2 to help you sort it out more efficiently. Just my personal take.

and oh yeah are your usb ports version3.0 as specified?

 

[Slopey]

What would be the point of confirming the 0.6 Runtime works with the DK2 - we know it does. The point is the CV1 doesn't work with earlier runtimes (which isn't surprising).

 

[Soda Popinski]

What would be the point of confirming the 0.6 Runtime works with the DK2 - we know it does. The point is the CV1 doesn't work with earlier runtimes (which isn't surprising).

I'd say it's unlikely, but there's a possibility that the 0.6 Runtime could work with the CV1, but since we don't have a positive control in this particular example that the 0.6 Runtime is functioning post system crash, we don't know 100% for sure. That could be remedied by plugging in a DK2 to make sure it does work. I couldn't get 0.6 working for me under Windows 10 64-bit, but 0.5 does.

That said, I'd be very surprised if 0.6 works with CV1.

 

[vic]

What would be the point of confirming the 0.6 Runtime works with the DK2 - we know it does. The point is the CV1 doesn't work with earlier runtimes (which isn't surprising).

Yes I know 0.6 works with DK2 since it is what I use, but the point is to help ghcannon becuase he may have something else messed up on HIS pc. like not having usb3.0/drivers correct,currpted files etc. It is possible with all the playing around he did behind the scenes and at low-level. Plugging back the DK2 is just to confirm all is still well. It's how I troubleshoot at work and I am the technical lead in my dept at work for high-end digitizers. I call it the return-to-golden-system before continuing when at a loss.

 

[Adam Lusardi]

I have to agree......not to decry all the good work gbcannon is doing but work to a baseline and revisit it. Most designers I work with tend to leave the baseline and drift off in there own direction until wound back to reality every so often.

 

[ghcannon]

Guys I told you I did try with old drivers, a couple of hours ago - and it didn't work. I went back a full year on the drivers. So much so that the 0.8 runtime refused to run with them.

- - - - - Additional Content Posted / Auto Merge - - - - -

I'm actually just wrapping up the old setup. Maybe on a clean bed I'll have more luck with xfire disabled. Either way I plan on actually playing some tonight.

As for the trick with the disc cover and water drop - couldn't see anything from the droplet I'll be getting someone with glasses to come over for a visit

 

[ghcannon]

Woohoo! After every bad evening comes a good one ...

Got it to work with a single card in disabled crossfire mode.
A single unclocked R9 290 chugs out 90 FPS in stations on medium settings. I'm sure medium-high is very much not a problem.
Have perfect positioning and rotation tracking, no extra latency ...

It works BEAUTIFULLY even with the SteamVR middleware thing.

Here's a pic to avert the trolls:

 

[Thorvald]

Great job Ghcannon, nice to see! Don't forget that the new SDK 0.8 and up have an onscreen performance hud, you have to access it via the Oculus tray icon.

Configuration Utility -> Tools Menu - Advanced -> Show Performance HUD -> Perf headroom


It has lots of great info but does take up a chunk of screen space to show it.

Cheers
Tim

 

[Space Dandy]

Woohoo! After every bad evening comes a good one ...

Got it to work with a single card in disabled crossfire mode.
A single unclocked R9 290 chugs out 90 FPS in stations on medium settings. I'm sure medium-high is very much not a problem.
Have perfect positioning and rotation tracking, no extra latency ...

It works BEAUTIFULLY even with the SteamVR middleware thing.

Here's a pic to avert the trolls:

View attachment 93178

Which sdk did you use and from this post I gather the issue was crossfire?

 

[SLeeC]

Nice pic! look at the size of those lenses
Will be nice to try the new erognomics, i look 5 years older after a sesh wiht the DK2 and pixel vision :-(
Roll on April...

 

[[VR] Mad Mike]

Woohoo! After every bad evening comes a good one ...

Got it to work with a single card in disabled crossfire mode.
A single unclocked R9 290 chugs out 90 FPS in stations on medium settings. I'm sure medium-high is very much not a problem.
Have perfect positioning and rotation tracking, no extra latency ...

It works BEAUTIFULLY even with the SteamVR middleware thing.

Here's a pic to avert the trolls:

Good work. Did this involve anything that the average jo could not do ? Ie my monitor can only pump out 60hz so if it involves having to have my monitor running at 90hz to get the rift running properly I would be snookered.

If not however then , so long as steamvr does not remove support via an update we should all be safe for ED in CV1

But then... How come FD are not telling us about it?

Thanks for the info

 

[Sir.Tj]

Woohoo! After every bad evening comes a good one ...

Got it to work with a single card in disabled crossfire mode.
A single unclocked R9 290 chugs out 90 FPS in stations on medium settings. I'm sure medium-high is very much not a problem.
Have perfect positioning and rotation tracking, no extra latency ...

It works BEAUTIFULLY even with the SteamVR middleware thing.

Here's a pic to avert the trolls:

View attachment 93178

Ooooooohhhhhhh Shiny....