Search Issue Tracker
Fixed in 2021.2.X
Votes
1
Found in
2017.3.1p2
Issue ID
1006742
Regression
No
Editor crashes when access to RaycastHit.textureCoord2 ( collider is meshCollider and Mesh.isReadable=false )
Editor crashes when access to "RaycastHit.textureCoord2".
1. Create GameObject with MeshCollider from AssetBundle.
( "MeshCollider.sharedMesh.isReadable == false" <- this is the crash reason.)
2. call Physics.Raycast and access to the result "RaycastHit.textureCoord2" then Editor will be crashed.
This crash is happened only on Editor.
Not Reproduced on player( windows exe / android apk).
Reproduced with : 5.6.0f3 / 2017.3.1p2 / 2018.1.0b8 ( Windows 10)
Comments (2)
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
- “Frame Debugger On” text color not maintained across different Editor Themes in toolbar
- Rendering artefacts appear in the Game view window when maximizing/minimizing Inspector window and Frame Debugger is Enabled
- [MacOS] AdvancedDropdown in the Profiler is not scrollable even when not all options in the list are visible
- Memory leak when a lot of Particle Systems instantiated while Profiler is open
- "ArgumentOutOfRangeException" error is thrown when trying to delete letters from an RTL TextField when using the Advanced Text Generator
Raccoon009
Dec 17, 2020 19:37
Try using this methods before assigning mesh to collider
colliderMesh.RecalculateBounds();
colliderMesh.RecalculateNormals();
colliderMesh.RecalculateTangents();
TC_FS
Jan 20, 2020 10:21
This accours not only in editor, but also in standalone builds (seen on windows) with Unity 2019.2
Is there any progress for a fix?
For us it happens when raycasting a mesh created via SkinnedMeshRenderer.BakeMesh