Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.4.X, 2018.1.X
Votes
0
Found in
2017.3.0p2
2017.3.0a1
Issue ID
989777
Regression
Yes
Assigning a float3 to SurfaceOutputStandard.Albedo causes compilation errors of the shader
To reproduce:
1. Open the project, attached by the user (Shader Bug.zip)
2. Observe the compilation errors in the console
3. Open the ShaderBug.shader
4. Comment out line 46
5. Observe that shader compiles fine now
Expected: Assigning a float3 to SurfaceOutputStandard.Albedo works and doesn't cause compilation errors
Reproduced in 2017.3.0a1, 2017.3.0p4, 2018.1.0b5
Did not reproduce in 2017.2.1p3
Regression introduced in 2017.3.0a1
Fixed in 2018.2.0a1
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