Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
2
Found in
2020.3
2020.3.4f1
2021.1
2021.2
Issue ID
1330299
Regression
No
"Can't recalculate bounds <...>" warnings on Mesh.SetSubmeshes using NativeArray with DontRecalculateBounds flag
Reproduction steps:
1. Open attached project "MeshWarning.zip" and scene "SampleScene"
2. Enter Play Mode
3. Observe Console window
Expected result: No warnings
Actual result: "Can't recalculate bounds of a mesh that does not have Float3 position format" and "Can't recalculate bounds of a sub-mesh that does not have Float3 position format" warnings
Reproducible with: 2020.3.7f1, 2021.1.6f1, 2021.2.0a16
Could not test with: 2018.4.34f1, 2019.4.25f1 ('Mesh' does not contain a definition for 'SetSubMeshes' error)
Note:
This issue does not reproduce when using a List
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a19
Resolution Note (fix version 2021.1):
Fixed in 2021.1.11f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.13f1