Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
Issue ID
1294048
Regression
No
Integer property type in ShaderLab has no effect on uniforms and fixed function state
Integer property type in ShaderLab has no effect on uniforms and fixed function state
STR: create a new shader, add a property with type Integer, connect it to a uniform or fixed function state.
Create a material, assign it to a cube, modify the property.
Expected: property affects fixed-function or uniform state
Actual: property has no effect
Comments (1)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Tooster
Feb 15, 2024 22:26
If that's the same issue, then it's not resolved in 2022.3.13f1. Just tried a shader with `[Enum(UnityEngine.Rendering.CullMode)] _Cull("Cull", Integer) = 0` and `Cull [_Cull]` in sub shader, along with fragment shader displaying different colors depending on `bool facing : SV_IsFrontFace`.
The property type `Integer` doesn't work when changing cull mode in material inspector. When property `Int` (legacy) is used instead, it works as intended.