Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.2.7
Issue ID
1107512
Regression
No
Cinemachine - Apply to all children prompt when no children exist
When changing the layer of a camera a pop up prompt appears asking to "Apply to all Children". There are no child objects attached to the camera game object.
Steps to reproduce
- Open the attached project in Unity 2018.30f1
- Open the "ClearShot Demo Scene"
- In the hierarchy select "CM ClearShot1 > CM vcam3"
- In the Inspector change the "Layer" from Default to any of the listed layers
Notice issue >> Prompt appears asking to apply changes to all children.
Tested Package Versions: 2.2.7, 2.2.0, 2.1.12
Tested Unity Versions 2018.3.0f1
Unable to test in 2019.1 because of issues with cinemachine package.
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
- Main Camera rendering is being overwritten by a UI Camera when using multiple cameras with URP and the second camera's background type is set to "Uninitialized"
- VisualTreeAsset has significantly increased memory allocation size at runtime when the project is built with IL2CPP scripting backend
- NullReferenceException is logged when cancelling Shader Graph recovery of an already deleted Shader Graph
- White Edges appear during Camera movement in runtime when using FSR2 with Motion Vectors and Exposure enabled
- Lens Flare renders without occlusion when the light source is obstructed by solid objects when running on Android using OpenGL
Resolution Note:
This is a known issue. Cinemachine creates hidden children on the vcam. We are working on changing this behaviour, CM 3.0 will not do this.