Forum Discussion
Node FFI bindings to the 0.3.1 SDK
https://github.com/wwwtyro/node-ovrsdk
It includes a small example of acquiring the orientation from the rift and printing it to the console.
It's not by any means feature-complete, but it's enough to get started (I used it to build this billiards game).
Let me know if you have any issues with it, or even better, if you make something with it.
I hope to post a hello world tutorial using this, node webkit, and THREE.js within the next few days.
It includes a small example of acquiring the orientation from the rift and printing it to the console.
It's not by any means feature-complete, but it's enough to get started (I used it to build this billiards game).
Let me know if you have any issues with it, or even better, if you make something with it.
I hope to post a hello world tutorial using this, node webkit, and THREE.js within the next few days.
2 Replies
- I would be wary of applying an public domain license to JS that is based on the Oculus SDK headers. It may constitute a derived work and therefore have to be under the Oculus SDK license.
- Yes, jherico is correct. If your software is a "derivative work" based primarily on the Oculus SDK source code, then you must retain the Oculus SDK License.
Please see the full legal copy here:
https://developer.oculus.com/license
