pshipkov
solver
======
Powerful new node that allows you to iterate on any kind of data and accumulate the results over multiple evaluation steps of the dependency graph.

resample
========
Resample mesh geometry by introducing new vertices in order to keep the distance between them as consistent as possible.

resolvePointCollisions
====================
If points where spheres with given radius, the node will reposition them in order to reduce overlaps.

kdTree
======
35%++ faster now.

textureToArray
=============
Can operate on point clouds directly = much-much faster in these cases.

Scenes archive updated accordingly.

Couple of solver node examples:

[solver1] 

[solver2] 

[solver3]

[solver4]

[solver5] 
Quote 2 0
levi
The new solver node looks amazing!  Can't wait to dig into it.
Quote 0 0
rolfcoppter
AMAZING! cant wait to give it a try
Quote 0 0
Bruce Lee

Really good! The

This version of the new out of the two nodes, resample and resolvePointCollisions I do not understand how they work. Can you tell us in detail? Or, each node makes a separate case file. I want to know how they work.

thank peter !!

Quote 0 0
pshipkov
resample:
Create a poly cube. Select it. Then click "resample"  from the first shelf button.
Display the mesh vertices. Adjust the resample distance parameter. The edges will get "subdividied" in order to keep the space between points acording to the defined value.

resolvePointCollisions:
Create polyPlane. Select it. Click "resolvePointCollisions" from the first shelf button.
Points will be moved around to minimize overlap.

The two nodes operate independently, but when connected to the same data set they can grow the geometry.
To make this happen set the resample distance to specific value that introduces enough new points.
Then set the resolvePointCollision radius to a value that is slightly bigger than the resample.distance one.
This way the points will get pushed out and the edges will get longer. During the next step these longer edges will be resampled again and new points will be introduced.
The new points will get pushed out ... and so on.
In a way this is an occupational spaces algorithm.
Quote 1 0
sepu
Hey Peter, 
There is a demo version that someone can try before buying?
Quote 0 0
pshipkov
Of course.
There is a 15 day fully functional trial.
Quote 0 0
plarson
The solver node is really great! So many interesting possibilities!
Quote 0 0
ObaOba

Hello, i'm tryinig to work on the solver node. I get a deformation when changing itinerations of the plane but nothing else. i guess there are several things that i'm missing but the thing is that i don't realice how to get thous results of the expamples. Any help is very welcome.

Thanks.

Quote 0 0
plarson
ObaOba wrote:

Hello, i'm tryinig to work on the solver node.



Perhaps this will help some:
With a solver node created, first thing to do is connect the time and set the start/end frames.
Hopefully the below image is helpful. There's the initial mesh, the looping area that will determine what is done each frame, and the output mesh. You can put a wide variety of operations in the looping branch. Just be sure that the output mesh loops back to the solver's inSolve.
solverExp.png 
Quote 0 0