Search Issue Tracker
Duplicate
Votes
0
Found in
4.3.0b1
Issue ID
567383
Regression
No
-e Collision not detected
To Reproduce:
1. Open the attached project and press play.
2. The object will fall unit it collides.
3. Notice the collision is detected at time 0.62, but the object collided at time 0.61 as well.
Why was the collision not detected?
(Submitted by Ricardo, Support ticket 00135467)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
This is a duplicate of issue #443969