Search Issue Tracker
By Design
Votes
1
Found in
2017.4
2019.3.9f1
2020.2
Issue ID
1237385
Regression
No
Vector3Field gets obstructed when it is used to represent a Quaternion angle and the Inspector window is narrow enough
How to reproduce:
1. Open the attached "1237385 repro" project
2. Open the "SampleScene" from the Assets folder
3. Select the "GameObject" from the Hierarchy window
4. Open the Inspector window
5. Reduce the width of the Inspector window slowly until the "Rotation" Vector3Field under "Script 3" Component gets obstructed
Expected result: all of the variable names and their fields are clearly visible
Actual result: some of the variable names and their field are overlapping and unreadable
Reproducible with: 2017.4.40f1, 2018.4.22f1, 2019.3.12f1, 2020.1.0b8, 2020.2.0a10
Notes:
-It is easier to reproduce this issue on smaller screens, for example, a laptop one
-This only happens with Quaternions and if the variable is changed from Quaternion to Vector3 the Inspector window appears normal again as shown in "Vector3.mp4"
-This also reproduces with URP and HDRP packages as they convert from Quaternion to Euler angles automatically without the need of "QuaternionToEuler.cs"
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 (2020.2.X):
User has to override the GetPropertyHeight() function in the QuaternionToEulerPropertyDrawer class.