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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a8