Search Issue Tracker

Duplicate

Duplicate in 6000.6.X

Votes

0

Found in

6000.3.0b10

6000.4.0a4

6000.5.0a1

6000.6.0a1

Issue ID

UUM-126647

Regression

No

"Type override" and "Strip keywords" strings overlap in the docked "Build Profiles" window

Shader System

-

Steps to reproduce:

  1. Create a project
  2. Go "File" -> "Build Profiles"
  3. Click the "Add Build Profile" button
  4. Select "macOS"
  5. Click the "Add Build Profile" button one more time in the "Platform Browser" window
  6. Click the "Add Settings" button in the build details window
  7. Select "Graphics Settings"
  8. Expand the section
  9. Resize or dock the window and observe the "Keyword Declaration Overrides" section

Actual results: Strings "Type override" and "Strip keywords" overlap each other 

Expected results:  No overlapping 

Reproducible with versions: 6000.3.0b10, 6000.4.0a4, 6000.5.0a1

Not reproducible with versions: -

Can’t test with versions: 6000.2.9f1, as this stream and build misses a new implemented change

Tested on (OS): macOS - Tahoe 26.1

  1. This is a duplicate of issue #UUM-133326

    “Selected keywords” string under “Shader Build Settings” is cut off (not truncated) in minimized "Build Profiles" window

  1. Resolution Note:

    Thank you for reporting this bug to Unity.

    We have reviewed your issue and found that it is a duplicate of an existing bug in our system. The good news is that this original issue has already been resolved, and the fix is currently available in the latest version of Unity 6.3 LTS.

    To keep our system organized, we have linked your report to the original case and will now close this ticket. We recommend updating your project to the latest 6.3 LTS release to take advantage of this fix.

    Thank you for your time and for helping us improve Unity!

  2. Resolution Note (6000.6.X):

    Thank you for reporting this bug to Unity.

    We have reviewed your issue and found that it is a duplicate of an existing bug in our system. The good news is that this original issue has already been resolved, and the fix is currently available in the latest version of Unity 6.3 LTS.

    To keep our system organized, we have linked your report to the original case and will now close this ticket. We recommend updating your project to the latest 6.3 LTS release to take advantage of this fix.

    Thank you for your time and for helping us improve Unity!

Log in to vote on this issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues