Search Unity

  1. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Resolved Focal Length (FOV-Setting) is broken in HDRP 14 when the camera is set to Physical

Discussion in 'Cinemachine' started by Onat-H, Oct 31, 2022.

  1. Onat-H

    Onat-H

    Joined:
    Mar 11, 2015
    Posts:
    195
    Hi all,
    as the title says the focal Length (both the lens presets and the slider) do nothing in HDRP 14 when the vcam is set to physical camera override.
     
    Last edited: Oct 31, 2022
    wm-VR and Mark_29 like this.
  2. marc_tanenbaum

    marc_tanenbaum

    Unity Technologies

    Joined:
    Oct 22, 2014
    Posts:
    637
    Thanks Onat. Will discuss with the team and get some investigation going.
     
    Onat-H likes this.
  3. gaborkb

    gaborkb

    Unity Technologies

    Joined:
    Nov 7, 2019
    Posts:
    856
    The issue is not present in the following released Cinemachine versions:
    • 2.9.2
    • 2.9.0-pre.6
    • 2.8.9
    • 2.6.17
    Let us know if updating Cinemachine does not resolve your issue! :)
    (Tested in unity version: 2022.2)
     
  4. Mark_29

    Mark_29

    Joined:
    Aug 11, 2014
    Posts:
    79
    @gaborkb

    I can confirm I am experiencing these same issues in all unity builds and cinemachines releases I have installed (release, alpha and beta). To add further info:

    In the previous release of cinemachine, it would only allow the user to drive FOV but not the aperture through a virtual camera, but the inverse is true in the newest release. The VC allows you to change the value of the aperture for DOF, but you are unable to change the FOV for a physical camera.

    Tested in Unity
    • 2022.1.20f1 (HRP 13)
    • 2022.2.0b13 (HDRP 14)
    • 2023.1.0a16 (HDRP 15)

    Cinemachine release tested
    • 2.9.2
    • 2.9.0-pre.6
    Please note, I am driving these values via virtual cameras on the timeline and not through code if that helps .... (its an animation). Timeline version:
    1.7.2 (although I have tried previous versions of the timeline too)

    Virtual cameras set to override/physical
     
    Last edited: Nov 1, 2022
    wm-VR, Onat-H and gaborkb like this.
  5. gaborkb

    gaborkb

    Unity Technologies

    Joined:
    Nov 7, 2019
    Posts:
    856
    Thank you, I could reproduce the issue!
     
    Mark_29 likes this.
  6. gaborkb

    gaborkb

    Unity Technologies

    Joined:
    Nov 7, 2019
    Posts:
    856
    A fix will be available with our next releases.
     
    wm-VR, Onat-H and Mark_29 like this.
  7. Mark_29

    Mark_29

    Joined:
    Aug 11, 2014
    Posts:
    79
    @gaborkb Do you have any idea as to when these version will be rolled out to 2022.1 or 2022.2 beta? It seems as though the issue is fixed in the alpha (v3),

    However with both of the new releases (official and beta), there is no update to the cinemachine package.
     
    Onat-H likes this.
  8. Onat-H

    Onat-H

    Joined:
    Mar 11, 2015
    Posts:
    195
    Also I think it would make sense to remove v 2.9.2 or at least disable auto-updating for the time being, as this breaks quite a lot. (I stayed on 2.9.1 on purpose because it's better to have broken aperture than broken fov... When I updated to 2022.2b15, the package was automatically updated to 2.9.2 and didn't notice until our animation team asked me if the "unusual" framing is correct.... :D )
     
  9. marc_tanenbaum

    marc_tanenbaum

    Unity Technologies

    Joined:
    Oct 22, 2014
    Posts:
    637
  10. Onat-H

    Onat-H

    Joined:
    Mar 11, 2015
    Posts:
    195
    Thanks Marc!
     
  11. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,125
    The regression has been fixed in Cinemachine 2.9.4, which was released earlier this week.
     
    Mark_29 likes this.