Search Issue Tracker
Fixed in 2.8.0
Votes
0
Found in [Package]
2.7.9
Issue ID
1394716
Regression
Yes
Cinemachine Virtual Camera Component gets duplicated when adding the same Component onto a Prefab
How to reproduce:
1. Open the attached "1394716.zip" project
2. Open the "SampleScene" Scene in the Scenes folder
3. Select the "A" GameObject in Hierarchy
4. Copy the hidden "CinemachineVirtualCamera" Component
5. Paste the copied Component into the "B" Prefab in the Prefabs folder
6. Remove the existing "CinemachineVirtualCamera" Component in the "B" Prefab
7. Paste the copied Component into the "B" Prefab once again
Expected result: Only one "CinemachineVirtualCamera" Component appears
Actual result: Two "CinemachineVirtualCamera" Components appear
Reproducible with: 2.7.9 (2021.1.28f1, 2021.2.10f1)
Not reproducible with: 2.6.11 (2019.4.36f1), 2.7.9 (2019.4.36f1, 2020.3.27f1, 2022.1.0b6, 2022.2.0a3), 2.8.0 (2021.2.10f1), 2.8.3 (2021.2.10f1), 2.8.4 (2021.2.10f1, 2022.1.0b6, 2022.2.0a3)
Note:
- Not reproducible with a different Component (tested using Event System)
- Reproducible on a new project
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 (fix version 2.8.0):
Fixed in: 2.8.0