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
- Inspector scroll area stretches when using components with nested serialized arrays on FBX model prefab instances
- Crash on ConstraintProjectionTree::projectionTreeBuildStep when ConfigurableJoint uses JointProjectionMode.PositionAndRotation and connected Rigidbody switches from kinematic to non-kinematic
- ScriptableObject asset is accessed during the lookup of Build Profiles when opening the Build Profiles Window
- [Multiplayer TPS Sample] Grenade launcher explosion misses the Player when the Collider count exceeds HitColliderBuffer
- OS Notification Documentation is missing when following hyperlink in Notifications Settings in Hub
Add comment