Search Issue Tracker
Fixed in 2021.2.X
Votes
4
Found in
2020.2.0a1
2020.2.1f1
2021.1
2021.2
Issue ID
1305557
Regression
Yes
GUIToScreenPoint() returns physical screen coordinates when in GUIGroup
Reproduction steps:
1. Open user's project "GUIToScreenPointBug.zip"
2. Open "SampleScene" Scene
3. Enter Play Mode and click around in Game view
Expected result: GUI coordinates match with Screen coordinates
Actual result: GUI coordinates don't match with Screen coordinates
Reproducible with: 2020.2.0a1, 2020.2.2f1, 2021.1.0b3, 2021.2.0a2
Not reproducible with: 2019.4.18f1
Couldn't test with: 2018.4 (couldn't downgrade to a functioning 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 (fix version 2021.2):
Fixed in 2021.2.0a8