Search Issue Tracker
By Design
Votes
0
Found in
5.2.1p1
Issue ID
732893
Regression
No
Int property of shader acts like float in inspector
Steps to reproduce:
1. Open attached project
2. Select TestShader material
3. Notice that it has "Some Int" property
4. Try to change it's value to float
5. Notice that value is successfully changed
6. Open TestShader shader and notice that "Some Int" property is declared as Int
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
Add comment