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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment