Search Issue Tracker
Fixed in 5.3.1, 7.1.7
Votes
1
Found in [Package]
5.3.1, 7.1.7
Issue ID
1210509
Regression
Yes
[SRP] Changes are not applied to Material's Main Texture when using Material.mainTexture functions
How to reproduce:
1. Open the attached project's "case_1210509-Project_LWRP.zip" Scene labeled "SampleScene"
2. Enter the Play Mode
3. Inspect the "Drywall Panel" GameObject
Expected result: Texture scrolls around the GameObject
Actual result: Main Texture is not affected by the new assignment of Material.mainTextureOffset
Reproducible with: 2019.2.0b7(5.3.1, 6.7.1), 2019.2.18f1 (6.9.0, 6.9.2), 2019.3.0f4 (7.1.6, 7.1.7), 2020.1.0a18 (7.0.1, 7.1.7)
Not reproducible with: 2018.4.15f1 (4.1.0-preview), 2019.2.0b7 (5.1.0, 5.2.3)
Couldn't test with: 2017.4.36f1 (Package Manager does not exist)
Workaround: Apply changes to _BaseMap instead of _MainTex
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Silicon] Crash on ScriptableRenderLoopJob when machine is left idle while the Editor is in Play mode
- [Android] GraphicsBuffer.CopyCount does not work with Append Compute Buffer after Compute Shader Dispatch on some Android devices
- "DirectoryNotFoundException" error when building a project via script in one folder, then building via Editor in another, deleting the folder built via Editor and rebuilding via Script
- New items are created and old ones remain in memory when using 'treeView.SetRootItems(items)' and 'treeView.Rebuild()' which can cause a memory leak
- Code continues to run after enabling the Frame Debugger when in paused Play Mode and using 'WaitForSecondsRealtime' coroutine
Resolution Note (fix version 5.3.1, 7.1.7):
Fixed in Unity 2020.1.0a21
Resolution Note (fix version 5.3.1, 7.1.7):
Fixed in Unity 2019.3.8f1