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
- Crash on __pthread_kill when initializing Vuplex WebView while entering the Play Mode
- Crash on FindSurface when adding a custom Renderer Feature to a 2D Renderer Data Asset
- [Android] [Vulkan] [UI Toolkit] Application crashes when the device is rotated when it has UI Toolkit TextField on Vulkan devices
- Crash on DualThreadAllocator<DynamicHeapAllocator>::TryDeallocate when opening a specific project
- Crash on memset_repstos when pressing a UI button while in Play Mode
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.