Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0p1
Issue ID
970469
Regression
No
Unity crashes when playing a scene with two instances of MotionControllerVisualizer.cs at MonoBehaviour_CUSTOM_IsObjectMonoBehav
Steps to reproduce:
1. Open the attached project(ControllersRepro.zip)
2. Open the Main.unity scene
3. Play the scene (Make sure that a Mixed Reality device is connected)
4. Observe the crash
Actual results: Unity crashes
Expected results: Unity should not crash
Reproduced with: 2017.2.1p2, 2017.3.0p2, 2018.1.0b3, 2018.2.0a1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
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.