Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0b6
2019.1.0f2
2019.2.0a1
2019.3.0a1
Issue ID
1149186
Regression
Yes
EditorGUIUtility.PingObject on a Hierarchy object is visually offset
How to reproduce:
1. Open attached project "PingObjectOffset.zip" and scene "SampleScene"
2. In the Hierarchy window, select "SampleObject"
3. In the Inspector window, press on "Ping me" button (Sample Ping custom editor component)
4. Observe the "SampleObject" in the Hierarchy window
Expected result: the object highlights properly
Actual result: the object highlight is offset to the left
Reproducible with: 2019.1.0b6, 2019.1.1f1, 2019.2.0a14, 2019.3.0a1
Not reproducible with: 2017.4.26f1, 2018.3.14f1, 2019.1.0b5
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
Add comment