With autokeying enabled I accidentally moved a few objects, unfortunately they now appear in the NLA editor. I removed the actions saved and reload but I can't get rid of the entries.
$\begingroup$
$\endgroup$
Add a comment
|
1 Answer
$\begingroup$
$\endgroup$
4
This behavior has been changed after 2.66a. Just tried to discuss with the designer. As explained, it is one of the main ways to prepare some places to add NLA strips from pre-made actions, and got its advantages, too.
To make them invisible, click the third toggle on the header to exclude them from displaying.
answered Feb 18, 2014 at 3:12
-
$\begingroup$ This solves the problems with objects. To remove the ones with Compositing Nodetree, I had to delete (in Python console) the Nodetree Actions. I don't know if there is another way to do it. $\endgroup$ Commented Nov 15, 2016 at 12:24
-
$\begingroup$ @MarioMey Can you provide an example? Just wonder why the compositing tree data relates to the problem here. $\endgroup$ Commented Nov 15, 2016 at 13:06
-
$\begingroup$ When we create a node group and animate something inside it, a new Action is created and appear in NLA as an Action (not yet track). When we ungroup the group... or clear keyframes, most of times, it disappears, sometimes, it doesn't. And here is where we would need to delete the empty Action. You can do it with Blender console, like this:
bpy.data.actions['CompositingNodetreeAction.001'].clear_user(). Maybe you want to delete it, but I prefer to reopen the file. See this [screenshot] (pasteall.org/pic/index.php?id=108866) before deleting the Actions. $\endgroup$ Commented Nov 18, 2016 at 2:54 -
$\begingroup$ Be careful when using
D.actions['CompNodetreeAction'].user_clear()and removing the Action likeD.actions.remove(D.actions['CompNodetreeAction']... you can make Blender crash (it just happened to me). It's better only to clear users and see what happens. Maybe you are using that Action somewhere else. $\endgroup$ Commented Nov 18, 2016 at 3:01