Search Issue Tracker
Fixed in 2.5.1
Votes
0
Found in [Package]
2.5.0
Issue ID
1213836
Regression
No
[Cinemachine] Prefab editing spit errors in the console
Editing a prefab containing a VCam will log errors in the console.
1. Create a VCam in the scene
2. Drag the VCam object into the project view to create a prefab
3. From the hierarchy, click on the arrow icon on the right of the prefab instance to edit it
4. When in editing mode, select the VCam object and change some values in the inspector (just to make the prefab dirty)
5. Exit the prefab isolation mode by clicking on the left arrow on top of the hierarchy
6. A dialogue should pop up asking you to either save or discard changes done to the prefab
7. Click on either one
Result:
Error will get logged in the console about object being destroy and GUI related errors.
See console screenshot below.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2.5.1):
Could not reproduce in Unity 2019.3.4f1 with Cinemachine 2.5.0