Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.3.1p4
Issue ID
765145
Regression
No
[Shader] Occlusion breaks if alpha is dependent to another UV/Texture set
Repro steps:
1) Open the project and AmbientOcclusion.scene
2) Notice four spheres in it - only one - 'DoesWork' shows Ambient Oclussion text on the sphere
3) If you open ShaderWorking.shader, you will notice, that the o.Alpha is dependent on Texture2.a and UV2 set
4) If you open ShaderNotWorking.shader, you will notice, that the o.Alpha is equal to the Alpha of the first texture and thus, is not working
Workaround: use 2nd UV set's data
Reproduced in: 5.4.0b3; 5.3.2p1; 5.2.3p3; 5.1.4f1
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