Search Issue Tracker
Fixed
Fixed in 2.6.18, 2.8.10, 2.9.2, 3.0.0-pre.3
Votes
0
Found in [Package]
2.6.17
2.8.9
2.9.1
3.0.0-pre.3
Issue ID
CMCL-652
Regression
No
[Cinemachine] ForceCameraPosition changes values in the Inspector when returning saved camera position and rotation
Reproduction steps:
1. Download the user's attached project "Unity Support.zip"
2. Open "Cinemachine2.6 Issue Demo" in Editor
3. Open Assets > Scenes > SampleScene
4. Enter Play Mode
5. Click the button "Set Random X/Y axis" to get different positions
6. Click the button "Save State" to save the camera values
7. Click the button "Restore State" to restore the camera values
8. Observe values at the top of the screen
Expected results: Cinemachine using ForceCameraPosition returns the exact camera position and rotation values
Actual results: Cinemachine using ForceCameraPosition changes position and rotation values in the Inspector before returning values
Reproduced in: 2.6.10 (2019.4.30f1, 2020.3.19f1), 2.7.8 (2021.1.22f1), 2.8.0 (2021.2.0b13, 2022.1.0a11)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on SerializedProperty:CopyInternalImpl when clicking on a specific Asset
- Crash on BurstCompilerService::CompileAsync when opening a specific project
- [Android] Particles aren't rendered when the shader "Particle/Standard Unlit" or "Particles/Standard Surface" is used on a Material
- Crash on nvoglv64.dll when opening a project
- [RenderGraph] [CameraStacking] Passes are failing when CameraStacking and RG are enabled
Add comment