Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.1.0f3
Issue ID
937943
Regression
No
[Cinemachine] Cinemachine Virtual Camera's "Look At" becomes None after exiting play mode if target's parent was changed
To reproduce:
1. Open attached project "Cinemachine.zip".
2. Open Test scene.
3. Select "CM vcam1" object. It has "Cinemachine Virtual Camera" component, with "Look at" set to Cube (Cube is a child of GameObject).
4. Press Play. (camera follows the cube)
5. Exit Playmode.
Actual result: Cinemachine Virtual Camera's Look At became null after exiting playmode.
Expected result: Playmode has no effect on component values.
Reproducible: 2017.1.1p3, 2017.2.0f1, 2017.3.0b2
Cinemachine version: 2.0.1 (Jul 13, 2017)
Comments (1)
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
- Main Camera rendering is being overwritten by a UI Camera when using multiple cameras with URP and the second camera's background type is set to "Uninitialized"
- VisualTreeAsset has significantly increased memory allocation size at runtime when the project is built with IL2CPP scripting backend
- NullReferenceException is logged when cancelling Shader Graph recovery of an already deleted Shader Graph
- White Edges appear during Camera movement in runtime when using FSR2 with Motion Vectors and Exposure enabled
- Lens Flare renders without occlusion when the light source is obstructed by solid objects when running on Android using OpenGL
popandersson
Nov 15, 2018 16:59
This is still a bug in Unity 2018.2.0b1