Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.1.0-preview.2
Issue ID
1345043
Regression
Yes
Cinemachine does not read Input System Actions when using a custom Interaction
Reproduction steps:
1. Open the attached project ('1345043')
2. Open scene 'SampleScene'
3. Enter Play mode
4. In Game view, move the mouse around while holding the right-mouse button
Expected result: Cinemachine reads the inputs and the Camera rotates around the cube
Actual result: Camera does not rotate
Reproducible with: 1.1.0-preview.2, 1.1.0-pre.5 (2021.2.0b3, 2022.1.0a2)
Not reproducible with: 1.0.2 (2019.4.29f1, 2020.3.14f1, 2021.1.15f1), 1.1.0-preview.1 (2021.2.0b3)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
"context.PerformedAndStayPerformed" should be called instead of "context.Performed" for desired behavior.
Currently observed behavior when calling "context.Performed" is by design.