Search Unity

  1. Unity 2018.3 is now released.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We've updated our Terms of Service. Please read our blog post from Unity CTO and Co-Founder Joachim Ante here
    Dismiss Notice
  4. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  5. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

Cinemachine camera frustum not updating in new unity versions

Discussion in 'Cinemachine' started by CyanSlinky, Nov 8, 2018.

  1. CyanSlinky

    CyanSlinky

    Joined:
    Feb 27, 2014
    Posts:
    11
    The cinemachine virtual camera frustum isn't updating in newer unity versions, tried with 2018.2.12f1 and 2018.2.14f1(newest 2018.2 version as of this post), it works in 2018.2.6f1 i don't know in which version it stopped working.

    Here's a gif i made showing the cinemachine frustum not updating

     
  2. Gregoryl

    Gregoryl

    Unity Technologies

    Joined:
    Dec 22, 2016
    Posts:
    1,932
    It's a regression in Unity, not in Cinemachine. The next 2018.2 release should fix it.
     
  3. CyanSlinky

    CyanSlinky

    Joined:
    Feb 27, 2014
    Posts:
    11
    Nice, glad it's getting fixed. Thanks for the fast response!
     
  4. CyanSlinky

    CyanSlinky

    Joined:
    Feb 27, 2014
    Posts:
    11
    still broken in 2018.2.15f1, it seems to be updating the far clip plane but not the near clip plane?

    gif to demonstrate (recorded in 2018.2.15f1)

     
  5. Gregoryl

    Gregoryl

    Unity Technologies

    Joined:
    Dec 22, 2016
    Posts:
    1,932
    Yes, unfortunately this is true. The issue has been fixed in Unity, but apparently the fix didn't make it into 2018.2.15f1 :(
     
  6. CyanSlinky

    CyanSlinky

    Joined:
    Feb 27, 2014
    Posts:
    11
    was also broken in 2018.2.16f1 but the fix seems to have made it into 2018.2.17f1, so this can be marked as solved if that's a thing.