Search Issue Tracker
Fixed in 2020.3.48f1
Fixed in 2020.3.X, 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a13
Votes
0
Found in
2020.3.40f1
2021.3.10f1
2022.1.17f1
2022.2.0b8
2023.1.0a11
2023.2.0a1
Issue ID
UUM-21301
Regression
No
Changes made to texture with a specific a _ST property marked as [NoScaleOffset] in the Inspector are shown but not saved
How to reproduce:
1. Open the attached project “IN_16486”
2. Open the “SampleScene” Scene
3. Select the “Cube” GameObject
4. In the Inspector unfold the “Unlit_Custom Shader” Material and change the X and Y value of “Tex 3 ST”
5. Save changes
6. Observe the Game View and unfolded “Unlit_Custom Shader” Material Tex 3 ST X/Y values
Expected result: changes are saved
Actual result: changes not saved
Reproducible with: 2020.3.40f1, 2021.3.10f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a11
Reproducible on: Windows 10 Pro
Note:
- After changing the version of Unity, the project needs to be closed and reopened in order to reproduce the issue
- After reproducing the issue once the project must be closed and reopened in order to reproduce the issue again on the same version
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment