Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.0.0
Issue ID
ECSB-309
Regression
No
[DOTS] Error "Not allowed to access vertices on mesh 'SM_Prop_Crate_03'" is shown when Physics Shape authoring component has collider mesh provided
Reproduction steps:
1. Open the attached project "ReproProj"
2. Observe the Console window
Expected result: No errors are displayed in the Console window and the Physics Shape authoring component does not try to access mesh data if the mesh is already provided
Actual result: Error "Not allowed to access vertices on mesh 'SM_Prop_Crate_03' (isReadable is false; Read/Write must be enabled in import settings)" appears in the Console window
Reproducible with: 1.0.0-exp.8 (2022.2.19f1), 1.0.0-pre.65 (2022.2.19f1)
Could not test with: 0.51.1-preview.21 (2022.2.19f1) (Project is using entities graphics, and no such version for this package exists)
Reproduced on: Windows 10 Enterprise 21H2
Notes:
- The physics shape is trying to access the visual mesh even though a collider mesh is already provided. Also, this is done in the Editor so it should have access to the mesh content anyway
- This error is also seen in the Console window “Not allowed to access triangles/indices on mesh 'SM_Prop_Crate_03' (isReadable is false; Read/Write must be enabled in import settings)”
Comments (1)
-
redwyre
May 13, 2023 16:30
repro for 1.0.8: https://github.com/redwyre/UnityReproProjects/tree/master/PhysicsShapeMeshRead
but now the physics authoring is in the sample
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
There are no fixes planned for this Bug