Timeline Bug in 1.3

[jstarrdewar]

So I actually haven’t tried 1.2, only 1.3 but this has got to be a bug.

The first keyframe in any curve insists on being at time=0 and value=1, if I scrub the timeline.

I can set these things manually, and so long as I don’t scrub, it will be fine. But as soon as I touch the scrubber, boom! It will either change the value of the first keyframe to 0,1 or add a new keyframe at 0,1 on any track with a curve.

Attachments:

You must be logged in to view attached files.

[carpe denius]

Have you tried turning “auto key frame 0” off?

[Gavalakis]

Hello,
Like Denius mentioned, please turn off ‘Auto Key Frame 0’ in the preferences. If turned ON, this option will auto key the first ‘frame’ at the current value of the property, which is helpful if you want to create smooth transition from current value to cutscene keyframed value without any ‘poping’. If this doesn’t work for you please the the option off.
I will update the documentation today with all new features and missing documentation by the way.
Thanks.

Join us on Discord: https://discord.gg/97q2Rjh

[jstarrdewar]

Yep that was the problem! Thanks guys. I see the value in it I think (it’s for entering a cutscene from an unknown state right?) but I think it’s not a good default to have it turned on, because it is such nonstandard behavior compared to the tools we are used to. Or maybe there should just be a warning on startup or a big all caps notice in the readme.

Looking forward to the docs. I’m excited about the Alembic workflow.

[Gavalakis]

Hey,

Yes, the purpose of this option is like you mention to be able to key the parameters from unknown state. With that said though, I agree that this is not the “standard” behaviour and as such I will turn it off by default for the next mini version I am about to commit soon.

The documentation is now updated by the way 🙂

Thanks

Join us on Discord: https://discord.gg/97q2Rjh

[Author]

Posts