Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.28f1
2022.3.5f1
2023.1.4f1
2023.2.0a23
2023.3.0a3
Issue ID
UUM-43728
Regression
No
physics.overlapspherenonalloc returns inconsistent results when overlapping an object
Reproduction steps:
1. Open the attached project “Piano”
2. Open Build Settings (File > Build Settings)
3. In the Build Settings window make sure that Development Build, Script Debugging and Wait for Managed Debugger are enabled
4. Build and run by pressing the Build And Run button
5. In the Console window select the Editor dropdown menu and select the Player, when a window pops up saying that a debugger can be attached
6. Press OK on the popped up window
7. In the Player move the character to the piano’s keys (to the right)
8. Observe the Console in the Editor
Expected result: overlapspherenonalloc always returns 1
Actual result: overlapspherenonalloc returns 1 or 0
Reproducible with: 2021.3.28f1, 2022.3.5f1, 2023.1.4f1, 2023.2.0a23
Reproducible on: Windows 10
Notes:
In the Play mode, overlapspherenonalloc will always return 1 when near the piano’s keys
In the Player, pressing the Interact button (E on Keyboard) near the piano’s keys will make the character play the piano and shortly stop
Comments from triage:
* Tested on 2023.2.0b1 on Mac and was able to reproduce
* Noticed that in the player build, that there was a periodicity to the output of the logging output to the Player.log where overlapspherenonalloc would return 1, then 5 zeros, and this would repeat (player was positioned in front of the piano in this case. When entering playmode from the Editor, and similarly placed, the log output was consistently 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
- Prefab Override popup displays on wrong monitor when Inspector width is resized to minimum
- Scroll View is not moving by inertia after scrolling by click and dragging when Editor window is minimized and Canvas "Render Mode" is set to "World Space"
- "type mismatch error" occurs when the currentDirectionWS output of a Sample Water Surface node is connected to a float3 input
- URP Material Upgrade utility does not enable Alpha Clipping when material had Rendering Mode set to Cutout
- Particle System emission ignores the Sprite Atlas when using a Material that has the "Include in Build" setting unchecked
Resolution Note:
The submitted issue could not be reproduced after the used APIs have been narrowed down and used to create a simple reproduction sample.
Cheers,
AlexRvn