Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.2.1p2
Issue ID
990611
Regression
No
[Hololens] [Vuforia] Unity Crashed when running Holographic Emulation on Device with Vuforia
How to reproduce:
1. Download attached project file and open "Main" Scene
2. In Assets folder go to Resources and select VuforiaConfiguration
3. Change Digital Eyewear to "Optical See-through" and See Through Config to "Hololens"
4. Connect to Hololens via Holographics
5. Enter Play Mode
6. Exit Play Mode
7. Attempt to disconnect from Hololens via Holographic Emulation tab
Actual result: Unity crash without stackttrace. Crash in winutils::ProcessInternalCrash(PEXCEPTION_POINTERS pExInfo)
Reproduced with: 2017.2.1p2, 2017.3.0p3
Note: if you have an external webcam, Unity crash on Play because of 973326 issue (only on 2017.2)
-
Mortalyx
Mar 12, 2018 15:30
And also you should set Digital Eyewear to hololens
Screen from Unity 2017.3.1p2
https://cl.ly/1k371E1n173t -
YoctoYury
Mar 05, 2018 14:49
I had the same result until change some configuration settings in Vuforia and Publishing (in Player settings). What i do: disable Vuforia video background, uncheck pose tracker in configurations, check next things in publishing settings:
InternetClientServer
PrivateNetworkClientServer
Microphone
SpatialPerceptionBut all this things will not let you use emulator if Vuforia behaviour is enabled. When you check this component the camera becomes unmovable. I created bug-report for that thinglast friday and waiting for confirmation
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] "Error while reading movie" errors are thrown when opening templates
- Standalone profiler process is hidden in macOS dock
- Shader warnings are being thrown after building Mixed Reality Template
- Error is thrown when entering play mode with build profiles docked and standalone profiler open
- The Player hangs when activating another maximized application
Resolution Note (2018.2.X):
XR Management has evaluated this issue and determined that it does not meet our current bug severity threshold. If you would like your issue to be reviewed again, please re-submit your bug.