Search Issue Tracker
Fixed in 2.2.10, 2,3,5
Votes
0
Found in [Package]
2.2.8
Issue ID
1162074
Regression
Yes
Camera controlled by Cinemachine Framing Transposer will only reach half of Maximum Ortho Size
How to reproduce:
1. Open attached project "case_1162074-MaxOrthoSize.zip" and scene "SampleScene"
2. In Hierarchy window, select "CM vcam1"
3. In Inspector window, observe "Maximum Ortho Size" value (its '5' in my example)
4. In Hierarchy window, select "Main Camera"
5. In Inspector window, observe "Camera" -> "Size"
Expected result: the size value is 5
Actual result: the size is 2.5, half of the "Maximum Ortho Size"
Reproducible with: 2018.3.0b1 (2.2.8), 2018.3.14f1 (2.2.9), 2018.4.2f1 (2.2.9), 2019.3.0a6 (2.3.3, 2.3.4)
Not reproducible with: 2018.3.0b1 (2.1.13, 2.2.0, 2.2.7)
Could not test with: 2018.3.0b1 (2.1.12) and older due to package manager errors
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Add comment