Okie doke, this version works for me. That rotation was evil, I think that made it hard to see the lack of eye parallax (besides making me dizzy!). Tested with 29.2_x86 and 30.2_x86 on Win7.

Hey mediadog, if you're sure about the wrong connections, go ahead - I ported directly from Unity and tried to make the same calculations as were done in the code there, but of course I may have done a mistake.

Concerning the HID grab by vvvv: it appears the HID nodes do scan and get all HID devices (there are some messages logged on the console during startup). I tried adding an HID Device node, setting the Device Type pin to "Tracker DK", and then the Enable pin to False, but it still was not seen by the Rift plugin.

Looks like there needs to be some way to really release an HID device via the HID nodes, and then initialize the Rift.

I think you're right, because those images appear to be lacking eye shift as well. If you freeze the video when there are objects very close, you can see there is no shift in them relative to the background between the right and left images - like there is when you look at your thumb in front of you and alternately blink your eyes, objects in the distance jump sideways.

There are many things that make up depth perception, R/L parallax just being one - so there is still a sense of depth even without it due to shading and relative motion. So when you freeze the motion the lack of parallax is more apparent.

And interestingly, about 10% of the population doesn't register R/L shift at all, so it adds nothing to their depth perception.

Yes jannis, I have seen that too. Seems to only happen a few times when I first start using it, and then doesn't again. Also only seen it happen on one machine of two I've tried it on (oddly the faster one).

This plugin I believe is using an older version of the Rift SDK; updating may fix it but not sure what's required to do that.

@Herbst: there are two different "OculusPlugin.dll" files in the zip file, one in the base folder, and another (newer) down in the plugins\DevicesOVRDevice\bin\Dynamic folder. Wasup wid dat? (;^}) Thanks!

Thanks guys. I think this is a really funny behaviour that the Oculus stabelizes after many hickups after starting the patch. So we all encounter the same problem. It was not so bad when I started patching but as the patch got heavier, the disconnection problem occured more often. It stabelizes, but not to a degree that makes me truly happy. Shouldn't disconnect after all :-)
Or only once a week :-) I think it's worth updating the SDK especially if it's not that big of a deal. I tried with 2 Oculus set's and 2 PC's with different setups, various vvvv beta's, the disconnection occured on all systems.
Let's update :-)

Hello,

thanks herbst and mediadog.

Did anyone got this working for DK2 / Oculus SDK 0.4 already?
I tried briefly but did not get any tracking output.

cool.

By the way, is there some general guideline converting Unity classes to vvvv?

Hi TidensBarn

Thanks for the update!

Did you get anywhere with getting the rest of the info out?

With which version of vvvv and OculusSDK is last plugin working? I'm using vvvv 32 and 0.4.2 oculus sdk and the OVRDevice node is always red

EDIT: It's working now. I missed some visual studio libraries

Yes, it appears the Rift SDK is using a different coordinate system than vvvv, or at least than the DK1 (or this plugin is not handling it the same). I made some hacks to get the rotations and position to work in the "proper" direction.

I also made some changes to fix the stereo eye offset once again, and also this plugin in already reporting the interocular distance of a single eye so I removed the divide-by-2.

What I did here is a total kluge, and I think the distortions, aberration, resolution, etc. still need fixing but hey it works! Thanks TidesBarn!

Now how to attach a patch here, without making a whole new download...?

added my current version with a small test scene.
not sure if this is helpful, but worked quite well here already.
start with OculusRiftDK2-ROOT.v4p

hey mrboni,

i just took what tidensbarn came up with (thanks!) and tried to correct the orientation problem that sonostrano mentioned by tweaking.

what i got is most probably not the most optimal solution and should not be considered final, as slight derivations happily introduce nausea and disorientation.

so i would be interested as well how some of this works, and also
if there is a way to get direct-to-rift with 75Hz working.

https://developer.oculusvr.com/forums/viewtopic.php?f=17&t=1341
https://developer.oculusvr.com/forums/viewtopic.php?f=20&t=1378

ok, good to know that it should work.
there seems to be a problem with my nvidia driver then.
the refresh rates dropdown in monitor settings shows an empty list and
hr. inspektor offers only 50, 59, 60 frames.

Hey, is anybody having luck with the distortion mesh? When i try only this one function: hmd.CreateDistortionMesh(...) in the Plugin i get an "Index out of range" Exception. No clue what to do.. Could the problem be inside the OculusSharp.dll?

bump here, anybody got this working in direct access? anybody have idea woul would be needed?

right now, when i run oculus in direct access, the tracking and accelerometer data works, as soon as i run it in extended mode, it does not work

Same here, OVRDevice is always red. Which libraries do I miss?
@ all that got it working: which versions of v4 and DK runtime are you running?

Hi guys!
It works c oculus dk2, sdk 0.6 and vvvv 45beta34.1 x64?

I do not go out = (