No warning is thrown when a non-readable mesh is assigned

Unity: Mesh

As Designed

2023.2.X

2023.1.X

2022.3.X

2021.3.X

The objects that cause the warning are marked as static. Furthermore static batching is enabled in the project. At build time the marked meshes are batched together. The resulting mesh has r/w disabled and thereby triggers the exceptions at runtime. Disabling static batching results in the no errors. Please file a feature request on our product board if you'd like to see us make improvements to the read/write behavior: https://portal.productboard.com/8ufdwj59ehtmsvxenjumxo82/c/452-didn-t-find-what-you-were-looking-for?utm_medium=social&utm_source=portal_share

How to reproduce:
1. Open the "IN_44940" project
2. Press File -> Build And Run
3. Observe the Console

Expected result: warning about Mesh being marked as non-readable is thrown before or after Build And Run is pressed
Actual result: no warning about Mesh being marked as non-readable is thrown

Reproducible with: 2021.3.27f1, 2022.3.3f1, 2023.1.1f1, 2023.2.0a20

Reproducible on: Windows 10 Pro

Note: this warning is needed for build since Meshes are not readable when built on Android, Windows Standalone and WebGL (everything works in the Play Mode)

Workaround: in the Player, the error is thrown regarding Mesh not being marked as readable so following provided steps in the Editor the issue can be easily fixed

Error message: “InvalidOperationException: Not allowed to access vertex data on mesh 'BendPlank' (isReadable is false; Read/Write must be enabled in import settings)”

No warning is thrown when a non-readable mesh is assigned

Unity: Mesh

As Designed

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

No warning is thrown when a non-readable mesh is assigned

Unity: Mesh

Statuses

As Designed

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?