Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a6
Issue ID
1064768
Regression
Yes
Changes to prefabs aren't applied to Instantiated instances of the prefab until the project is re-opened
When you make changes to a prefab, the changes will not be applied to any instance of that prefab instantiated at runtime until you close/reopen the project.
NOTE: I've only been able to reproduce this with prefabs created with the legacy prefab system and then upgraded. Prefabs created with the new system don't suffer from this problem.
1. Install Unity
2. Open the attached project (prefabupgraderepro.zip)
3. Open SampleScene.scene
4. Find "LegacyPrefab" in Project View and open it
5. Make some changes to the prefab
6. Save the prefab and return to Scene view
7. Enter Play Mode
8. Investigate the instance of LegacyPrefab that is instantiated
Result:
The prefab instance doesn't have the changes made to the root prefab applied to it.
Expected Result:
The changes made to the prefab should be applied to the instantiated prefab instance.
Found in 2018.3.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment