Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.3.48f1
2021.3.26f1
2022.3.0f1
2023.1.0b19
2023.2.0a17
Issue ID
UUM-36905
Regression
Yes
Physics.Raycast does not work when used on the whole model
Reproduction steps:
1. Open project “BugReport”
2. Open “SampleScene”
3. Enter Play Mode
4. Click on the left side of the model
5. Observe the Console printing “True”
6. Click on the right side of the model
Expected result: the Console prints “True”
Actual result: the Console prints “False”
Reproducible with: 2019.3.7f1, 2020.3.48f1, 2021.3.26f1, 2022.3.0f1, 2023.1.0b19, 2023.2.0a17
Not reproducible with: 2019.3.6f1
Reproducible on: macOS Ventura 13.2.1 (Intel), Windows 10 (by the reporter)
Note: couldn’t test in Standalone Player due to the model breaking
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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Resolution Note:
Since mesh isn't available we can't access it.
Try going to the mesh collider > Cooking options > deselect Fast Midphase option and run it again.
Warning error gives some hints on what to do to avoid this issue:
"default" mesh has over 2,097,152 triangles in it, and is using the Fast Midphase option. This might cause certain collisions to not be detected correctly due to an issue in the physics engine. If you observe that in your project, a workaround could be to turn off the Fast Midphase option for this particular mesh.