Cinemachine Automatically Setting Camera Far Clip Plane

Been running into an issue where the Cinemachine Brain script is setting the Far Clip Plane of the camera to 5000.

This seems like way too much and I'd like to have control over it. Is there any way to stop Cinemachine from doing this?

 

Oops that makes sense, I forgot to check there.
I really appreciate the quick reply!

 

any way to change that in runtime? or to disable cinemachine overriding this parameter so i can control that from a custom script ?

 

im having the exact opposite problem.

id like my virtual camera set at 5000, but it keeps reverting back to 1000 at runtime.

my other virtual camera and freelook are fine...

 

yep. you were right. i gave it another look. it turns out i had a BOLT lens setting node buried in my Zoom code macro which defaulted at 1000.

Thanks, Greg.

 

Hi, I have a similar problem with a large scene. using the starter third person asset. If I add a CinemachineVirtualCamera to modify the camera's clipping plane, I must disable the CinemachineBrain. But the third person controller is then stuck in place. If I thick the CinemachineBrain back on, it moves again but with a clippingplane automatically blocked at 500 meters. What can I do ? Thanks in advance.

 

I'm using the First Person Core Template in Unity 2021. The camera far clipping plane is locked at 500. How do I change this value?

 

Thank you very much Gregoryl!

 

Is there a way we can just tell Cinemachine (at an application or Brain level) to not modify certain properties?

We have a camera stacking setup and very particular and controlled setting of near/far planes, and it shouldn't be the content people (artists/designers/cutscene team) that need to remember to set (or update) every single VC. The VC should instead instead first defer to some 'authority' (Brain, or app wide CM settings) before changing such things.

Is this possible?

 

Thanks for this, that does what I need for now, I'm able to set the output camera settings to what I need.

For context, and due to our particular setup with cameras, it's not ideal that those authoring the artistic side of the camera's need to be aware of all the technical/performance related topics, such as very specific near/far settings. They should just focus on the creative side.

Since there are far more VC's than the single Main camera, it's also not practical to manage this at a content level. Thus was hoping to be able to set project wide restrictions to what a VC is allowed to modify. This would allow content people to go on being creative and the tech/perf team to feel confident a VC isn't accidently breaking things.

Cheers!

 

The dirtiest way to do this is put an Animation Legacy component on an object in the hierarchy that's above all your CM cameras, and then set a keyframe at the beginning of animation clip that's the value you want, for each camera's property that you want. This overrides any and all other attempts by Unity systems to modify this parameter's value, and will "lock" the value in the Inspector, too, so user's can't accidentally modify it.

Couple of steps that need to be taken:

The clip to do this needs to be added as the default clip for the Animation Component, and placed at the top of the list of Animations in the Animation Component, though when doing this trick you'll likely only have the one clip in this list, but it still needs to be in the Default slot, too. Just in case.

This is an ugly, tacky and hacky way to achieve this lock, but it works like a charm, for me, and provides a very easy place to edit these values, and to put lots more in this lock state in this single place. And swapping clips means swapping values. So is quite a powerful "preset" mechanism.

And you can easily, for example, lock unique clipping plane values to each unique camera, as needed, and each will be in this list of modified/locked objects, in the Animation Clip, whereby it's as simple as clicking on the Animation Clip's name of this camera to select it in the hierarchy for further adjustment/assessment/creativity.

 

7 years later and this solved my issue. Thank you!

 

thank you so much brother