Search Issue Tracker
Fixed in 2022.2.X
Duplicate in 2020.3.X, 2021.3.X
Votes
0
Found in
2017.3
2020.3
2021.3
2022.1
2022.2
Issue ID
1417578
Regression
No
Raycast may fail after moving a lot of Game Objects
How to reproduce:
1. Open and run the attached project (PhysicsTest.zip)
2. Observe the Console and wait until the Editor pauses because of the "Debug.Break()" on line 43 of the "Test.cs" script
Expected result: The Raycast never fails and the Console keeps printing the position that the raycast hit
Actual result: After about a minute the Editor pauses and the Console prints "No ground!" indicating that a Raycast failed
Reproducible with: 2020.3.34f1, 2021.3.3f1, 2022.1.1f1, 2022.2.0a11
-
Wawwaa
Jun 28, 2024 13:06
This is not fixed in Unity 2022.3.5 and still happening!!!
-
nxtboyIII
Dec 14, 2023 16:30
Also having issues with this on Unity 2021.3.30f1
-
Zimbres
Jul 23, 2022 15:06
Tested on my game, did not fixed my issue
-
Gotmachine
Jun 18, 2022 11:58
Can anybody expand on the exact nature of this bug (sharing the reproduction project of this issue would be nice) and possible workarounds ?
I'm experiencing a similar issue with raycasts starting to randomly fail after some time, and the game involves moving many GameObjects continuously through their transform position/rotation.
Reproduced in Unity 2019.2 up to 2019.4, wasn't happening in 2017.1
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a12