Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice
  2. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  3. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Feedback Oculus Integration not working anymore

Discussion in '2020.2 Beta' started by ImpossibleRobert, Jul 13, 2020.

  1. ImpossibleRobert

    ImpossibleRobert

    Joined:
    Oct 10, 2013
    Posts:
    521
    Oculus Integration 17 requires "UnityEngine.Experimental.XR.Boundary", which cannot be found anymore in 2020.2. Did the namespace just move or is this something more elaborate? In this state testing 2020.2 doesn't make any sense to me otherwise unfortunately.
     
  2. genericusername555

    genericusername555

    Joined:
    Sep 17, 2020
    Posts:
    2
  3. jj-unity

    jj-unity

    Unity Technologies

    Joined:
    Jan 4, 2017
    Posts:
    74
    More recent versions of the Oculus integration asset have fixed this dependency. Updating to the latest version of the asset should resolve these issues.
     
    ImpossibleRobert likes this.
  4. IainMcManus

    IainMcManus

    Joined:
    Feb 9, 2017
    Posts:
    2
    Seeing the same issue with 2020.2.1f1 and Oculus Integration 23.1. Some of the OVRBoundary ones have a clean fix (the retrieval of geometry points) but not the rest. OVRBoundary.cs and similar look to still have references to UnityEngine.VR and to the Boundary class

    Rolling back the Oculus Integration to 20.1 seems to fix the issue. It has specific preprocessors for Unity version 2020.1 and up.
     
    Last edited: Jan 5, 2021
    Tibor0991 likes this.
  5. harryblack

    harryblack

    Joined:
    Dec 26, 2016
    Posts:
    19
    I am also using Unity 2020.2.1f1 and Oculus Integration v23.1 and I am also facing this issue..
    In some places I found UnityEngine.VR being used, I replaced it with UnityEngine.XR and things looked ok for that.
    But I am not able to get any replacement for UnityEngine.Experimental.XR.Boundary namespace.
    Can anyone give some suggestions here?
     
    leofight9, garretthoyos and Tibor0991 like this.
  6. garretthoyos

    garretthoyos

    Joined:
    Oct 18, 2019
    Posts:
    2
    I updated all the VR instances to XR (in the error/changed code to "using XR = UnityEngine.XR;" instead of VR.

    but this Boundary = UnityEngine.Experimental.XR.Boundary; is still giving an issue using Unity 2020.2
     
  7. cecarlsen

    cecarlsen

    Joined:
    Jun 30, 2006
    Posts:
    858
    Was this ever fixed? I am trying to get OVR Hand tracking working in any version above 2019.4 without luck. 2020.1, nope. 2021.2, nope (can't get past the Boundary reference issue). Using the latest Oculus Integration v25 (Feb 19th).
     
    IgnisIncendio likes this.
  8. DomeCreator

    DomeCreator

    Joined:
    Mar 5, 2020
    Posts:
    29
  9. LIFEtool

    LIFEtool

    Joined:
    Jun 7, 2017
    Posts:
    5
  10. sbanbury

    sbanbury

    Joined:
    Sep 8, 2019
    Posts:
    3
  11. faart

    faart

    Joined:
    Feb 21, 2014
    Posts:
    1
  12. Steamc0re

    Steamc0re

    Joined:
    Nov 24, 2014
    Posts:
    144
  13. torave

    torave

    Joined:
    Jun 27, 2019
    Posts:
    1
  14. PaulForward

    PaulForward

    Joined:
    Mar 2, 2022
    Posts:
    1
  15. barsl5

    barsl5

    Joined:
    May 5, 2018
    Posts:
    1
  16. cecarlsen

    cecarlsen

    Joined:
    Jun 30, 2006
    Posts:
    858
    I am not seeing this issue in 2020.3 with Oculus Integration 38 and 39.