Search Issue Tracker
By Design
Votes
0
Found in
1.3.10
Issue ID
UUM-132651
Regression
No
Raycasts fail to detect child colliders when Static Entities are shifted multiple times per frame
Reproduction steps:
1. Open the attached “IN-94910” project
2. Open the “Scenes/Test” Scene
3. Enable only the “NoneChild” GameObject from “TestSub” Subscene in the Hierarchy window
4. Enter the Play Mode
5. Observe the Console window
6. Enable only the “WithChild” GameObject from “TestSub” Subscene in the Hierarchy window
7. Enter the Play Mode
8. Observe the Console window
Expected result: Raycast consistently hits after shifts
Actual result: Raycast will fail to hit the cube starting from the second {{FixedStep}}
Reproducible with: 1.2.0 (2022.3.59f1), 1.3.2 (6000.0.41f1), 1.3.10 (6000.0.41f1, 6000.1.0b9, 6000.2.0a6)
Reproducible on: Windows 10
Not reproducible on: No other environments tested
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.