Search Unity

  1. If you have experience with import & exporting custom (.unitypackage) packages, please help complete a survey (open until May 15, 2024).
    Dismiss Notice
  2. Unity 6 Preview is now available. To find out what's new, have a look at our Unity 6 Preview blog post.
    Dismiss Notice
Feedback request: Understanding import & export package workflows Unity 6 Preview now available

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:
    28
    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

     
    CyanSlinky, Nov 8, 2018
    #1

  2. Gregoryl

    Gregoryl

    Unity Technologies

    Joined:
    Dec 22, 2016
    Posts:
    7,751
    It's a regression in Unity, not in Cinemachine. The next 2018.2 release should fix it.
     
    Gregoryl, Nov 8, 2018
    #2

  3. CyanSlinky

    CyanSlinky

    Joined:
    Feb 27, 2014
    Posts:
    28
    Nice, glad it's getting fixed. Thanks for the fast response!
     
    CyanSlinky, Nov 8, 2018
    #3

  4. CyanSlinky

    CyanSlinky

    Joined:
    Feb 27, 2014
    Posts:
    28
    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)

     
    CyanSlinky, Nov 11, 2018
    #4

  5. Gregoryl

    Gregoryl

    Unity Technologies

    Joined:
    Dec 22, 2016
    Posts:
    7,751
    Yes, unfortunately this is true. The issue has been fixed in Unity, but apparently the fix didn't make it into 2018.2.15f1 :(
     
    Gregoryl, Nov 12, 2018
    #5

  6. CyanSlinky

    CyanSlinky

    Joined:
    Feb 27, 2014
    Posts:
    28
    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.
     
    CyanSlinky, Nov 24, 2018
    #6