Blender Git Commits

Blender Git "strand_nodes" branch commits.

Page: 29 / 37

October 22, 2015, 12:14 (GMT)
Support for constants as internal node socket inputs.

Constants should never be linked to other nodes (will be ignored).
October 22, 2015, 11:45 (GMT)
Added an integer type for node sockets.
October 21, 2015, 15:24 (GMT)
Cleanup: removed unused test code.
October 21, 2015, 11:00 (GMT)
Fix for multiplicity of internal socket mapping.

A Blender bNode input socket can represent multiple internal node inputs,
so mapping for links must use a set rather than a single socket.
October 21, 2015, 09:47 (GMT)
First input node: getting basic properties of the "effected" point.
October 21, 2015, 08:33 (GMT)
Complementary separate/combine nodes for vectors.
October 20, 2015, 11:57 (GMT)
Added all the scalar math modes.
October 20, 2015, 08:46 (GMT)
Cleanup: Separate folders for compiling nodes and for executing the resulting bvm programs.
October 19, 2015, 16:11 (GMT)
Use a map to ensure proper links between internal nodes.

Socket names usually don't match the internal nodes exactly.
October 19, 2015, 14:38 (GMT)
Added a topological sorting pass to make sure nodes are compiled in the right order.
October 19, 2015, 14:18 (GMT)
Some simple math nodes to test node connections.
October 19, 2015, 10:16 (GMT)
Test of node conversion from bNodes to internal instruction graph.
October 19, 2015, 09:17 (GMT)
Next compiler step: convert internal node graph to opcode instructions.
October 18, 2015, 14:45 (GMT)
init/free functions for blenvm to have a place for global initializations.
October 18, 2015, 13:48 (GMT)
First test of the VM evaluation function.
October 11, 2015, 13:51 (GMT)
Merge branch 'master' into mesh_samples
October 11, 2015, 13:02 (GMT)
Create expression return values based on node tree outputs.
October 11, 2015, 10:24 (GMT)
Invoke the BVM expression eval for effectors.
October 10, 2015, 08:48 (GMT)
Integration of BVM into the effector system for using programmable expressions there.
October 10, 2015, 08:26 (GMT)
Use a dedicated struct EffectorContext for storing results of effector
lookup rather than a plain ListBase.

This paves the way for future inclusion of evaluation context info in
the EffectorContext struct, and hides some of the annoying details of
the ListBase double dereferencing.
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021