Search Issue Tracker
Won't Fix
Won't Fix in 3.1.X
Votes
0
Found in [Package]
3.1.0
Issue ID
CMCL-1582
Regression
No
The "cm" GameObject is not removed when upgrading a component to Cinemachine 3
Reproduction steps:
1. Open the “IN-70525_repro_project.zip” Project
2. Open the “SampleScene”
3. In the Hierarchy window, open the “Room” GameObject in Prefab mode
4. Select the “VirtualCamera” GameObject
5. In the Inspector window, open the Cinemachine Upgrader and upgrade the component
6. Observe the Hierarchy window
Expected result: the “cm” GameObject gets removed
Actual result: the “cm” GameObject does not get removed
Reproducible with: 3.0.1, 3.1.0 (2022.3.26f1, 2023.2.20f1, 6000.0.0b16)
Couldn’t test with: 2021.3.36f1 (Cinemachine 3 is not available)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note:
- Not reproducible in an empty 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:
Several issues were raised:
1. "cm" child objects: these are no longer present in CM3 once the full upgrade is completed. Won't change in CM2.
2. CM3 hard to find in package manager: this is by design.
3. Vcam Priority API has changed unnecessarily: Fixed in CM 3.1.0.
4. Upgrading a CM2 project to CM3 can be non-intuitive: we have accurately documented the process in the CM3 upgrade guide.
5. Inspector in a strange state: this is due to an incomplete upgrade with compile errors. The solution is to finish the upgrade by fixing the compile errors in the local scripts.
Resolution Note (3.1.X):
Several issues were raised:
1. "cm" child objects: these are no longer present in CM3 once the full upgrade is completed. Won't change in CM2.
2. CM3 hard to find in package manager: this is by design.
3. Vcam Priority API has changed unnecessarily: Fixed in CM 3.1.0.
4. Upgrading a CM2 project to CM3 can be non-intuitive: we have accurately documented the process in the CM3 upgrade guide.
5. Inspector in a strange state: this is due to an incomplete upgrade with compile errors. The solution is to finish the upgrade by fixing the compile errors in the local scripts.