Forum Discussion
Solved
The name 'Boundary' does not exist in the current context
Dear Developer,
After installing the Oculus Integration in Unity version 202.1.1.7 i received the error message:
Library\PackageCache\io.extendreality.zinnia.unity@1.14.1\Runtime\Tracking\CameraRig\Operation\Extraction\PlayAreaDimensionsExtractor.cs(49,17): error CS0103: The name 'Boundary' does not exist in the current context"
I have inserted these lines of code in the Manifest JSON file:
"scopedRegistries": [{"name": "npmjs","url": "https://registry.npmjs.org/","scopes": ["io.extendreality"]}],
"io.extendreality.vrtk.prefabs": "1.1.11",
I am stuck now, what went wrong? what is the solution ?
Regards
Gerard
Just found the cause myself.
I had used an old installation document "Oculus Quest WorkFlow". In the Manifest JSON file i had filled in the code line mentioned in the document.
The correct code line is : "io.extendreality.zinnia.unity": "1.36.0",
2 Replies
Replies have been turned off for this discussion
Just found the cause myself.
I had used an old installation document "Oculus Quest WorkFlow". In the Manifest JSON file i had filled in the code line mentioned in the document.
The correct code line is : "io.extendreality.zinnia.unity": "1.36.0",
Your solution got rid of the problem I had with with "Boundary" I ran across while trying one of the Unity VRTK tutorials, but I suddenly had a slew of new problems, particularly with missing "tilia" namespaces. But the format of the line you recommended I add to my manifest.json file led me to search for other similar lines to add, and I found these two:
- "io.extendreality.tilia.interactions.interactables.unity": "1.24.2",
- "io.extendreality.tilia.interactions.snapzone.unity": "1.7.2",That solved all of my namespace problems. 😄 BUT, now I have a few dozen "missing prefabs". 🙄 At least I'm a little smarter now about the possibilities with the manifest thanks to you. 😊
