Search Issue Tracker
Fixed
Fixed in 2021.3.54f1, 2022.3.64f1, 6000.0.52f1, 6000.1.9f1, 6000.2.0b7, 6000.3.0a1
Votes
0
Found in
2021.3.51f1
2022.3.62f1
6000.0.49f1
6000.1.3f1
6000.2.0b1
6000.3.0a1
Issue ID
UUM-105001
Regression
No
A vertex stream with a stride of 1 is bound to the GPU in Player when mesh is compressed
How to reproduce:
1. Open the attached “IN-101335” project
2. Select “File → Build Settings… → Build”
3. Open the RenderDoc graphics debugger software
4. In the “Launch Application” tab of RenderDoc, set the “Executable Path” field to the built project’s path (…/Build/Simple 3D project.exe)
5. Ensure the “Enable API Validation” checkbox is ticked
6. Select “Launch”
7. Select “Capture Frame(s) Immediately”
8. Double-click the capture to open it
9. Observe the bottom of the window
Expected result: No error messages appear
Actual result: A “Simple 3D Project_…. Capture has 4 issues. 4 unread” message appears. Double-clicking this message reveals a “ID3D11DeviceContext::DrawIndexed: Vertex Buffer Stride (1) at the input vertex slot 2 is not aligned properly. “ error message
Reproducible with: 2021.3.51f1, 2022.1.0a1, 2022.3.62f1, 6000.0.49f1, 6000.1.3f1, 6000.2.0b1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Double-clicking the “DeviceContext::DrawIndexed: Vertex Buffer Stride (1) at the input vertex slot 2 is not aligned properly. “ error shows where the error originated. Expanding the “IASetVertexBuffers” foldout and then the “pStrides” foldout in the API inspector window shows that the second element in the array is set to 1.
- RenderDoc can be downloaded here: https://renderdoc.org/
- Reproducible using Direct3D11
- The error message does not appear in Direct3D12 or Vulkan
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Add comment