Blender 2.8 Crash - Translating Key Frames in Action Editor and Dope Sheet #57561

New Issue

Boomer FiftyNine · 2018-11-01T17:03:14+01:00

Boomer FiftyNine commented

2018-11-01 17:03:14 +01:00

System Information
OS: Windows 10 Professional
CPU: Intel 4770k
GPU: AMD RX480 8GB

Blender Version
Blender 2.80 Commit Date: 20181031

Description

When translating key frames in the Dope Sheet or in the Action Editor, it causes an immediate crash.
This issue is not present in the F-Curve Editor when moving the key frames. It serves as a work around.

Reproduction Steps:
//The following assumes that 'Auto Key Framing' is disabled and a simple object is being manipulated.
It is also possible to replicate this with Armature Key Frames and Key Frames for Light Colors. If it can have a Key Frame, it applies '//

In a new Blender Project File...
Ensure you are on Frame 1 of the animation Timeline Window.
Create a basic shape (cube, sphere, etc) or use the cube shape provided in the default starter view (if applicable).
Select the shape and press the 'Create Key Frame' shortcut. This is 'I as in Island' by default.
Choose Location, Rotation, Scale (LocRotScale).
In the timeline window, move forward 10 Key Frames.
Press G to translate the object to a new location in the 3d space.
Press R to rotate the object to a new axis.
Press S to scale the object to a new scale.
Press the 'Create Key Frame' shortcut again, choosing Location, Rotation, Scale (LocRotScale) again
Navigate to the Dope Sheet either by changing one of your existing views, splitting the view and opening it there, or changing to a window that has it by default
Verify that in the Header for this view the 'View Context' is set to Dope Sheet.
There should be two Key Frames visible: On Frame 1 and Frame 10.
Save the Blend File.
Right Click Select one of the Key Frames, then press the 'Grab' shortcut (G by default), and try to translate either forwards or backwards. This should result in an immediate crash.
Repeat the above step but instead press the 'Scale' shortcut (S by default).

Repeat the previous 2 steps, however this time change the 'View Context' to Action Editor. The results should be the same.

**System Information** OS: Windows 10 Professional CPU: Intel 4770k GPU: AMD RX480 8GB **Blender Version** Blender 2.80 Commit Date: 20181031 **Description** When translating key frames in the Dope Sheet or in the Action Editor, it causes an immediate crash. This issue is not present in the F-Curve Editor when moving the key frames. It serves as a work around. **Reproduction Steps:** //The following assumes that 'Auto Key Framing' is disabled and a simple object is being manipulated. It is also possible to replicate this with Armature Key Frames and Key Frames for Light Colors. If it can have a Key Frame, it applies '// - In a new Blender Project File... - Ensure you are on Frame 1 of the animation Timeline Window. - Create a basic shape (cube, sphere, etc) or use the cube shape provided in the default starter view (if applicable). - Select the shape and press the 'Create Key Frame' shortcut. This is 'I as in Island' by default. - Choose Location, Rotation, Scale (LocRotScale). - In the timeline window, move forward 10 Key Frames. - Press G to translate the object to a new location in the 3d space. - Press R to rotate the object to a new axis. - Press S to scale the object to a new scale. - Press the 'Create Key Frame' shortcut again, choosing Location, Rotation, Scale (LocRotScale) again - Navigate to the Dope Sheet either by changing one of your existing views, splitting the view and opening it there, or changing to a window that has it by default - Verify that in the Header for this view the 'View Context' is set to Dope Sheet. - There should be two Key Frames visible: On Frame 1 and Frame 10. - Save the Blend File. - Right Click Select one of the Key Frames, then press the 'Grab' shortcut (G by default), and try to translate either forwards or backwards. This should result in an immediate crash. - Repeat the above step but instead press the 'Scale' shortcut (S by default). # Repeat the previous 2 steps, however this time change the 'View Context' to Action Editor. The results should be the same.

Boomer FiftyNine commented

2018-11-01 17:03:14 +01:00

Added subscriber: @Boomer059

Philipp Oeser commented

2018-11-02 09:25:27 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2018-11-02 09:25:28 +01:00

Cant get it to crash in this simple scenario, but I'm pretty sure this is the same as #57530.
@Boomer059 : can you confirm this doesnt happen when you start blender from the commandline with the --threads 1 option?

Cant get it to crash in this simple scenario, but I'm pretty sure this is the same as #57530. @Boomer059 : can you confirm this doesnt happen when you start blender from the commandline with the `--threads 1` option?

Philipp Oeser commented

2018-11-02 13:35:33 +01:00

Marking as incomplete until we have an answer...

Boomer FiftyNine commented

2018-11-03 00:06:29 +01:00

I created a shortcut to the exe, added -t 1 and now I can translate keyframes. After googling --threads 1 and -t 1 from the other task you posted, I couldn't find any documentation on what it does and why it solves the issue. For the sake of anyone who might experience this, and in the interest of a third task not being made, why does this solve the problem?

Philipp Oeser commented

2018-11-03 09:56:26 +01:00

With --threads you can control how many tasks run in parallel in various areas of blender.
One of these areas is dependency graph evaluation (animationsystem, etc).

And while of course running more tasks in parallel usually is faster, it can also lead to bugs because different threads might read/write to the same data in an unexpected manner.

I'll merge this report into #57530, further discussion can take place there then.

With `--threads` you can control how many tasks run in parallel in various areas of blender. One of these areas is dependency graph evaluation (animationsystem, etc). And while of course running more tasks in parallel usually is faster, it can also lead to bugs because different threads might read/write to the same data in an unexpected manner. I'll merge this report into #57530, further discussion can take place there then.

Philipp Oeser commented

2018-11-03 09:56:42 +01:00

Closed as duplicate of #57530

Philipp Oeser closed this issue

2018-11-03 09:56:42 +01:00

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

Blender 2.8 Crash - Translating Key Frames in Action Editor and Dope Sheet #57561

Repeat the previous 2 steps, however this time change the 'View Context' to Action Editor. The results should be the same.