Search Issue Tracker
Duplicate
Votes
0
Found in
2018.1.5f1
2018.1.9f1
Issue ID
1064523
Regression
Yes
[Physics] Physics Raycaster does not detect the full object's collider bounds after scaling and disabling the object
Steps to reproduce:
1. Open user attached project
2. Play the scene
3. Select the EventSystem and observe the output
4. Select the Game window
5. As you hover over the object you see game object "Incident" listed in the event system
6. Hit "down" arrow key to scale the object down and turn it off
7. Hit "up" arrow to turn it back on and scale it back up
8. Observe that the event system does not find it until you hover over almost the very bottom of the "Incident" game object
Expected result: Physics Raycaster should detect the full object's collision bounds after an object was scaled down and disabled
Workaround: toggle the box collider off and back on after
Reproduced in: 2018.3.0a6, 2018.2.1f1, 2018.1.9f1, 2018.1.5f1
Not reproduced in: 2018.1.4f1, 2017.4.7f1
Regression since: 2018.1.5f1
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
This is a duplicate of issue #1024453