Search Issue Tracker
By Design
Votes
0
Found in
2020.3
2020.3.0f1
2021.1
2021.2
Issue ID
1321496
Regression
No
Mesh: last vertex index (e.g. 0xFFFF for 16-bit indices) makes the triangle invisible on some platforms
How to reproduce:
1. Open the user's attached "TerrainGen" project
2. Open the Scene "SampleScene"
3. Enter the Play Mode
4. Inspect a "Heightmap" GameObject's corners in the Scene view
Expected results: None of the corners have an invisible triangle
Actual results: One of the corners have an invisible triangle (the triangle that uses 0xFFFF vertex index)
Reproducible with: 2020.3.3f1, 2021.1.1f1, 2021.2.0a11
Could not test with: 2018.4.23f1, 2019.4.23f1 because of the script breaking when downgrading
Notes:
- As a workaround, you have to manually set the index format
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
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices in "com.unity3d.player.UnityPlayerActivity/2D Colour Attachement"
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
- [HDRP] Text is rendered with artefacts when using STP and resolution scale is set a float value
Resolution Note:
Max possible vertex index (i.e. 0xFFFF for 16-bit IndexFormat) is "undefined" on some graphics APIs/GPUs and makes the triangle be invisible. Will update Mesh.indexFormat docs to point this out.