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
- [Android] Texture Compression default texture format is set to PVRTC when building via script BuildPipeline.BuildPlayer
- [Android][GameActivity] APK built with Development Build enabled gets flagged as having Malware
- Default name of manually created Global Light 2D GameObject differs from the one included in the initial project Scene
- Option for "Acceleration Structure Build Flags" cannot be toggled when Lightmaps have been Generated for a Mesh Renderer
- Lights in Batch keep resetting to 0 in the Light Batching Debugger when a new GameObject is created and the mouse cursor is hovered over the Inspector window
Add comment