Search Issue Tracker

Won't Fix

Won't Fix in 6000.6.X

Votes

0

Found in

6000.0.74f1

6000.3.16f1

6000.4.8f1

6000.5.0b9

6000.6.0a5

Issue ID

UUM-142886

Regression

No

Cursor image flickers in Viewport preview when unsupported Texture 2D is assigned to element

UI Builder

-

Steps to reproduce:
1. Create new Unity project using Universal 3D Template
2. Open UI Builder
3. Add Button element in Hierarchy window
4. In Inspector > Cursor > click on “None (Texture 2D)” object field
5. Select any image from opened “Select Texture 2D” window
6. In UI Builder press on “Preview” button
7. Move mouse in Viewport
8. Observe the Viewport

\\
Actual results: Unsupported textures can be selected in the Texture 2D object picker, causing Cursor image flicker in the Viewport during preview

Expected results: Unsupported textures should be filtered out from the Texture 2D picker when selecting a cursor image, no texture flickering should be visible

\\
Reproducible with versions: 6000.0.74f1, 6000.3.16f1, 6000.4.8f1, 6000.5.0b9, 6000.6.0a5

\\
Tested on (OS): macOS Tahoe 26.4.1 (M1)

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

  2. Resolution Note (6000.6.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment