Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.56f1
6000.1.16f1
6000.2.2f1
6000.3.0a6
6000.4.0a1
6000.5.0a1
Issue ID
UUM-115754
Regression
No
Inconsistent behaviour for Physics.ContactModifyEvent
Reproduction steps:
1. Open the attached “IN-113784_ContactModification.zip“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter the Play Mode
4. Observe the Scene View
Expected result: All spheres pass through respective surfaces
Actual result: The “Rigidbody + non-kinematic rigidbody” sphere fails to pass through the pan
Reproducible with: 6000.0.56f1, 6000.1.16f1, 6000.2.2f1, 6000.3.0a6
Reproducible on: M1 Max MacOS 15.5 (Tested by CQA)
Not reproducible on: No other environment tested
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
- Points Lights are getting culled prematurely when using Forward+ and Deferred+ rendering paths
- Search's Indexing settings in the Preferences window are not searchable
- Crash on block_locate_free when opening a specific project
- "Project connected" pop opens again after closing it
- Cloud Code Authoring logs "JsAssetHandler:OpenAsset (int,int) does not match any of [OnOpenAssetAttribute] expected signatures" when opening or switching scenes and having the Deployment Package Installed
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
additional info:
Based on the provided reproduction case, one thing that needs to be understood for rigidbody x rigidbody pairs is that either pair.colliderEntityId or pair.otherColliderEntityId can be the collider you are using to filter with.
if(pair.colliderEntityId == m_TrackedColId || pair.otherColliderEntityId == m_TrackedColId)
{
//either of the ids is the tracked id, execute whatever modification is required.
}
Cheers,
AlexRvn.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
additional info:
Based on the provided reproduction case, one thing that needs to be understood for rigidbody x rigidbody pairs is that either pair.colliderEntityId or pair.otherColliderEntityId can be the collider you are using to filter with.
if(pair.colliderEntityId == m_TrackedColId || pair.otherColliderEntityId == m_TrackedColId)
{
//either of the ids is the tracked id, execute whatever modification is required.
}
Cheers,
AlexRvn.