Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4
2019.4.21f1
2020.3
2021.1
2021.2
Issue ID
1318169
Regression
No
The wrong variable value is used when accessing it from a method which is called from another script
Reproduction steps:
1. Download and open the attached project "1318169.zip"
2. Enter Play mode and notice the values logged in the console
3. Exit play mode
4. Open the "Script1" script and change the assigned testVariable value on line 10
5. Enter Play mode and notice the values logged in the console
Expected result: The logged values are both the same as set in step 4
Actual result: The second logged value is the same as it was set once the project was opened
Reproducible with: 2018.4.33f1, 2019.4.23f1, 2020.3.3f1, 2021.1.2f1, 2021.2.0a12
Notes:
Restarting the project or switching scenes solves the issue
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:
The PrefabInstance present in the scene gets recreated on entering play mode(scene is reloaded) invoking the initializers. While the already in memory prefab remains.