Open mic-code opened 3 years ago
In order to make everything burst compatible, I am thinking the node graph should generate a run time format, which can be a array, with all the node in the graph packed as struct, then at runtime, user can only modify the node parameter of those struct. Then iterate all the elements in array inside burst, and get a csg tree
In order to make everything burst compatible, I am thinking the node graph should generate a run time format, which can be a array, with all the node in the graph packed as struct, then at runtime, user can only modify the node parameter of those struct. Then iterate all the elements in array inside burst, and get a csg tree
Yeah it makes sense to have some sort of packed tree structure + packed data that contains all the values, that burst can just plow through really quickly
Related: https://github.com/RadicalCSG/Chisel.Prototype/issues/94
My proof of concept node graph https://github.com/mic-code/Chisel.Prototype/tree/node
Currently implemented feature, Box brush Cylinder brush Subgraph Float Property node for exposing parameter