Search Issue Tracker
Fixed in 4.6.1
Votes
0
Found in
4.6.0b20
Issue ID
636761
Regression
No
Physics2D.RaycastAll don't calculate hit for CircleCollider2D if distance parameter is set to float.MaxValue
To reproduce this bug:
1. Open the attached project
2. Open 'test' scene
3. Press play
4. Notice in the console that only RaycCasterBox indicates a hit
5. Select 'RayCasterCircle' in the hierarchy
6. Uncheck 'Max Value Distance' and now distance will be set to 1000.0f instead of float.MaxValue
7. Now everything works fine
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
Add comment