Search Issue Tracker
Fixed
Fixed in 2.6.17, 2.8.9, 2.9.1
Votes
1
Found in [Package]
2.6.11
2.8.4
2.9.0-pre.6
Issue ID
CMCL-922
Regression
No
Clutter caused by vcams in git
It could be that this is a user error, because version control on the scene might not be recommended.
Reproduction Steps:
In a nearly empty scene I reproduced the issue.
1. Create scene and add a Cinemachine camera and an empty GameObject.
2. Set Aspect ratio to 16:9 in Game window
3. Commit to Git.
4. Change aspect ratio to 16:10, make any edit to the GameObject (like position), and save the scene.
5. Observe in Git that the only pending change is the GameObject.
6. Add a Cinemachine Virtual Camera. Repeat steps 2 through 4.
7. Observe in Git that there are now pending changes to the m_SensorSize on the virtual camera.
So this seems to be occurring only on virtual cameras, and only when you've changed the aspect ratio (or resized the free aspect) from what's in the Git repository, *and* made any other edits to the scene before saving.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment