NLA: track extrapolation auto-changes and clear keyframe crashes blender #52346

New Issue

¿? · 2017-08-11T02:50:48+02:00

¿? commented

2017-08-11 02:50:48 +02:00

Window 7, GTX 770 oc

2.79rc 6af7d7e

Pressing Alt+I while hovering over a strip's Extrapolation value just crashes Blender.
Moving the strip causes the value to switch back to Hold.

In another file, I have a strip that's stuck in Hold Forward. No matter what I do, the tracks will only use Nothing or Hold Forward. If the box and changed to Hold any change (even temp/cancelled), will switch it back to Hold Forward (or None if that was set).

In this new example file, it's the opposite except if the value is set to Hold Forward, it will work and remain that until the strip is moved (temp/cancelled/permanent).

untitled.blend

Window 7, GTX 770 oc 2.79rc 6af7d7e Pressing Alt+I while hovering over a strip's Extrapolation value just crashes Blender. Moving the strip causes the value to switch back to Hold. In another file, I have a strip that's stuck in Hold Forward. No matter what I do, the tracks will only use Nothing or Hold Forward. If the box and changed to Hold any change (even temp/cancelled), will switch it back to Hold Forward (or None if that was set). In this new example file, it's the opposite except if the value is set to Hold Forward, it will work and remain that until the strip is moved (temp/cancelled/permanent). [untitled.blend](https://archive.blender.org/developer/F706078/untitled.blend)

¿? commented

2017-08-11 02:50:48 +02:00

Changed status to: 'Open'

¿? commented

2017-08-11 02:50:48 +02:00

Added subscriber: @Ebone

Bastien Montagne commented

2017-08-11 10:18:21 +02:00

Added subscribers: @JoshuaLeung, @mont29

Joshua Leung was assigned by Bastien Montagne

2017-08-11 10:18:21 +02:00

Bastien Montagne commented

2017-08-11 10:18:21 +02:00

@JoshuaLeung is that kind of settings supposed to be animatable at all?

¿? commented

2017-08-11 11:01:31 +02:00

The Right-Click Menu says no but the hotkey says crash ^_^

.

The Right-Click Menu says no but the hotkey says crash ^_^ .

blender-admin commented

2017-08-11 15:52:51 +02:00

This issue was referenced by e6da7bb75c

This issue was referenced by e6da7bb75c8eff13185a56a144dce920b3886ecb

Joshua Leung commented

2017-08-11 15:53:01 +02:00

Changed status from 'Open' to: 'Resolved'

Joshua Leung closed this issue

2017-08-11 15:53:01 +02:00

¿? commented

2017-08-11 16:49:34 +02:00

Changed status from 'Resolved' to: 'Open'

¿? reopened this issue

2017-08-11 16:49:34 +02:00

¿? commented

2017-08-11 16:49:34 +02:00

This is actually two different problems.
Part 1 (the keyframe-crash) is/was a secondary concern.

Part 2 is the extrapolation mode (and the reason I tried part 1 in the first place).

This is actually two different problems. Part 1 (the keyframe-crash) is/was a secondary concern. Part 2 is the extrapolation mode (and the reason I tried part 1 in the first place).

Joshua Leung commented

2017-08-12 00:37:29 +02:00

Changed status from 'Open' to: 'Resolved'

Joshua Leung closed this issue

2017-08-12 00:37:29 +02:00

Joshua Leung commented

2017-08-12 00:37:29 +02:00

Without a test file to demonstrate the sitaution where it's "stuck", I can't say for sure what's going on in that case.

However, in general, only the first strip in the timeline for a datablock gets set to Hold, while all others are set to Hold Forward or Nothing. This is done for the following reasons:

The very first strip must use Hold or else jumping to a point before that strip will not evaluate the pose, and things will go wonky
Strips on which you've manually set Nothing on are left alone. It's assumed that you asked for it in that case
Hold Forward is set on all others so that you won't add a new strip at the top of the stack that ends up completely blocking everything that came before.

Without a test file to demonstrate the sitaution where it's "stuck", I can't say for sure what's going on in that case. However, in general, only the first strip in the timeline for a datablock gets set to Hold, while all others are set to Hold Forward or Nothing. This is done for the following reasons: * The very first strip must use Hold or else jumping to a point before that strip will not evaluate the pose, and things will go wonky * Strips on which you've manually set Nothing on are left alone. It's assumed that you asked for it in that case * Hold Forward is set on all others so that you won't add a new strip at the top of the stack that ends up completely blocking everything that came before.

Brad Clark commented

2022-03-01 04:37:09 +01:00

Added subscriber: @BClark

Brad Clark commented

2022-03-01 04:37:09 +01:00

Do we still need this "auto hold change" to keep the crash from happening? I and many others want it to not act this way and I would love to know if we can revert/get rid of it and not have it crash.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

NLA: track extrapolation auto-changes and clear keyframe crashes blender #52346