Hi everyone.

I have written a new simple and useful node : "PointExt" contained into the file "basicExt.js".

It's almost identical to "Basic/Point" node and the the only difference is that my "PointExt"
exposes also the others PointArray's properties, that is AngleX, AngleY, AngleZ and pSize.

Using the great "Points2/spliPts" node (many thanks to its author) and my "PointExt" node I was able to "mimic" the behavior
of the node of which I spoke in some previous posts, that is, the node "ArrayMathTrasformations" that should do these things :

- Input :
     - PointArray
     - Math formula to apply to "X" values of each array element
     - Math formula to apply to "Y" values of each array element
     - Math formula to apply to "Z" values of each array element
     - Math formula to apply to "AngleX" values of each array element
     - Math formula to apply to "AngleY" values of each array element
     - Math formula to apply to "AngleZ" values of each array element
     - Math formula to apply to "pSize" values of each array element

- Output :
    - The resulting PontArray

With the opportunity to include into every single math formula, a reference to the fields of the PointArray structure.

Here's the new nodeeditor_0_85_mod6 archive : http://take.ms/RfzWH that contains also my new "PointExt" node.

Here's a brief video : http://take.ms/zJDVN

And here's the .nod file : http://take.ms/WHASK

Performances are rather weak but I think that with all job done in one single node (ArrayMathTrasformations) things would improve.

Best,

Hi Marco

Thank you for these new nodes. To familiarise myself with them, I re-did Max's Twist exercise
using spliPts/PointExt. A Dynamic Duo opening up limitless possibility.

Thanks again
-James

UPDATED to run on most recent NE (Jun18)

Hi James.

You're welcome!

You did a very interesting nod file.

I hope that one day, someone more skilled than me in math, want to write the "ArrayMathTrasformations" node that
should pull all these stuff together (Math node + PointExt) into a single and faster node ;)

Have a nice day,

Hi Marco
Cool Node... PointExt ,
well done , clarifies the question which I put to Karsten
best
al

Hi Karsten and Friend
By continuing the exercise CP-Catenary , I have another question from ports of;
If you wanted to split the 30 curves obtained
with 10 points each
and then reuse these 30 groups of 10 pt each
to draw as many curves (each of 30 pt)....
see attached picture ( Rhino -Gh)
Is it possible to do it ?
which nodes can I use?
many thanks
al

Hi James (again)

Here's a little upgrade of your Twist2 nod file.

Here's the Twist3.nod : http://take.ms/PcK8H

And here's some screenshot : http://take.ms/hUTiL and http://take.ms/FR9oz

I think that would be a good thing if we put at the end of all our posts with nod files this notation :
"These nod files requires <node editor version name> downloadable at <url>"

So...
These nod files requires "nodeeditor_0_85_mod6" that contains also my new "PointExt" node downloadable at http://take.ms/RfzWH

Best,

- Marco (mkdm)

Hi Marco,

Cool update .nod file.

>>i think that there's a Moi BEFORE Max's contribution and a Moi AFTER Max's contribution.<<

I fully endorse your concept of the "Maxian Calendar" as we enter year 2 AE (Anno Elephantus)

-James

Hello Al,

I'm working on that at the moment. We need a multiple pathArray for that. It was clear for me, that you will ask and I agree with you it's a elementary function. But there a 4 problems at the moment: time, the performance of the pathArray, knowledge of JS and knowledge of the elephants internals. Performance:pathArray could be replaced by a node that only gives unoriented points - the rest is still difficult.

Have a nice day
Karsten

Hello Al,

have a look in mPathArray and switch under Infos to "cross"- connect your curves and connect the output to Curves\Curve interpcurve ...
The node is very untested!!!
Have a nice day
Karsten

Hello Karsten
Excellent, it works fine
you are a " Maestro"
many thanks
have a nice afternoon
al

Hi everyone,

As agreed in previous posts, I upload here the file "nodes_V0.85_mod6.xls",
containing an updated version of the infos of all my nodes with the new "Basic/PointExt" (column Authors : Marco (mkdm)).

Here's the file : http://take.ms/2jz7Q

This xls file relates to "nodeeditor_0_85_mod6" downloadable at http://take.ms/RfzWH

P.S. Karsten, when you will consider to be stable the new "mPathArray" node contained into points2.js file
(downloadable at post : http://moi3d.com/forum/index.php?webtag=MOI&msg=7777.162),
please update a new "nodes_V0.85_mod7" version of Project Elephant and create the new "nodes_V0.85_mod7.xls" file.
Thank you.

Best,

- Marco (mkdm)

Hello Friends
It ends another week .....
another test of Boolean Intersect
works fine
Have a happy weekend to all
best
al

Hello James,

the flowObj node have to be changed to multiprocess. At the moment - only one target. The second problem is, that you try to use a rectangle as base surface. Try using SubDiv/selCenterPlane. I will have a look, to change the node to multiprocess in the next days.

Have a nice day
Karsten

Hello James,

very untested!!!

Have a nice day
Karsten

p.s.: Very interesting experiments here - thanks to all!

Hi Karsten,

One day I would like to buy you a beer!

Thanks again
-James

Hi Karsten,

I have analysed the code of your new "mFlowObj" node in an attempt to create a "mLoft" node
that can multiprocess lofts on multiple targets. I'm afraid that the task is beyond me.

If & only if this is a copy, paste & minor edit to the code you have already written for "mFlowObj" node,
and you can see the benefit of a "mLoft" node's creation, I would appreciate your expertise.

Thanks in advance, and for all you have done for me.

-James

Hello James,

looks really great. I think about the multiLoft node, but it is not so elegant to handle like pointarrays, because the additional informations in pointarrays be absend here. So we need an additional input to give them externally. In detail we need to split the objectlist members (curves) in separate groups to loft them. It depends on the workflow of creation which information are given. So we can split the objectlist by a value of curves for every loft or the amount of lofts. So we can evaluate a value from a pointarray xlength/zlength, manually or something else. Complicated, if you want to process numarrays for that, if you want individual numbers of curves for each loft. What is your idea about creating the loft curves? I don't think that the multiprocess mechanism in mFlowObj is needed for that node - maybe the short+ mode can do that, but I'm not Max.

Have a nice day
Karsten