Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
0.1.0, 0.2.0
Issue ID
1180155
Regression
No
Dots Physics RayCast does not detect collision when using from float.MAX to float.MIN distance
To reproduce:
1. Open attached project ("case_1180155-Raycast")
2. Attach "Test" script from Assets to "Directional Light" object in Hierarchy
3. Press Play
4. Observe Console
Expected result: CastRay works and "failed 1" message is not being printed in Console
Actual result: CastRay fails and "failed 1" message is being printed in Console
Reproducible in: 2019.2.4f1, 2019.3.0b1, 2020.1.0a2
Could not test in: 2017.4.32f1 (Package Manager not introduced), 2018.4.8f1 (Due to errors in project)
Reproducible in package versions: 0.1.0, 0.2.0
Could not test in package versions: 0.0.1, 0.0.2 (Due to errors in project)
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:
We suggest using a finite number closer to the starting raycasting point for equal results and better performance. Moreover, it is a bad practice to do in a unity project.