jacqueslucke / animation_nodes Goto Github PK

View Code? Open in Web Editor NEW

2.3K 172.0 342.0 6.8 MB

Node based visual scripting system designed for motion graphics in Blender.

License: Other

Python 65.17% C++ 5.61% Shell 0.04% Batchfile 0.03% GLSL 0.03% Cython 29.14%

blender python animation-nodes

animation_nodes's Introduction

Animation Nodes

Animation Nodes is a node based visual scripting system designed for motion graphics in Blender.

Download the latest version from the Animation Nodes website. https://animation-nodes.com/#download

Get started with Animation Nodes by reading the documentation. https://docs.animation-nodes.com/

animation_nodes's People

Contributors

Stargazers

Watchers

Forkers

jasperges brentini nikos-prinios antoniusf theheurist wardrums vvfickvv 3delic ikesters allkhor guy-lateur yousifalyousifi brookman og76 yorslosilla primitivahallon andrestr02 raducius fourks davidmueller13 ainovaz peca3d leopardob bitdifferent game-artist-rafael-nascimento peter1000 hapit mx1001 juantresde unwarysage ion12 up4 googleweb chrisatbest mistajuliax ikovic-lab jeske xetrocoen prakashketkar s-light hypearena ai4vj s-leger yuen33 bjoeris diramazioni bikarjx alansalihi darbinieks heyunpiupiu ricardoroehe 3rawkz rjmcguire whaison dolphindream raulpercy scorpion451 resultant-gamedev printerkiller olumideolufy29 bertvandenbosch pauliegillett hejia-v disarticulate pyrokinesisstudio satishgoda multiabhay head-zonkstudios miszla viddyozeapp gfcprogramer saeedmoin clockmender leoncheung fox36 martialgallorini uberslo1369 souvik025 silverx6000 dadaromeo slothropsez m0nkeybread lawtonjohn ktakahiro1729 drakedarky anonymousindian follower dteurope mrandreastoth 765563652 tewodroes luoxz-ai dreadchild j1930021 misiewiczradoslaw creativedesigner3d aleua abhaysharma-tp tomatoma2 ipaddilectio

animation_nodes's Issues

Modifier output node suggestion

Hi Jacques, thank you so much for developing such a great and powerful tool! I really love to play with it and show people how wonderful the works can be done with it.

Here I noticed the modifier outpout node has been changed to a more readable way for uses to input by typing. It's cool for sure. However I just feel that the old design can also be effective, since we can simply copy and paste datapath into the field, no need to type anything else. But I think both will work fine for different people.

So I suppose maybe it will be better to make a toggle there so that we can choose which way uses perfer to use? Or, just add the old datapath field (you also call it Attribute before), so when it contains any texts in it, the node will automatically make the other way turns gray. Just a humble thought though. FYI.

better interpolation system for mix vector node

print code generation time

cleanup interpolation socket

fake user issue

unified converter node

find reason for 'internal state error: this should not happen'

setting viewport color maybe..

replicator: change to object mode before unlinking

function not found in compiled code object (works if I execute it the normal way)

import bpy

def node_111_Function(output_111):
    global nodes
    node_112 = nodes['Debug.001']
    output_112 = node_112.execute({ 'Data' : output_111['Objects'] })
def node_108_Function(output_108):
    global nodes
    node_109 = nodes['Sub-Program.001']
    input_109 = { 'Amount' : node_109.inputs['Amount'].getValue(), 'Objects' : output_108['Objects'] }
    for i in range(input_109['Amount']):
        input_109['Index'] = i
        node_111_Function(input_109)
    output_109 = input_109
    node_110 = nodes['Debug']
    output_110 = node_110.execute({ 'Data' : output_109['Objects'] })
nodes = bpy.data.node_groups['NodeTree'].nodes
node_105 = nodes['Object List']
output_105 = node_105.execute({  })
node_106 = nodes['Sub-Program']
input_106 = { 'Amount' : node_106.inputs['Amount'].getValue(), 'Objects' : output_105['Objects'] }
for i in range(input_106['Amount']):
    input_106['Index'] = i
    node_108_Function(input_106)
