Search Issue Tracker
Won't Fix
Votes
3
Found in
2017.1.0f3
Issue ID
942116
Regression
No
Game Object's Animator Controller is not saved after deleting Library folder from the project folder
How to reproduce:
1. Open QA-supplied project
2. In the Hierarchy expand "Larva" and select "Animator" gameobject
3. Observe that in the Inspector the Animator component has Controller "LarvaAnimator"
4. Close Unity
5. Open project folder and delete Library folder
6. Re-open project and open "sceneWithBug" scene
7. In the Hierarchy expand "Larva" and select "Animator" gameobject
8. Observe that in the Inspector the Animator component has no Controller
Expected result: Deleting Library folder from the project folder does not cause any changes in the scene
Actual result: Animator Controller is missing after deleting Library folder from the project
Reproduced with: 5.5.4p4, 5.6.3p1, 2017.1.0p5, 2017.2.0b8, 2017.3.0a5
-
Sarseth
Oct 04, 2017 09:54
The problem has not workaround when you work with other ppl. Removing library is a simulation of working with others, so it's easy to reproduce. Library folder is not shared between users, it is not on any kind of repo, it was never suggested to be. Assets and project settings only. So for example, when I make a change, there is no known workaround that other user who pulls commit see animator controller changes on prefab.
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Resolution Note (2019.1.X):
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.