Search Issue Tracker
Fixed in 2018.1.X
Votes
1
Found in
2017.2.0f3
Issue ID
996118
Regression
No
Collab: Clients do not properly read data from new variable fields on automatic scene re-load when downloading modified scripts
Reproducing this requires modifying an existing script (adding new variables), assigning a value to the new variable, publishing, and having a second client grab the files from a collab Update.
When the second person downloads the update and reloads their scene automatically, they will see the new fields from the script in the inspector, but the values will be defaults ("none" for objects, "0" for int, etc.). Re-loading the scene locally fixes the issue and picks up the new values.
Making additional changes to the scene and saving them without fixing this (by reloading) will save off the default values instead of the original values.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Add comment