Page MenuHome

Hold forward is reseted in NLA
Open, NormalPublic


System Information
W10 64b

Blender Version

Short description of error
If you move with action in NLA Hold extrapolation is changed to Hold Forward

Exact steps for others to reproduce the error

  1. Open my scene
  2. Change extrapolation of SET TO HOLD action to Hold
  3. Move with action "Clip"
  4. SET TO HOLD action is changed to Hold Forward automaticaly



Event Timeline

Cenek Strichel (cenda) set Type to Bug.
Cenek Strichel (cenda) created this task.
Cenek Strichel (cenda) raised the priority of this task from to Needs Triage by Developer.

Can confirm that behavior (switch to Hold Forward if there is another action before it in timeline), would assume this is intended, Joshua?

Bastien Montagne (mont29) triaged this task as Normal priority.Aug 20 2015, 2:37 PM

Yes, that was the original intended behaviour.

That said, I can see why this can get annoying (e.g. if you're just spent time setting "hold both" on a whole bunch of strips, only to have this get reset).

I think that it is not good idea set something automatically, when I setted it explicitly.

Hello, I see that auto forward hold behaviour is still in the Blender 2.76. Will it be removed or stay? Maybe some options for this behaviour would be fine. Or if I change extrapolation explicit it will not change automatically.

For example now I am animated some vehicles. I have several clips for rotating wheels, for turning wheels etc. Some of my clips started on frame 100+ so I setted Hold. But if I move with another clips, it automatically reset this. So I have to do key on frame 0 everytime, for suppres this behaviour.

Hey, any news on this one?

Just wanted to chime in to add that the extrapolation also gets reset by the presence of action stash strips. Is this behavior also on purpose?

I'm in the middle of a motion graphics Project and have to deal with a lot of Strips getting reset with every move.

This bug would explain why I would sometimes experience weird glitchy behavior in an animation project back in 2015. Now that I have discovered it was all due to the NLA strips switching to "Hold Forward", I will have to be extremely cautious every time a change is made in this new project, unless someone has found a workaround.


Thanks Philipp. Is there any chance this bug could be fixed by one of the devs within the next few days? It is really slowing down the animation of a project which I need to submit by the 11th. It basically doesn't allow the Non-Linear Action editor to be used in a Non-Linear manner, as any update to the strips will destroy the settings in all the other ones. This forces you to have all strips start at frame 1, even if the action doesn't occur until frame 100 (essentially a Linear editing workflow).

If an early fix is not possible, I understand, but I really do appreciate your time in looking into this.


chiming in my hope that someone addresses this, as it's still present in 2.8.

its one thing to have it as a default for newly created strips, but resetting on every single move of the strip is super frustrating. what is the use-case where a user would want this value which they explicitly set overridden?

wow, it is from 2.75 :( still frustrating feature

Any chance that it will be fixed in Blender 2.8? It is nearly 4 year old report. It make many troubles when NLA editor, change extrapolation automatically.

Yes, it would be nice to have this fixed in 2.8 for sure. :-)