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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment