Search Issue Tracker
Won't Fix
Votes
0
Found in
5.3.0b1
Issue ID
739903
Regression
Yes
SetTextureScale started complaining about material missing texture property
Open the scene TrackEditor_Example from the attached project and press Play. It will throw lots of errors about materials missing some texture properties: http://i.imgur.com/BfbNb0h.png
These errors don't show up in Unity 5.3.0a1 or earlier versions. This is a regression introduced somewhere between Unity 5.3.0a1 (fa0e11261f8c) and 5.3.0b1 (7dfb4e0eab03)
-----------------
Won't fix since it's caused by a user error, his custom shader fails to compile:
Shader error in 'LevelEditor_DiffNorm': 'vert': output parameter 'o' not completely initialized at line 84 (on glcore)
As a result m.SetTextureScale fails to find shader properties by name. Which is perfectly expected behavior from our side.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Remote Config] PreparePayloadWithConfigType function is looking for camelCase property names, when the JSON objects are using PascalCase naming
- UI Builder Viewport's Tool Gizmo has deadzones
- SpriteShapes are rendered using multiple draw calls when the SRP Batcher determines their nodes are incompatible in a specific project
- UI Toolkit Debugger "Pick Element" selects Scene view panel when trying to select a world space UI element in the Scene view
- MSAA warnings are thrown when custom post-processing is used and the Scene contains transparent GameObjects
Add comment