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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
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.