Search Issue Tracker
By Design
Votes
0
Found in [Package]
2.6.0
Issue ID
1261619
Regression
No
[Cinemachine]Recomposer effects appear in game view after virtual camera is deleted
Steps To Reproduce:
1. Create a new Project
2. Package Manager > Cinemachine > Install
3. Cinemachine > Create Virtual Camera
4. Virtual Camera > Extension > Cinemachine Recomposer
5. Tweak some settings and observe that camera settings change and appear in game view
6. Delete the Virtual camera
Expected Result: The effects of Cinemachine Recomposer disappears from game view
Observed Result: The effects of Cinemachine Recomposer stays in game view
Note: Cinemachine Recomposer was introduced with Cinemachine 2.6.0
Reproducible On: 2020.2.0a17, 2020.1.0b15
Package Version: 2.6.0
Environment: Win and Mac
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:
When you delete the active virtual camera, the main camera should then take the position of the next-highest priority virtual camera in the scene. If there is no other virtual camera, then the main camera should remain where the last virtual camera put it. That is what's happening.