Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.16f1
2022.2.2f1
2023.1.0a23
2023.2.0a1
Issue ID
UUM-21560
Regression
No
"Material doesn't have a float or range property '_GradientScale'" error thrown when selecting an Element in the UI Builder
How to reproduce:
1. Open the user-attached project (MWE.zip)
2. In the Project window double-click to open the MWE (Visual tree asset)
3. In the UI Builder windows Hierarchy section select the Button element
4. In the UI Builder's Inspector section under Text make sure that "Font Asset" is set to "NotoSerifThai-Regular"
5. Deselect and reselect the Button as described in step 3
6. Observe the Editor's Console panel
Expected result: An error gets thrown in the Console
Actual result: No errors are thrown in the Console
Reproducible with: 2021.3.16f1, 2022.2.2f1, 2023.1.0a23
Could not test with: 2020.3.42f1 (UI Builder not available)
Reproducible on: Ubuntu 20.04, Windows 10
Full error:
Material 'NotoSerifThai-Regular Material' with Shader 'Hidden/Internal-GUITextureClipText' doesn't have a float or range property '_GradientScale'
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
Can't reproduce.
On 2022.3 only, the font asset seems to be corrupted (we cannot see the text in the button). However, no error is being thrown. This can be solved by simply creating the font asset again from the Font.
Resolution Note (2023.2.X):
Can't reproduce.
On 2022.3 only, the font asset seems to be corrupted (we cannot see the text in the button). However, no error is being thrown. This can be solved by simply creating the font asset again from the Font.