C# Wrapper?

"CaliberMengsk" wrote:
Yeah, at the moment, all that's really needed is yaw, pitch, and roll. It wouldn't be a perfect implementation as you wouldn't have any of the predictive stuff, but that can be done internally in the software as well. It'd just be nice to not have to have Unity pro, since I don't have $1.5k to spend on it. (and probably won't for a very long time T_T)

Well, the sensor fusion stuff isn't that much code, it's probably portable. :) No need for me to re-implement threads and mutexes though.

After a quick look at the project from the SDK, it seems to me that the way forward would be to use something like this :

http://www.developerfusion.com/article/84338/making-usb-c-friendly/

to get the HID device then just implement the code in OVR_Wind32_HMDDevice and OVR_Win32_Sensor.

How is Unity Pro supporting the Oculus? Last I checked Unity supports JavaScript, C# but I don't believe it supports C++ so if it will have Oculus support they likely already managed the C# wrapper.

See this post for a Unity sample ...

viewtopic.php?f=37&t=204

"Sularus" wrote:
After a quick look at the project from the SDK, it seems to me that the way forward would be to use something like this :

http://www.developerfusion.com/article/84338/making-usb-c-friendly/

to get the HID device then just implement the code in OVR_Wind32_HMDDevice and OVR_Win32_Sensor.

I found this on github: https://github.com/mikeobrien/HidLibrar ... Methods.cs

Which imports the native HID interface into C#. I'll need to do something similar to import the GDI stuff (enumerating displays). Unless someone knows of another library that's already done it. :)

So, it doesn't do anything yet other than enumerate HID and Display devices, but here's the project so far. I can run the console app in the debugger and hover over the device lists, and they appear to contain descriptions of my devices. :)

Thanks for all the help Entroper. I would help, but like I said, I know practically nothing about c++, and even less about making a wrapper. I'll just work on the other end, the program to transfer data back and forth. Hopefully we can get this up and running soon. T_T Just sad I can't test it until I get my rift XD.

Alright, I got the necessary Win32 calls marshaled over. I should be able to start building HMDDevice descriptions next. I don't know that I'm going to follow the factory/visitor pattern that they used; it seems so much easier to make an IEnumerable. :)

The plus is, this is for us. :P So make it however you would like. Personally, I've been reading that a fair amount of people don't like how the rift outputs data. If we find a better way to do it that more people like, then they can implement it in the sdk so everyone can use it easier.

Did you happen to get any farther with it over the weekend? I got the pipeline system working pretty good at this point. I need to do a few error checks on the c# end, and I also need to do some force stops on the unity end. (It's not stopping the thread when you hit the play button to stop the game, so when you start the game a second time, unity freezes. Don't know how easy this will be to fix. May have to somehow use the C# program to somehow force close the thread somehow.)

It sends data extremely fast on my system. I was getting around 7,500 data sends per second when not screen recording. While screen recording, I was still getting over 5,000 data sends per second, so pretty darn fast since generally speaking we only really "need" 60 or so. Unity is working a lot better with threading then I thought it would. A few quirks (like not stopping the thread on close) but meh.

I'm hoping this ends up working like I intend it to, and works fast enough to actually use. Getting unity to work with it for free, even in a jenky hacky way still let's people not have to buy the $1500 to get pro. (mainly effecting me, as I don't have the money even if I wanted, and just "figured" that the rift would just work like a joystick or something, not require a full sdk built specifically for each different game and engine. Just doesn't seem that... useable from a developer standpoint as it is.)

Nah, I've been holding off working on it until my Rift arrives. Should be tomorrow. I'm also kicking around ideas of what I want to do with it once I have it ported over. I have an itch for something using either vector (wireframe) graphics or flat-shaded polygons, as a throwback to some of the first 3D games from 20 years ago.