Search Issue Tracker
Fixed in 2.6.X
Votes
0
Found in [Package]
2.3.3
Issue ID
1222740
Regression
No
[Cinemachine] FreeLook Value Range still affects camera even with Binding Mode that doesn't allow changing it
Steps to reproduce:
1. Open attached project
2. Select "CM FreeLook1" camera
3. Under Orbits->Binding Mode, select "World Space"
4. Under X axis, For Value Range, input 0 and 5 for Min and Max values respectively
5. Select Binding mode to "Simple Follow with World Up"
6. Enter Play mode
7. Moving the mouse sideways to the left will rotate the camera slowly, while rotating to the right will flip around very quickly
8. Change the Binding mode to "World Space" again
9. Under X axis, For Value Range, input 0 and 360 for Min and Max values respectively
10. Change the Binding mode to "Simple Follow with World Up"
11. Moving the mouse sideways to the left or right will rotate the camera slowly
Expected: Value Range should not affect "Simple Follow with World Up" binding mode or it should be displayed when that binding mode is selected
Actual: If "Simple Follow with World Up" is selected, Value Range is hidden even though those values can affect the Camera
Reproduced on: 2020.1.0a25, 2019.3.3f1, 2019.21f1
Cinemachine PV: 2.5.0, 2.3.3
Attaching a video of the repro to the case
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
- Undoing Animator Parameter name change breaks references to it
- Crash on BV4_OverlapBoxAll when moving in play mode
- Custom mesh water surface normal map fades out when Y Position increases
- Sprite renderer does not issue draw calls correctly when using SRP Batcher
- [Android] Flickering artifacts when using "ScriptableRenderer.EnqueuePass(RenderPassEvent.BeforeRenderingPostProcessing)" multiple times
Resolution Note (fix version 2.6):
Fix will be available in the next release.