Search Issue Tracker
By Design
Votes
0
Found in [Package]
2.6.10
2.7.8
2.8.0-pre.1
2.8.0
Issue ID
CMCL-336
Regression
No
CinemachineImpulseSource.GenerateImpulseAt() continues to move the Camera when TimeScale is set to 0
How to reproduce:
1. Open the user's attached "CinemachineTest.zip" project
2. Open the "SampleScene" Scene
3. Enter Play Mode
4. Press the Space key and then the Escape key
5. Observe the Game view
Expected result: CinemachineImpulseSource stops moving the Camera
Actual result: CinemachineImpulseSource keeps moving the Camera
Reproducible with: 2.7.3, 2.8.0-pre.1 (2018.4.34f1, 2019.4.27f1, 2020.3.10f1, 2021.1.8f1, 2021.2.0a17)
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
- NullReferenceException errors appear in the Console when changing the values of Visual Effect Control Clip Events' Attributes
- Crash on TextCore::OTL_TableReader::GetOpenTypeLayoutTables when using Japanese Font as TMP Fallback
- TreeView.AddItem performance regression when opening EditorWindow
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
Resolution Note:
The error is caused by incorrect setup. Cinemachine vcam is a child of the Main Camera. If I move the vcam out (so it is no longer a child of the Main Camera), then the bug is not present.