Search Issue Tracker
By Design
Votes
1
Found in
2021.3.27f1
2022.3.3f1
2023.1.1f1
2023.2.0a20
Issue ID
UUM-41251
Regression
No
No warning is thrown when a non-readable mesh is assigned
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)”
Comments (1)
-
DevDunk
Jun 29, 2023 13:50
The important part for me is that this does not happen in play mode, but does in builds. This should be consistent and at least throw a warning
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
- “Baking ReferencedPrefabAuthoring!” errors are thrown when creating or deleting unrelated GameObjects in a SubScene that references prefabs
- Cannot scroll down to see all UI Builder Inspector items after content is resized
- Crash on SceneTracker::SetObjectDirty when entering Play mode on a project with specific Assets
- UI Toolkit's TextInput element does not inherit layout parameters from the TextField element when TextField.multiline is true
- The TileMap grid in the Tile Palette is not visible when Screen Space Ambient Occlusion is enabled
Resolution Note:
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