Search Issue Tracker
By Design
Votes
0
Found in
4.5.5f1
Issue ID
658358
Regression
No
[MeshRenderer] Mesh cannot be accessed when running not in editor if the gameObject was instantiated from a fbx model.
To Reproduce:
1. Run the attached project in editor, observe that the collider on 'tank2_collider' is generated correctly from the sharedMesh in the MeshFilter from the tank2_collider gameobject (script TestScene.cs).
2. Build the project to iOS or standalone, notice that the collider is not generated because this error
'CollisionMeshData couldn't be created because the mesh has been marked as non-accessible'
is thrown, when trying to access the mesh which is used to generate the MeshCollider.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment