Search Issue Tracker
In Progress
Fix In Review for 2023.1.X
Fixed in 2022.2.15f1
Under Consideration for 2023.2.X
Votes
0
Found in
2022.2.0b10
2023.1.0a12
2023.2.0a1
Issue ID
UUM-20621
Regression
Yes
Changing Cinemachine camera's physical properties does not change the respective properties of the Main Camera
How to reproduce:
1. Open the attached “bug-cinemachine-iso” project
2. Select “CM vcam1” in the Hierarchy
3. In the Inspector’s “CinemachineVirtualCamera” component navigate to “Lens” → “Physical Properties” → “Iso” and change its value to any other number (e.g., “143”)
4. Select “Main Camera” in the Hierarchy
5. Expand the “Projection” property in the “Camera” component
6. Observe the “ISO” value under the “Camera Body” category
Expected result: The value is the same as the new value in the Cinemachine camera
Actual result: The value remains the same (200)
Reproducible with: 2022.2.0a10, 2022.2.0b10, 2023.1.0a12
Not reproducible with: 2020.3.39f1, 2021.3.11f1, 2022.1.20f1, 2022.2.0a9
Reproducible on: Windows 10
Notes:
1. HDRP is required to access the physical properties
2. Also reproduces with Aperture and Shutter Speed properties
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment