Search Issue Tracker
By Design
Votes
0
Found in [Package]
2.5.0
Issue ID
1230512
Regression
Yes
[Cinemachine] Newly created Virtual Camera has incorrect transform values as it doesn't reset to 0,0,0
Newly created Virtual camera has incorrect transform(position/rotation) values. It should be same as the Main Camera default values.
Steps To Reproduce:
1. Cinemachine > Create Virtual camera
2. Observe the transform of the created virtual camera
Expected Result: The Virtual camera is created with default transform values as the Main Camera
Observed Result: The virtual camera is created with incorrect transform values
Reproducible On: 2020.2.0a5, 2020.1.0b3, 2019.3.07f1
Reproducible On Package Version: 2.5.0
Not Reproducible On Package Version: 2.3.4
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:
This is correct behaviour. Virtual cameras are created to match the scene view camera, not the main camera