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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.