Search Issue Tracker
Fixed
Fixed in 2021.3.14f1, 2022.1.23f1, 2022.2.0b16, 2023.1.0a19
Votes
0
Found in
2020.3.38f1
2021.3.10f1
2022.1.16f1
2022.2.0b8
2023.1.0a10
Issue ID
UUM-14611
Regression
No
[Linux] CinemachineVirtualCamera Component's body's "ScreenY" and "ScreenX" values move towards 1.5 while pressing and moving the mouse
How to reproduce:
# Open the attached project (BugRepro.zip)
# Make sure the “SampleScene“ is open
# Enter Play Mode
# In the Hierarchy select the “VCam“ Game Object
# In the Inspector expand the “CinemachineVirtualCamera“ Component’s “Body“ section
# Observe how “Screen X” and “Screen Y“ values change while doing the proceeding step
# In the Game view left click the mouse and move it in circles for 30 seconds
Expected result: The “Screen Y“ and “Screen X“ values are modified based on where the mouse moves in the Game view
Actual result: The “Screen Y“ and “Screen X“ values go up to 1.5 no matter where the mouse is moved
Reproducible on: Cinemahine 2.5.0, 2.6.17 (2022.3.38f1), 2.8.6 (2021.3.10f1), 2.8.9 (2022.1.16f1), 2.9.0-pre.6 (2022.2.0b8, 2023.1.0a10)
Reproducible with: Ubuntu 20.04
Not reproducible on: Windows 10
Notes:
# “Screen X” reaches 1.5 slower when compared to “Screen Y“ and sometimes gets stuck at a lower value than 1.5
# If the “Body“ section isn’t opened in the “CinemachineVirtualCamera“ Component the issue doesn’t reproduce
# Changing “Screen X” and “Screen Y” values back to 0.5 allows the process to be repeated again
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 2023.1.0a19):
Verified the fix has landed to trunk 3231fba0b481 with Rocky Linux 8.6
Resolution Note (fix version 2022.2.0b16):
Fixed in 2022.2.0b16
Resolution Note (fix version 2022.1.23f1):
Fixed in 2022.1.23f1
Resolution Note (fix version 2021.3.14f1):
Fixed in 2021.3.14f1