Search Issue Tracker

Fixed

Fixed in 6000.3.1f1, 6000.4.0a6, 6000.5.0a2

Votes

0

Found in

6000.3.0b9

6000.4.0a4

6000.5.0a2

Issue ID

UUM-127514

Regression

No

Shader Build Settings keyword overrides not matching with different empty keyword forms

-

The shader build settings requires exact match of the keyword list to apply given keyword declaration overrides. However, the users would expect "empty keyword" to be the same no matter how many underscores is used to spell it out (as this is how it works otherwise). Requiring the exact match in the empty keyword case can be really confusing for users trying to use the shader build settings.

 

Steps to reproduce:

  1. Create a shader with multi_compile using multiple underscores as the "empty keyword"
  2. Create a keyword declaration override in the shader build settings targeting that multi_compile but using single underscore as the "empty keyword"

Actual results: 

The keyword declaration override does not take effect on the shader.

Expected results: 

The keyword declaration override affects the shader.

Reproducible with versions: 

Not reproducible with versions: 

Can’t test with versions: 

Tested on (OS): 

Notes:

  •  
  1. Resolution Note (fix version 6000.5.0a2):

    Any number of underscores as the empty keyword identifier are now treated the same in the shader build settings.

  2. Resolution Note (fix version 6000.4.0a6):

    Any number of underscores as the empty keyword identifier are now treated the same in the shader build settings.

  3. Resolution Note (fix version 6000.3.1f1):

    Any number of underscores as the empty keyword identifier are now treated the same in the shader build settings.

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.