Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
5
Found in
2019.3
2019.3.0b8
2020.1
Issue ID
1197040
Regression
No
Rebuilding a mesh, using the job system to bake the collider, then setting the mesh, results in a double collider bake
To reproduce:
1) Open the attached project and scene
2) Open up Profiler, and enable Deep Profile
3) Play it, then pause it after a few frames come in
4) Select the current frame in Profiler
5) Search for sharedMesh in Hierarchy
Expected: The collider is baked once
Actual: The collider is baked twice
WORKAROUND: Do not reuse the Mesh instance for now. Every time you bake, that should be a new Mesh instance.
Reproduced in 2020.1.0a12, 2019.3.0b11, 2019.3.0a9 (when the feature was introduced)
Comments (1)
-
Marrt
Jan 05, 2020 22:00
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a5
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b4
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.10f1