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
- MSAA warnings are thrown when custom post-processing is used and the Scene contains transparent GameObjects
- Texture looks point-sampled when Mipmap Streaming is enabled
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
Resolution Note:
There are no fixes planned for this Bug