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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
This is correct behaviour. Virtual cameras are created to match the scene view camera, not the main camera