Question First to third person camera transition problems

I'm working on a third to first person shooter game. I'm using a free look camera for the third person mode and a virtual camera placed just in front of the players head for first person. (Would have done over the shoulder if I could but it's a uni project and a requirement is first person but anyway.)
I've got it set up so the main camera transitions from third person to first person when you hold right mouse button which works well but when transitioning back to third person is where my problem lies.

If I toggle the "Inherit position" option under Transitions in the third person free look camera off, the camera stays at the position that it was last at when the player was in third person and always goes back to that same position.
If I toggle the "Inherit position" option under Transitions in the third person free look camera on, the camera will move in front of the player. I'm pretty sure this inherit position works by having the camera move to the closest position on it's orbit based off of the last active camera, and since the first person camera is just in front of the player the closest position on the free looks orbit is in front of the player, which is no good.

Is there a way around this? Player rotation is based off of the cameras rotation so every time you unscope your player turns 180 which isn't ideal. Any help is appreciated!

 

I was hoping you'd reply Greg, I've been a big fan of yours whenever I have to search the Unity Forums for something about cinemachine cameras.

Number 2 worked well!

Slight follow up question, as mentioned the players rotation replies on the main camera's rotation so as the camera moves from the two perspectives the player "wiggles" a bit awkwardly. I think to counter this I can make the players rotation based off of the current active cinemachine camera. I have a reference to both the cinemachine cameras in my script, what's the best way to tell which camera is active? I saw you replied to someone asking something similar (over 3 year ago) and you said something to do with CinemachineCore.Instance.IsLive but I don't really know what CinemachineCore is and I saw somewhere else that they removed Instance.

Thanks!

 

Hopefully that works/shows the problem.

Trying to use the active cinemachine camera didn't work also, if anything made it worse.

As you can see it's a fully physics based character controller, similar to games like human fall flat and gangbeasts. We're making it multiplayer using the mirror plug in so the follow targets have to be set in the code. It might be helpful to know the third person camera now is set to follow and look at the empty child placed just in front of the characters face from your suggestion, and the first person camera is set to follow the players hips (as they're the most stable body part) and look at the top of the characters head.

How I worded it may sound like this problem only arose after adding the empty child to look at but it has been like this the whole time I've had the two camera modes working.

 

There is no animation! He just does that. The only thing not being controlled by an addForce() is the gun rotation/position, hand/arm position being controlled by inverse kinematics, and the feet/leg position also controlled by inverse kinematics, but I don't see them having any effect on this.

I haven't really touched the binding modes but the FreeLook third person camera is Simple Follow With World Up, and the VirtualCamera for the first person seems to not say binding mode anywhere(?) but in Body where I would expect to find it it's 3rd Person Follow. Which does seem a bit strange for a camera intended to be first person.. but it works...

Cameras aren't really my strong point. (which might be obvious)

 

So I switched the binding mode to transposer and used lock to target with world up which kind of acts the same but that's fine, more correct this way anyway.

BUT before I came on here I had this issue and both the cameras had the same LookAt and Follow targets so (no offence) but I didn't think changing the LookAt target to the new empty game object I made earlier would fix it. However I obviously had too little faith in you as that has fixed it completely!

I don't know how much they're paying you Greg but it needs to be more. Thank you so much!