Search Issue Tracker
Feature Request
Feature Request in 2023.2.X
Votes
0
Found in
2021.3.21f1
2022.2.12f1
2023.1.0b10
2023.2.0a7
Issue ID
UUM-31312
Regression
No
[ShaderGraph] "Float" property value may be set to a floating point value via Material Inspector when Node Mode is "Integer"
How to reproduce:
1. Open the user’s attached “UnityBugShaderGraphFloatAsInteger” project
2. Select the “Assets → MyMaterial” Material in the Project Browser
3. Change “MyInt” field to a floating point value
Expected result: Inspector doesn’t let to change to a non-integer value
Actual result: Any rational number may be set
Reproducible with: 10.10.0 (2020.3.38f1), 12.1.7 (2021.3.8f1), 13.1.8 (2022.1.13f1), 14.0.2 (2022.2.0b4), 15.0.0 (2023.1.0a5)
Reproduced on: macOS 12.3 (Intel)
Note:
- “Default” Node field works as expected
- Related issue forum thread:
https://forum.unity.com/threads/integer-mode-behaves-as-float-in-inspector.936149/
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
ShaderGraph needs to output an Integer material property type to get the desired behaviour.
Resolution Note (2023.2.X):
ShaderGraph needs to output an Integer material property type to get the desired behaviour.