Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2019.3
2019.4
2020.1
2020.2
2020.2.0a16
Issue ID
1257991
Regression
No
[2D] Depth keyword gets clipped in the Visibility Tool window in the skinning editor
[2D] Depth keyword gets clipped in the Visibility Tool window in the skinning editor.
The depth keyword gets clipped in the Visibility Tool window in the skinning editor in sprite editor only when the display resolution set to 125% or more. Refer to the attached screenshot.
Note: Working fine when the display resolution set to 100%
Steps to reproduce:
1. Create a new project with a 2D template.
2. Import Fei_Cel_group.psb file or any Sprite into the Unity project.
3. With the sprite selected in Assets, open Sprite Editor.
4. Sprite Editor > Skinning Editor > Visibility tool
5. Observe the Depth keyword gets clipped in the Visibility Tool window.
Actual result: Depth keyword gets clipped in the Visibility Tool.
Expected result: Depth keyword should not get clip with any display resolution.
Occurring in : 2020.2.0a16, 2020.1.0b12, 2019.4.2f1, 2019.3.15f1
Environment: Windows 10.
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2021.1):
Fixed in 5.0.2
Resolution Note (fix version 2020.2):
Verified on :
Version: 2020.2.0b6.3259
Revision: 2020.2/staging 24a0f8b56f72
Built: Fri, 02 Oct 2020 01:34:47 GMT