Search Issue Tracker
Not Reproducible
Not Reproducible in 2023.1.X
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
- GameObjects change Hierarchy order when undoing adding Component to multiple GameObjects
- [macOS] Editor crashes after entering Play mode with overlapping GameObjects with Cloth Component and Cloth Inter-Collision enabled
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
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
Resolution Note (2023.1.X):
this is a behavior change introduced by third party library upgrade ( ie physx upgrade)
could not reproduce the exact failure on a fresh project