Search Issue Tracker
Fixed in 2018.1.X
Votes
1
Found in
2017.2.0f3
Issue ID
969710
Regression
No
Editor is crashing or throwing the System.Runtime.InteropServices.COMException exception when using Remote to Device
Steps to reproduce:
1. Open the attached project
2. Open the MainScene.unity scene
3. Navigate to Window > Holographic Emulation and select Remote to Device as the Emulation Mode
4. Enter the HoloLens IP address in the Remote Machine field
5. Click the Connect button
6. Play the app
7. Stop the app
8. Observe the crash or error is thrown
Actual Behavior: Unity editor crashes or error is thrown
Expected Behavior: Unity editor properly stops playing the scene
Note:
Crash is not 100% reproducible
Most easily reproducible with 2017.2.0f3
Unable to reproduce with 2017.1.2p4, via errors
Reproduced with: 2017.2.0f3, 2017.2.0p2 MRTP5, 2017.2.1f1, 2017.3.0f2, 2018.1.0a7
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 2018.1):
The exception occurs because there is a missing or out of date driver for SpaceNavigator. The driver can be found here: https://www.3dconnexion.com/service/drivers.html