Editor 2017.2 compilation issues
See original GitHub issueHi,
I got a HoloLens for a research project at school. I have downloaded a Toolkit here. I am on Unity 2017.2.0b3. I believe I set everything right… But at my console, I am getting this error, only this one.
Assets/HoloToolkit-Examples/SpatialUnderstanding/SpatialUnderstanding-FeatureOverview/Scripts/SpaceVisualizer.cs(8,22): error CS0234: The type or namespace name WSA' does not exist in the namespace
UnityEngine.VR’. Are you missing an assembly reference?
I googled for the issue. I couldn’t solve the problem. Any idea?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Editor 2017.2 compilation issues #790
Hi, I got a HoloLens for a research project at school. I have downloaded a Toolkit here. I am on Unity 2017.2.0b3.
Read more >Upgrading from 2017.1 to 2017.2, compilation errors "The ...
I upgraded to 2017.2. IT's working fine in the holographics emulator via Unity editor. But when I try to Build the project and...
Read more >[Editor] Compilation error in the editor code after a failed ...
Assets/Code/Imagine/Editor-Tools/Build.cs(3,7): error CS0246: The type or ... Reproduced with: 5.6.1p1, 5.6.2f1, 2017.1.0b10, 2017.2.0a4.
Read more >Packages folder scanned by Editor causing compilation errors
Packages folder scanned by Editor causing compilation errors ... Reproduced in 2017.2.0b4, 2017.2.0b5, 2017.2.0b6, 2017.3.0a2
Read more >Compilation error
I´m getting this error with Playmaker 1.8.5 and Unity 5.6.3, 2017.1 and 2017.2. Code: [Select]. 2>Assets\PlayMaker\Editor\FsmComponentInspector ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Unity has changed that namespace from
UnityEngine.VR
toUnityEngine.XR
. Everything under the namespace should be the same, from my experience!The namespace change is one part of it. Some of the handlers have changed in the SDK as well. This resolves about 90% of the issues.