Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Won't Fix in 2023.2.X
Votes
2
Found in
2020.3.47f1
2021.3.22f1
2022.2.14f1
2023.1.0b11
2023.2.0a9
6000.0.0b11
Issue ID
UUM-32705
Regression
No
Variables have no values in them when updating the opened scene with Unity Version Control
Reproduction steps:
1. Open the attached "New Test Project" on both machines
Steps on machine 1:
2. Create a new workspace in the Unity Version Control window
3. Commit the Project to the workspace
4. Disable "Auto Refresh" (Edit > Preferences > Asset Pipeline)
5. Open the "Script" Script and uncomment line 7
6. Open the "Scenes/SampleScene" Scene
7. Select the "GameObject" GO in the Hierarchy window
8. Set the "Test Bool" variable to "True" in the Inspector window
9. Save the "SampleScene" Scene
10. Commit the made changes in the Unity Version Control window
Steps on machine 2:
11. Repeat step 3
12. Open the "Scenes/SampleScene" Scene
13. Update the Project from the Plastic SCM
14. Right-click on the "Script" Script in the Project window and press "Refresh"
15. Select the "GameObject" GO in the Hierarchy window
16. Observe the "Test Bool" value in the Inspector window
Expected result: The "Test Bool" variable is set to "True"
Actual result: The "Test Bool" variable is set to "False"
Reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.2.14f1, 2023.1.0b11, 2023.2.0a9
Reproducible on: Windows 10
Note:
- After reloading the Scene, the "Test Bool" variable is set to "True"
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
- "Objects are trying to be loaded during a domain backup." errors on entering Playmode
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.