Search Issue Tracker
By Design
Votes
0
Found in [Package]
13.1.4
Issue ID
1394549
Regression
No
Mesh combined and created with Burst Jobs result in vertex input description not matching input layout
Reproduction steps:
1. Open project "LightmapsBakedMesh.zip"
2. Open Project Settings window from Edit > Project Settings
3. Navigate to Player Settings and turn on "Optimize Mesh"
4. Open Build Settings window from File > Build Settings
5. Build the project then launch it from Render Docs
6. Select DrawIndexedInstance and go to Pipeline Status
7. Observe Buffers
Expected result: There are only 2 buffers
Actual result: There are 3 buffers
Reproducible with: 10.8.1 (2020.3.26f1), 12.1.3 (2021.2.8f1), 13.1.4 (2022.1.0b3), 13.1.2 (2022.2.0a1)
Could not test with: 2019.4.34f1 (Project compilation issues)
Note:
- Tested on Windows
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Closing 'by design' - the issue comes from not having lighting baked/assigned causing the mesh optimiser to strip unused UV channels. At run time those channels, while declared for the shader, are pointed at existing data but the data is unused. The same is true of the additional buffer; the shader input expects it, but as it is unused the data is striped and at runtime a dummy buffer is created to keep the API happy.