Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2021.3.29f1
2022.3.7f1
2023.2.0b5
2023.3.0a4
Issue ID
UUM-46787
Regression
No
Shader Graph Blackboard categories are shown in the Inspector even when all of their properties and keywords are not exposed
Reproduction steps:
1. Open the attached “IN-48414_Shader Graph Blackboard unexposed properties.zip” project
2. Select the “ShadowMaterial.mat” in the Materials folder
3. Observe the “Surface Inputs” settings in the Inspector
Expected result: Categories from the Blackboard of the “ShadowMaterial” Shader Graph with no exposed properties or keywords are hidden in the Inspector
Actual result: Categories from the Blackboard of the “ShadowMaterial” Shader Graph with no exposed properties or keywords are shown in the Inspector
Reproducible with: 12.1.12 (2021.3.29f1), 14.0.8 (2022.3.6f1), 15.0.6 (2023.1.7f1), 16.0.3 (2023.2.0b3)
Reproduced on: Windows 11 Pro
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
For now; we won't be changing this behavior without adding additional options to control the material inspector behavior. We'll keep this in mind for a UI/UX refresh that we're working on, but we won't be addressing this issue as it stands.
Resolution Note (2023.3.X):
For now; we won't be changing this behavior without adding additional options to control the material inspector behavior. We'll keep this in mind for a UI/UX refresh that we're working on, but we won't be addressing this issue as it stands.