Search Issue Tracker
Fixed
Fixed in 3.1.5
Votes
0
Found in [Package]
3.1.4
Issue ID
CMCL-1693
Regression
Yes
Cinemachine blend duration becomes incorrect when interrupting multiple blends
Reproduction steps:
1. Open the attached “IN-107302.zip” project
2. Open the “SampleScene”
3. Enter Play mode
4. Press “2” on the keyboard and wait 1-2 seconds
5. While the blend is in progress, press “1” on the keyboard
6. Press “2” on the keyboard again instantly
7. Observe the camera blend
Expected result: The camera blends smoothly to Cam2 over approximately 7-8 seconds
Actual result: The camera quickly zips to Cam2 in approximately 0.7 seconds instead of blending smoothly
Reproducible with: 3.1.3, 3.1.4 (2022.3.63f1, 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a1)
Not reproducible with: 3.1.2 (2022.3.63f1, 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a1)
Reproducible on: Windows 10 (user reported), Windows 11
Not reproducible on: No other environment tested
Notes:
- The bug was likely introduced after a fix for this: https://discussions.unity.com/t/i-dont-understand-the-cinemachine-camera-blend-duration-behavior/1592488/4
- Performing the same repro steps but waiting different amounts of time between the 5th and 6th steps, shows that in 3.1.2, the final blend always respects the settings on the Brain, but in 3.1.3, the shorter the wait, the faster the final blend is. It continues to shrink the more times a blend is started
- Also reproduces in the Player
- In the scene are two CinemachineCamera objects and a script to swap their priority with the “1” and “2” keys. Pressing “1” sets Cam1 to the higher priority, and pressing “2” sets Cam2. Cam1 is higher initially. The settings on the Brain have a 1->2 blend of 10 seconds, and a 2->1 blend of 7 seconds
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment