Bodysoulspirit's picture

@Bodysoulspirit

Bodysoulspirit's picture
@Bodysoulspirit posted a new Feature Request, “Layer to 3D Object & 3D Object to Layer

Layer to 3D Object & 3D Object to Layer

Hey guys ;)

Wanted to know if there is a reason why something like Karl Henkel both his "3D Object to Layer" and "Layer to 3D Object" nodes are not included in the stock nodes ?
Using it quite often to bypass some limitations (Use Copy 3D Object with Material with layers), having scene based compositions not having to select different Z-axis to blend nicely etc.

Once "Allow custom node paths" will be implemented it won't be really a problem anymore, but until then, it's sometimes complicated to share compositions with custom nodes.

Thanks ;)

Component: 

Tags: 

Bodysoulspirit's picture
@Bodysoulspirit commented on @marioepsley's Discussion, “JSON data streams

Yes maybe encoding the values in another way could help.

And if Get Tree Content would export a list of values (or a space separated values block of text) we could use that.

Another method is to use split text (joined composition), maybe that would work as a workaround, test what is faster :

Bodysoulspirit's picture
@Bodysoulspirit commented on @marioepsley's Discussion, “JSON data streams

Yeah, and again, maybe "Copy Layer" will be faster than Process List too.
And you also have your layers size set to 8. 100 layers with an 8 width & height could be pretty heavy anyway I guess.

Bodysoulspirit's picture
@Bodysoulspirit commented on @marioepsley's Discussion, “JSON data streams

Haha our posts crossed.

Maybe if you use "copy layer" instead of a second "process lists" node to parse the XY values it would be faster ?
Maybe Iteration: Turn most nodes into iterators by allowing single-value ports to accept lists will also be faster for this.
But still, maybe the team has a better option ;)

Bodysoulspirit's picture
@Bodysoulspirit commented on @marioepsley's Discussion, “JSON data streams

I'm not a tree pro anyhow so maybe there are way better solutions, or maybe we could need some more nodes, some more conversion nodes or nodes to handle lists of trees, but if 15 fps allows it you could for example use :

Pages