Search Issue Tracker
Third Party Issue
Votes
0
Found in
2022.3.60f1
6000.0.42f1
6000.1.0b10
6000.2.0a6
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-100210
Regression
No
Rigidbodies clip through terrain and snap back up when Heightmap Resolution is bigger than the terrain size
How to reproduce:
1. Open the attached “IN-96728” project
2. Open the “SampleScene” Scene
3. Enter Play mode
4. Observe the Game window
Expected result: The Capsule GameObject does not clip through the terrain
Actual result: The Capsule GameObject quickly clips through the terrain and then snaps back upwards when colliding with the terrain
Reproducible with: 2022.3.60f1, 6000.0.42f1, 6000.1.0b10, 6000.2.0a6
Reproducible on: Windows 10 (User), Windows 11
Not reproducible on: No other environments tested
Note: To reproduce in the 2022.3.60f1 version untick the X, Y, Z boxes in the Capsule GameObject Inspector window “Freeze Rotation” option
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
- Query Builder items display raw code style names instead of human readable labels in search field
- “+” button does nothing and has no functionality when clicked in Human Template "Bone Template" list
- Solid gray or black areas are present when using ShaderGraph with Custom Function nodes without manual reimport
- The Multiplayer Play mode tool doesn't see the list of Play Mode scenarios when using 6000.3.x
- Input field does not update when selecting the same input field after previous input was canceled
Resolution Note:
The issue is internal to the PhysX SDK, currently we are no longer modifying the PhysX 4 sdk logic.
The issue is by design from the physx sdk perspective, but we'll be taking a look at this as a internal ticket going forward.