Search Issue Tracker
Fixed in 2018.1.X
Votes
1
Found in
2017.2.0f3
Issue ID
963332
Regression
No
PrefabUtility.RecordPrefabInstancePropertyModifications not saving prefab changes
Steps to reproduce:
1. Open attached project
2. Open "Scene1" scene
3. Go to menu TestPrefab -> ModifyAndSaveInstance
4. Cube gets scaled from (1,1,1) to (2,2,2) as expected
5. Save and reopen scene
-Cube scaling didn't save and got reverted back to (1,1,1)
Actual result: PrefabUtility.RecordPrefabInstancePropertyModifications didn't save changes to prefab
Expected result: PrefabUtility.RecordPrefabInstancePropertyModifications should save changes to prefab
Reproduced with: 2017.1.2p2, 2017.2.0f3, 2017.3.0b5
Comments (3)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Siegvar
Feb 01, 2018 01:41
My current workaround is to disconnect and reconnect the prefabinstance in my editor script. Seems to work fine so far, but not extensively tested.
Putting it out here in hopes it saves some guys a couple of hair-tearing hours.
LazloBonin
Oct 30, 2017 21:31
Link fix (can't edit): http://support.ludiq.io/forums/5-bolt/topics/579-object-variables-on-prefab-instances-reset-when-assigned-from-the-variables-window/
LazloBonin
Oct 30, 2017 21:30
This issue is classified as severity 3: "Workaround is possible".
What is the suggested workaround?
Currently, this causes an unsolvable bug in my editor extension (Bolt):
http://support.ludiq.io/forums/5-bolt/topics/579