Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.8.9
2.9.7
3.0.0-pre.8
Issue ID
CMCL-1522
Regression
No
Moving Cinemachine Camera parented to Cinemachine Brain causes non deterministic movement
Reproduction Steps:
1. Open attached project "CinemachineBug.zip" and scene "SampleScene"
2. In Hierarchy window, select the "CinemachineCamera" GameObject
3. Either via the Transform Gizmo or the Transform Component, move the "CinemachineCamera" GameObject
4. Observe child and parent Cameras' position in Scene View and the Transform Component
Expected result: Only the "CinemachineCamera" GameObject is moved or both of the Cameras are moved to the same position
Actual result: The parent Camera's transform moves much further than intended, and may continue moving even after the child Camera's transform is no longer interacted with
Reproducible with: 2.8.9 (2021.3.31f1), 2.9.7 (2022.3.11f1, 2023.1.17f1, 2023.2.0b14), 3.0.0-pre.9 (2023.3.0a11)
Reproduced on: Windows 10
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
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
Resolution Note:
User error. CM Camera should not be a child of main camera, because CM camera's relative position drives main camera's position, creating a feedback loop. See the CM camera inspector, it displays an error message telling you not to do this.