Search Issue Tracker
Third Party Issue
Third Party Issue in 6000.0.X
Votes
0
Found in
2021.3.37f1
2022.3.23f1
2023.2.17f1
6000.0.0b14
Issue ID
UUM-69181
Regression
No
Dynamic colliders of GameObject with Rigidbody component become undetectable when another GameObject's position coordinates are about 1e8
How to reproduce:
1. Open the “PhysicsOverlapBugRepro2022” project
2. Open the “SampleScene”
3. Enter the PlayMode
4. Open the Scene View and select the orientation view along the Z axis
5. Select the “OBJECT” GameObject in the Hierarchy
6. Change its position to the (1e8, -1e8, 0)
7. Select the “OVERLAPPER” GameObject in the Hierarchy
8. In the Inspector, expand “Overlaps Sphere”, “Overlaps Capsule”, and “Overlaps Box” Lists of the Overlap Detector (Script)
9. Navigate the “OVERLAPPER” GameObject to cross the red cube by using Move Tool
10. Take a note of the Elements (colliders) that appear in the Lists in the Inspector
11. Navigate the “OVERLAPPER” to cross the yellow cube by using Move Tool
12. Take a note of the Elements (colliders) that appear in the Lists in the Inspector
Expected result: The number of appearing Elements (colliders) is the same for both yellow and red cube
Actual result: “OVERLAPPER” GameObject does not detect some of the yellow cube’s colliders
Reproducible in: 2021.3.37f1, 2022.3.23f1, 2023.2.17f1, 6000.0.0b14
Reproduced on: Windows 10
Not reproduced on: No other environments tested
Note: Reproducible in Player
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Unfortunately, this is how the spatial search structures are built in PhysX and we are unlikely to be able to change that. Perhaps the only workaround would be to have a script that watches glitchy objects and tries detect issues before they happen.
Resolution Note (6000.0.X):
Unfortunately, this is how the spatial search structures are built in PhysX and we are unlikely to be able to change that. Perhaps the only workaround would be to have a script that watches glitchy objects and tries detect issues before they happen.