Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a8
Issue ID
UUM-52920
Regression
No
PhysicsScene.OverlapSphere is not working when calling it in the custom physics scene
How to reproduce:
1. Open the attached project “OverlapSphere”
2. Open the “IN-50407_OverlapSphereTest” scene
3. Enter the Play mode
4. Observe the Console
Expected result: The message informing about the collider count is logged into the Console
Actual result: There is no message informing about the collider count
Reproducible with: 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a8
Can’t test with: 2021.3.31f1 (The script can’t be loaded without any compilation errors)
Reproducible on: Windows 11 Pro
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
To specify the default layer mask, Physics.DefaultRaycastLayers should be used. In this project, the `default` keyword is used, which really gets resolved to 0 (no layers selected).
Resolution Note (2023.3.X):
To specify the default layer mask, Physics.DefaultRaycastLayers should be used. In this project, the `default` keyword is used, which really gets resolved to 0 (no layers selected).