Setup guide

36 | Migrating From Earlier Versions | Unity
Migrating From Earlier Versions
The 0.4.3+ Unity Integration’s API is significantly different from prior versions. This section will help you upgrade.
For changes pertaining to Mobile SDK v 0.5, see the section at the bottom.
API Changes
The following are changes to Unity components:
Table 5: Unity Components
OVRDevice
→
OVRManager Unity foundation singleton.
OVRCameraController
→
OVRCameraRig Performs tracking and stereo rendering.
OVRCamera Removed. Use eye anchor Transforms instead.
The following are changes to helper classes:
Table 6: Helper Classes
OVRDisplay HMD pose and rendering status.
OVRTracker Infrared tracking camera pose and status.
OVR.Hmd
→
Ovr.Hmd Pure C# wrapper for LibOVR.
The following are changes to events:
Table 7: Events
HMD added/removed Fired from OVRCameraRig.Update() on HMD connect
and disconnect.
Tracking acquired/lost Fired from OVRCameraRig.Update() when entering
and exiting camera view.
HSWDismissed Fired from OVRCameraRig.Update() when the Health
and Safety Warning is no longer visible.
Get/Set*(ref *) methods Replaced by properties.
Behavior Changes
• OVRCameraRig’s position is always the initial center eye position.
• Eye anchor Transforms are tracked in OVRCameraRig’s local space.
• OVRPlayerController’s position is always at the user’s feet.
• IPD and FOV are fully determined by profile (PC only).
• Layered rendering: multiple OVRCameraRigs are fully supported (not advised for mobile).
• OVRCameraRig.*EyeAnchor Transforms give the relevant poses.
• For OrientationOffset, set rotation on the TrackingSpace game object instead.
• FollowOrientation is no longer necessary since OVRCameraRig applies tracking in local space. You are free
to script the rig’s pose or make it a child of another GameObject.
Upgrade Procedure
To upgrade, follow these steps: