Search Issue Tracker
Feature Request
Feature Request in 2023.2.X
Votes
2
Found in
2021.3.5f1
2022.1.5f1
2022.2.0a17
2023.1.0a1
2023.2.0a1
Issue ID
UUM-6988
Regression
No
Mesh.GetIndexBuffer() requires Mesh's 'Read/Write' flag to be enabled to get its index buffer data in Builds
Reproduction steps:
1. Open the attached 'GetIndexBuffer' project
2. Open the 'SampleScene'
3. Observe the 'Assets\Body mesh.fbx' model in the Inspector
4. In the 'Model' section toggle off the 'Read/Write' checkbox
5. Go to the 'File -> Build and Run'
6. In the build click on the 'Open Log File'
Expected result: 'GPU GetIndexBuffer (GraphicsBuffer) = 5904' is logged, index buffer data is accessible
Actual result: 'GPU GetIndexBuffer (GraphicsBuffer) = 0' is logged, no index buffer data can be retrieved
Reproducible with: 2021.3.5f1, 2022.1.5f1, 2022.2.0a17, 2023.1.0a1
Could not test with: 2020.3.35f1 (Compile errors)
Note:
- The issue is not reproducible in the Editor
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
- Some Material Overrides are viewed as broken when using the Shadergraph CustomLighting package sample
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
Resolution Note:
Current API has the expectation the buffer target is changed before the Mesh is created and the CPU data is discarded. Feature work is required to modernize this API and allow for more flexibility. This case is closed and moved to internal feature tracking.
Resolution Note (2023.2.X):
Current API has the expectation the buffer target is changed before the Mesh is created and the CPU data is discarded. Feature work is required to modernize this API and allow for more flexibility. This case is closed and moved to internal feature tracking.