output_106 = input_106
node_107 = nodes['Debug.002']
output_107 = node_107.execute({ 'Data' : output_106['Objects'] })

viewport color node

improve layout of debug node

matrix sockets

access to different time on baked sound

better categories for nodes

Something about Sum Elements node

Apparently,the Start value is based on index, while End is actually something like "Items" or "Count". This is a bit confusing. We may consider to name it another way?
When Summing strings, it misses update sometimes. (Or, it just doesn't function in this mode by design?)

FYI.

sound bake node as socket

Performance influened by unconnected nodetrees?

It seems that the unconnected nodetrees (those already in the nodetree list) will influence the performance with the current one?

I found that the more and complicated nodetrees I created, the slower operation responses I got.

To test it, just simply duplidate the current nodetrees several tiimes. And then link or unlink any noodles in the connected one.

colorify node sockets

Make nodes inputs and outputs more clearly differentiable with their color coding, also probably could add a color reference in their add menu.

Avoid repeatable adding selection

When adding objects from selection, it seems that there is not yet a filter to ignore those items that are already in the list, something like this:

I\m not sure if it will cause performance reduction, it just can mess up the list easily. And, I guess a "Remove All" or "Clear List" button will also be great.

BTW, You can see from the image above, I've also tried removing line "row.scale_y" for icons (not pulled though). I'm not sure why that was set to 1.3 by default (to avoid misclick?), I think its OK to set it back to 1 and things look more algned than before, isn't it?

put some node inputs in the 3d view

speedup object output with in-line-execution

Difference between Attribute Output and Modifier Output?

It seems these two nodes got little difference on function, they can both control attributes in or out of modifier attributes. Maybe we should abandon one of them and just call it Attribute Output?

improve random number node

additional seed
speedup

replicator node cleanup

should be possible to change the mesh for individual objects

Class name / bl_idname

I propose that you add prefix to all class names since for example FloatInputNode is a very generic name and all class in blender are registered in flat namespace in bpy.types.
Changing breaks existing node trees but better sooner than later.

implement group nodes -> reusable node networks

Wrong node update order

Needs a new algorithm that handles such cases correctly.

easier access to materials with a node

find a better name for this addon

"+" button on "Loop" node

It would be nice for Loop node to have the + button, as well, which is a quicker way to add a new Loop Start node conveniently. Just like what the one on Loop Objects node does. 😸

rename sockets

finish custom node implementation

cleanup Object info node (utils functions)

implement groups and loops that iterate throught each object

perlin noise

subframe support for sound input

set shape key influences

in-line execution possibility for some nodes

Using unique names for nodes of different types

Hi, since I got used to add nodes by searching, I think this would be a much quicker way to add nodes (for me at least :P). However, just found it didn't work well with the recent changes.

You can see from the screenshot, I can hardly tell which "Animate" or "Math" is the one I really want. So I think unique names for them will be helpful here?

in-line-execution. to many getValue() calls

Rename the files from animation_nodes to something else

deduplicate code in loop nodes

An idea on debug nodes.

A humble idea: We can consider Debug node similar to what Viewer node does in Compositing editor. So how about adding the quick shortcut for it so that we can quickly connect it to any output sockets within 1 sec? I mean, in Compositing editor, we can simply add / link a Viewer node to another node by holding Shift Ctrl then clicking. Probably Animation Nodes can do such magic? :P

Dragging toggle feature doesn't work well?

While in other area of Blender UI, we can toggle multiple things by dragging over adjacent items (such as toggling the visibility of many objects in Outliner), but the experience seems doesn't work farely well with nodes like "Transforms Output" or "Copy Transforms", which are with many toggles, that are ususally needed to be toggled by the internal quick toggling way.

EDIT:
Toggling in N panel would get better a bit, but still failed sometimes, occasionally.