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
- The <sprite> tag inserted image from a Sprite Asset into the UI Builder Button disappears when the Inlined Style Text Shadow Horizontal or Vertical Offset is set to be more than 0 px
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
- [Android] Virtual device crashes with "Scudo ERROR: invalid chunk state when deallocating address" error in Firebase Test Lab when Optimized Frame Pacing is enabled
- Particle System does not resume when its Culling Mode is set to "Pause" or "Pause and Catch-up," and particle position simulate in world space
Add comment