Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
Anonymous's avatar
Anonymous
10 years ago

Errors in Oculus Unity Developer Guide

Hi,

I have recently started getting into developing some simple applications for the Oculus Rift, and I have found the Developer Guide included in the Documentation folder of the Unity integrations to contain some misleading errors:


    - Some of the public members listed in Table 2 are not present (e.g. Use Rotation Tracking)
    - Migrating From Earlier Versions: This section has had the same list of changes in it since v0.4.3; can this be updated?


Are these just a result of copy-pasting from previous versions? If so which version of the SDK included the 'Use Rotation Tracking' feature?

Thanks!!

5 Replies

Replies have been turned off for this discussion
  • Anonymous's avatar
    Anonymous
    thanks!
    I am asking mainly because I'm curious if it's possible to get position tracking but not orientation tracking data from the tracking camera. I am working on an application similar to the Roto chair that requires the tracking camera to move.
  • "PrivateBoolean" wrote:
    I'm curious if it's possible to get position tracking but not orientation tracking data from the tracking camera.

    You can ignore rotation data by filtering the tracking pose in your own callback for the OVRCameraRig.UpdatedAnchors event. BTW, you can also change the frame of reference of tracking relative to the OVRCameraRig by changing the local position, orientation, and scale of the TrackingSpace GameObject.
  • Thanks again for bringing this to our attention - I'm making some updates to the Unity guide now.
  • Anonymous's avatar
    Anonymous
    "vrdaveb" wrote:
    You can ignore rotation data by filtering the tracking pose in your own callback for the OVRCameraRig.UpdatedAnchors event.


    Sorry I wasn't clear. I meant to ask if it is possible to use the position data from the camera combined with the orientation data from the IMU in the HMD (While ignoring the optically-corrected orientation data from the camera). My reasoning is that I am working on a moving installation where users can rotate themselves in real space, similar to http://www.rotovr.com/.