Confusion around loading saved data about keyframes

[samisalreadytaken]

Resolved in v1.2.0. kf_save is deprecated and kf_savepath is added. See the changelog for a list of changes.

[samisalreadytaken]

kf_load reloads the keyframes_data.nut file, script kf_load() loads the named data itself. I'll probably rename kf_load to kf_loadfile to prevent this confusion.

Keyframe and path datas are separate, you'll need to save and load them separately with kf_save and kf_savekeys.

Unless you're saving the final path for the sole purpose of playing back, I suggest always saving keyframes, as you can always compile keyframe data, but cannot get keyframes from compiled path data.

[djmattyg007]

Right. Would it be worth renaming the kf_save command to make this more obvious?

[samisalreadytaken]

This difference is indicated in the command list, after compile, after save, and after load. How do you think it could be made more clear?

[djmattyg007]

Perhaps kf_savecompiled would be better?