Search Issue Tracker
Not Reproducible
Votes
0
Found in
2022.2.0b12
2023.1.0a14
Issue ID
UUM-18796
Regression
Yes
OnTriggerEnter method does not call when project is opened in a later version of the editor
Reproduction steps:
# Open the user’s attached project (“Mail Most.zip”)
# Open the “PlayerController” and “PlayerScene” scenes Additively
# Find the “TestLookSpatialInteractable” GameObject in the scene and observe its BoxCollider Component
# Enter Play Mode
# Move the “FirstPersonPlayer” GameObject to hit the “TestLookSpatialInteractable” GameObject
# Track down any Debug messages in the console
Expected result: Console prints “FirstPersonPlayer Entered” message
Actual result: The OnTriggerEnter method does not call
Reproducible with: 2022.2.0a11, 2022.2.0b12, 2023.1.0a14
Not Reproducible with: 2020.3.40f1, 2021.3.11f1 , 2022.1.20f1, 2022.2.0a10
Reproducible on: Intel macOS 12.6
Note: A message (“FirstPersonPlayer Entered”) is expected to be printed in the Console if the "FirstPersonPlayer" collides with the "TestLookSpatialInteractable" GameObject via its Trigger Collider and script ("SpatialInteractible.cs").
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
this is a behavior change introduced by third party library upgrade ( ie physx upgrade)
could not reproduce the exact failure on a fresh project