This MeshCollider requires the mesh to be marked as readable.

[Bastienre4]

Hello.

We updated our project from 2019.2.8f1 to 2019.3.0b10. Unfortunatly, all our scenes seem to have broken MeshColliders because of this:

Ticking the Read/Write enabled on the asset fix the issue, but it would take forever to go in all our scenes to fix every meshs. Also, it takes 2x more memory.
If we tick Generate collider on the asset, it seem to be better but again, it would take a very long time to go on all concerned assets and fix this manually. Also, it add a collider by default, which is not optimal for us (we have a specific prefab workflow, and the first prefab variant from the asset should not have any collider on it).

Any ideas on how to fix this? Any ideas why this bug appeared?

PS : A while ago I tried to update around the b6, and the issue was also there.

Thanks and have a nice day.

[Bastienre4]

Up!

[Peter77]

This is a known issue, please see:

Upgrading to 2019.3 results in all MeshColliders requiring readable on mesh

Moving from 2019.2 to .3 is a lot more difficult than I’d imagine for a point release. But I’ve worked through most of the issues. The last big one remaining is that every single MeshCollider in the project is reporting this sort of error: This MeshCollider (GameObject: 'Bridge_Support_Sm (11)' Mesh: 'Bridge_Support_Sm') requires the mesh to be marked as readable in order to be usable with the given transform. That’s thousands of MeshColliders. I presume this is a bug, as the only r…

[Bastienre4]

Ok thanks for the link