Forum Discussion

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

Other new stuff in v0.2.2 integration

Haven't actually used it yet, but poked around in the code and found a couple interesting things not mentioned in release notes (as far as I could tell):

Headtracking orientation appears to now be officially shared across multiple OVRCameraControllers. Woo hoo!

OVR.GetOrientation()/GetPredictedOrientation() both now accept a sensor # argument. Right now the integration code only uses 0 here, but this seems to imply support for multiple sensors are coming up. What other sensors could this refer to?

4 Replies

Replies have been turned off for this discussion
  • drash's avatar
    drash
    Heroic Explorer
    12 years ago
    Also, I noticed that 0.2.2 integration's OVRMessenger.cs is using the "advanced c# messenger". There are four "Callback" delegates that have the potential to clash with the same messenger functionality in other Unity packages. If that happens, the dev will get "The namespace 'global::' already contains a definition for 'Callback'" errors.

    So if the license makes it possible, I would suggest renaming the four Callback delegates in OVRMessenger.cs to something that's less likely to clash, such as CallbackOVR or something. (I'm renaming the callback delegates in my other asset packages in this case in order to keep the OVR integration hack-free as possible).
  • petergiokaris's avatar
    petergiokaris
    Protege
    12 years ago
    Thanks for catching the potential clash with the Callback delegates!

    I am renaming them to OVRCallback and this will be part of a small bug-fix to 0.2.2 that I plan to release later this week.

    Best,
    Peter
  • Anonymous's avatar
    Anonymous
    12 years ago
    Hello,
    I'm getting an issue that seems to relate... Imported a set of scripts called cameraPath2.

    Assets/OVR/Scripts/OVRMessenger.cs(50,22): error CS0101: The namespace `global::' already contains a definition for `Callback'

    Is it related?
    Thanks!
  • drash's avatar
    drash
    Heroic Explorer
    12 years ago
    Definitely related HeadTrip! I had my problem because of CameraPath also :) Both OVR and CameraPath make use of the same messaging script, so you'll just have to rename the callback delegates in one of them (probably best to rename the CameraPath ones).

    All I did to work around it was rename all instances of "Callback" in CameraPathEvent.cs to "CallbackCP".