Search Issue Tracker
Fixed
Fixed in 2020.3.48f1, 2021.3.26f1, 2022.2.20f1, 2023.1.0b17, 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
- 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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment