Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 2017.2.X
Votes
0
Found in
5.6.0f1
Issue ID
893229
Regression
Yes
Surface Shader does not display correct color if using #ifdef on PARALLAXMAP Preprocessor variable to check if it is defined
How to reproduce:
1. Open the attached "SurfaceShaderStrangeness" project
2. Open "asdf" scene, double click on "Shader_Broken" in Project window to open it
3. Comment #ifdef and #endif lines on 26th and 28th line
4. Notice that the "Plane" has a red color
Expected result: "Plane" should have had a red color, before commenting #ifdef line
Actual result: "Plane" didn't have a red color, until commenting #ifdef and #endif lines in Input struct
Regression introduced in 5.6.0b2
Reproducible with 2017.1.0a3, 5.6.0f2, 5.6.0f1
Not reproducible with 5.6.0b1, 5.5.2p3, 5.4.5f1
Note: Alternatively to a 3rd step on how to reproduce the issue, you can just change "Plane" material shader from Custom/Broken to Custom/NoIfDef (this shader simple removes #ifdef from Input struct)
---
Fixed in 2017.3.0a4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
Add comment