Heading changes

What are the settings to get the recenter heading behaviour of the last version of cinemachine?
None of the new Binding Modes seem to do the same as the old one.

I have a car and a camera, one of the cars children (local position and rotation zeroed out) transform to follow (with three children to look at for the different rigs)

With the old version, I could step in the car, whichever direction the camera was facing and just hit the gas. The camera would follow the car. While changing directions, the camera would change them, too, unless I was actively looking from the sides (via axis control)

What I currently see with heading definition position delta:
- Lock to target on assign: just orbiting, no recentering or changing view directions at all
- Lock to target with world up: normal orbiting, no recentering at all, view changes directly with car direction (instead of waiting for recentering)
- Lock to target no roll: normal orbiting, recenters to some arbitrary angle (probably locks to target on assign)
- Lock to target: same as no roll, feels like "lock to target on assign"
- World space: recentering to arbitrary angle, feels like "lock to target on assign", but orbiting barely works
- Simple follow with world up: recentering in the right direction, always, but orbiting has almost no effect because there are no recentering settings and it recenters instantly, probably fighting against the controller input

 

I've seen the heading settings, but most of them do not work like they are supposed to, at least according to the manual, see post 1.
Simple follow is probably the nearest thing to the last version, but it isn't possible to change the wait time or recentering time. It recenters without the ability to control it.

Edit: the cinemachine version before was 2.0

 

Simple Follow is quite different from anything we had before.
We'll go over the recenter behaviour today to ensure that it's working as designed - pretty sure it is but we will confirm.

Is it possible there's some other differences on your side? Are you not able to get the desired behaviour with CM v2.1?

 

Well, it seems to me that the recenter behaviour is at least shifted between binding modes.

I don't think there are other differences on my side, since the only custom code is setting x and y axis values, but I'll make a fresh one with a simple demo scene this evening.

Not related: you are the developer behind the original cinemachine, aren't you? I love it. Even with this (maybe only in my project) wrong behaviour it is still much easier to work with than without.

 

This will follow a cube, wait for some time (not 0.5 seconds, but close) and then recenter to some unknown direction.

Edit: the direction seems to be the first direction (position delta) the car has. After changing directions, it seems to recenter to the first direction instead of the current

 

TargetForward works as expected (at least what I expected):
it always tries to look in the direction the object is facing, even if I rotate it at runtime via inspector.

 

That works, yes. If I switch between a free look cam and a standard cam with the same settings (position delta, lock to target with world up) I get the right behaviour with the standard cam and the free look cam is about 90 degrees off, which was the initial camera direction.

 

I have more than enough patience for everyone
The new script doesn't work: orbiting now is fully inactive, regardless of the recentering settings. x axis values always resets to zero, instantly and it seems to recenter all the time now.

Plus: the old object has now one set of settings for heading, orbits etc, if I recreate it, the binding mode, heading and recenter settings are visible on every body. X axis in those settings is editable.



The heading direction seems to be working now.
(ignore the direction or input axis names, I made the screenshot with a new object)

 

The extra settings are now indeed gone, calculating the heading works, too.

The non-responding x-axis is still there, though. It seems that I set the wrong value (just .Value instead of .m_inputAxisValue), but it still gets reset to 0 and I can't find where that happenes...

 

While running playmode, I can't even change "invert axis" or "input axis name", they all get reset to the
default values.

Editor:


Playmode:


The Mouse X name gets reassigned, too. Could it be, that an empty object gets deserialized constantly?

The code I was trying with the last version was
freelook.m_XAxis.Value = freelook.m_XAxis.Value + player.GetAxis ("Camera Horizontal") * HorizontalMultiplier;

and now I tried m_inputAxisValue instead of Value, too.


Edit: I think I found something.
The axis of the FreeLook gets constantly overwritten by the axis of the top rig, so my changes get discarded. CinemachineFreeLook.cs line 279

 

Beautiful. Seems to work now. There are small differences to the old behaviour, but thats probably some wrong offset or speed setting I lost while creating a new object.

 

No, it definitely was my fault. I had the wrong orbit radii. Everything behaves now like I think it should. recentering delay is now the value I set instead of roughly the doubled value. Feels really smooth now.

Thank you for your work.