Search Issue Tracker
In Progress
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X
Fix In Review for 6000.3.X
Votes
0
Found in
2022.3.18f1
6000.0.49f1
6000.1.4f1
6000.2.0b2
6000.3.0a1
7000.0.0a35
Issue ID
UUM-107356
Regression
No
Mesh Object has an invalid Indices value in a Memory Snapshot of a Player Build when the Read/Write option of the Mesh is disabled
Reproduction steps:
1. Open the attached "TestPrebakeMeshCollider" project
2. Build and Run
3. While the Build is running, go back to the Editor and open the Memory Profiler via Window -> Analysis -> Memory Profiler
4. Take a Memory Snapshot of the running Build
5. Click on the Memory Snapshot and click on Inspect of the "Top Unity Objects Categories"
6. Search for "DecorativeTeapot_01_Mesh_LOD0" and select it
7. Observe the results
Expected results: The Indices of the selected Mesh is not 0
Actual results: The Indices of the selected Mesh is 0
Reproducible with: 1.0.0-pre2 (2022.3.18f1), 1.1.0 (2022.3.18f1, 2023.2.8f1)
Could not test with: 0.7.1-preview.1 (2021.3.34f1) (Indices feature missing), 1.0.0-pre.1 (2022.3.18f1) (Indices feature missing), 1.1.0 (2023.3.0b5) (Memory Profiler hangs on "Importing Assets")
Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested
Notes:
- Only reproducible in Standalone Player
- Not reproducible when the Read/Write property of the Mesh is enabled
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Add comment