Search Issue Tracker
Fixed
Votes
5
Found in
5.2.1p3
Issue ID
737187
Regression
No
Prefabs will not save inspector data changes if manipulated by editor script
Steps to reproduce:
1. Open Project.
2. Open scene "Test Scene"
3. Click on the gameObject "Cube Prefab" in the Hierarchy.
4. Press the "Assign Variable" button in the Inspector tab under the "Box" component.
5. Notice the value is changed from the default "0" to "1".
6. Repeat steps 3 to 5 for the gameObject "Cube" to change it's value from "0" to "1" via the custom button.
7. Save the scene with ctrl + s
8. Goto File >> New Scene
9. Open the scene "Test Scene" again.
10. Click on the gameObject "Cube" and notice the value is still "1".
11. Click on the gameObject "Cube Prefab" and notice the value has reverted to the default "0".
Reproduced with Windows 10 (64 bit) on 5.2.1p3 (b7d18ab613bc), 5.2.2f1 (f5cc61d36935), 5.3.0b3 (b6181bece87a) and 4.6.9f1 (44099fd26189).
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
- [Linux] Screen.SetResolution immediately applies windowed resolution when switching from Fullscreen to Windowed mode
- Lighting window allows non-cube map texture for Environment Reflections, throwing invalid texture type (2D) error
- Console warning “MismatchingRepositoryProjectMessage” when creating a new Unity Version Control workspace
- [Ubuntu] VFX Graph Enum Value menu stretches across screen when entered long Enum Value
- Unclear warning message in Rendering Debugger about the Play mode Debugger Overlay
krakentanz
Dec 21, 2020 11:10
We seem to have the same problem in 2020.1.6f1 How is this fixed? What was the issue? How can i work around it?
aaronfranke
Jan 06, 2020 18:56
I'm encountering this in 2017.4.28f1
ChrisSpears
Oct 22, 2015 20:22
My guess is this was a conscious change. You now have to manually "Save Project" for a prefab change to stick. HORRIBLE idea in my opinion though it is probably more consistent.