Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
4
Found in
2021.2.0b1
2021.2.0b3
2022.1
Issue ID
1349833
Regression
Yes
Custom asset changes are not applied when modifying the asset in Play Mode
Reproduction steps:
1. Open the attached project "UpdateIssue.zip"
2. Open the "Scenes > SampleScene" Scene
3. Enter Play Mode
4. Click "New Game"
5. Select "Assets > Script" in the Project panel
6. Edit the text on the 2nd line in the Inspector
7. Click "Apply" and observe the Game View
Expected result: Change is applied and visible
Actual result: Change is not visible
Reproducible with: 2021.2.0b1, 2021.2.0b4, 2022.1.0a2
Not reproducible with: 2019.4.29f1, 2020.3.14f1, 2021.1.15f1
Could not test with: 2018.4.36f1 (version does not support the asset), 2021.2.0a1, 2021.2.0a21 (project crashes or asset errors appear)
Note: not reproducible on macOS
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.1):
now fixed both on 2021.2 and 2022.1
Resolution Note (fix version 2021.2):
The fix landed in 2021.2.0b7, verified fixed manually on 2021.2.0b12 and 2021.2.2f1