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
- 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
Add comment