Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.3.9 - Physics
Issue ID
ECSB-1534
Regression
No
Physics Shape incorrectly generates collision edges when the Geometry is of 32-bit Index Format and contains more than 16-bits number of vertices
How to reproduce:
1. Open the “dots-bug.zip“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Observe the Game view
Expected result: All Cubes collide with the mountainous geometry
Actual result: One Cube on the right falls through the Geometry (32-bit)
Reproducible in: 1.2.4, 1.3.9 (2022.3.58f1, 6000.0.39f1, 6000.1.0b7, 6000.2.0a4)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- The geometry has 6.4 million vertices
- Not reproducible with a low number of vertices 32-bit geometry (i.e. Cube) (There have to be more than 65536 vertices in the geometry)
- There is one area that has collision
- Without having selected any of the meshes, in the Scene view you can see the collide-able area in green
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
- Shader Graph Create Node window cannot be resized or moved after maximizing and reopening it
- [Usability] Cannot toggle Scene checkboxes using TAB/Enter in Build Profiles’ > Open Scene List
- Installing HDRP package throws Shader Graph validation warning about Exposure node when installed in Universal 3D Template
- ShaderGraph “Create Node” menu’s resize icon overlaps with the menu's scrollbar
- ShaderGraph “Create Node” menu’s Search bar's typing cursor is barely visible since it's black on a dark background
Resolution Note:
There are no fixes planned for this Bug