Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.4.0b17
Issue ID
795553
Regression
Yes
Shader Input Arrays not getting set Unity 5.4
Shader input arrays not getting set Unity 5.4
Steps to Reproduce
-------------------------------
1.Download the small user reproduction project
2.Open the project in 5.3, open the 'test' scene and run in the editor.
3.Note that there are no problems, you will see 16 white squares.
4.Open the same project in the latest 5.4
5.Open the 'test' scene and run in the editor.
Result
When running in 5.4.x you will note that a single black square is visible.
Expected Result:
Sixteen white squares should be visible.
See the 5.3.x Vs 5.4.x comparison screenshot in the comments below.
Tested in
5.3.5f1 (960ebf59018a) - working
5.4.0b18 (5744ebf94ac5) - broken
5.4.0b11 (323b0238353b) - broken
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unapplied changes on the "MainPanel" GameObject in the "BlobShadow" of URP Samples
- [Vulkan][Android] The Player crashes on devices with SP9863A chipset
- "Output properties of this Camera do not match the output properties" warning is shown In the "SplitScreen" scene of URP Samples
- "Gun" Prefab used in "MixedFOV" scene of URP Samples has unapplied changes
- "FirstPersonController uses the legacy input system" message is logged when entering the Play Mode in "MixedFOV" scene of URP Samples
Add comment