Hi Michael,
from time to time I have to manually shell an object that can't be done automatically due to the organic shape of the object and as part of checking the shell thickness I use the project tool to give me cross sections thro the shell.
Is it possible to have a script that would give a cross section plane thro objects that could be moved thro the object with a slider.( not sure if the computations will make it to slow?)
My second thought was to have the project tool do just the outlines and either move thro the objects again with a slider or to set the number of projections and be able to step thro them again with a slider and to have the option of keeping just the chosen profile.
Perhaps it could be done with the node editor?
Cheers
Barry

Hello Barry,
try this node file. Start the nodeeditor - select your object and do an update with the RMB on the selected node - Press run and adjust the knobs for the section position. If you need an array of cross sections - it should also be possible:-)

Have a nice day and a lot of fun
Karsten

Karsten your a star,
works a treat better than I had imagined so much adjustment.
It just shows how useful the node editor is.
So again I in your debt.
Many thanks
Barry

No problem - gladly!
Karsten

Very, very nice.
Thanks,
Mike.

Karsten....you rock!!!

What can I say ?
This is one of the coolest node I've seen so far!!!

As a sort of thank you please accept a little video of this simple experiment : http://take.ms/qEGbZ




Thank you very much.

Ciao!

Marco (mkdm)

P.S. Your last "work" also open a new kind of interesting possibilities!

Thanks!

Hi karsten.

Damn!...how fun it is ??!!!

And it has also very acceptable performance.

This is a video of "section" with a scene made by about 14000 control points : http://take.ms/G2bww




Cheers.

Animated cut sections indeed!

Hello Marco,

eehm - only a few nodes, nevertheless many thanks for the beautiful video. Maybe others need someday also a section, then no Explanation is needed.

Have a nice day
Karsten

p.s.: A quartz node in combination with a boundingbox for the range would also worth an Experiment. Important is to have fun:-)

Hi Karsten.

You're welcome!

@You : "...A quartz node in combination with a boundingbox for the range would also worth an Experiment..."

Perfect! This is exactly what I've thought while I was playing with this experiment.
An "automatic" range detection would be very very useful.

Is the same approach I have applied to my (almost done) new script "FilterCurveByLength", that I hope to publish soon,
where I calculate automatically the "min" and "max" range for filtering.

Cheers!

Hi Barry and Friends
Without taking anything away from Karsten's instructions, place the same solution
last night I realized ;
Karsten was no doubt much faster ...
This morning I took his post in the forum
file at this link:
http://www.mediafire.com/file/n4dtgc19kwwsf44/Intersect_test.rar
You may want to create a Macro Cross Section
in a very easy way-
have a nice day
alberto

Hello Al,

I saw you have already used the bounding box. That's good!

Have a nice Weekend
Karsten

Hi AL!

Thanks a lot for sharing.

Very cool stuff!

Bounding box is very useful!

Ciao.

Hi Karsten,

thanks for very useful script. I have a problem with nodeditor probably, because if I start latest (v. 0.97) nodeeditor which I extracted after a long time into nodeeditor folder and load the node, so SAVE, APPLY, RUN and STEP buttons become gray and I cannot find out the reason of such behaviour.

Thank ýou for any help.
Mik

Hi Mik.

I've already solved the same issue.

Get this zip archive : http://take.ms/ayOez
unzip it and copy the whole content into "C:\Program Files (x86)\MoI 3.0\ui\nodeeditor.v.0.97.2017.10.05\nodes\extensions"
or wherever you have the 0.97 version of NE.

You should get this content :



Also ensure that the very last lines of JS code into "index.html" file of 0.97 NE are these :

loadScripts('core','lang, compatibility, colors, geometry, main, editor');
loadScripts('nodes','macros, basic, logic, points, curves, solids, construct, transform, objects, interface');
loadScripts('nodes/extensions/libs','*');
loadScripts('nodes/extensions','*');
loadScripts('core','init, ext.*');

After that you should run all latest nodes without issues.

I solved in this way.

Hi Marco,
this is it! It works perfectly now.
Thanks a lot.
Ciao
M

Why not post the entiere node Editor pakage with the new node ?

I suppose that a Zip file of it takes 2 seconds
It's not ecologic but that avoid any headache of version for the user! :)

If user is interested by the result he copies the .nod in its repository of nodes!

Hi Pilou.

@You : "...It's not ecologic but that avoid any headache of version for the user! :)..."

LOL LOL LOL :)

Want to have fun ? Read all the posts I wrote about this argument (keep things organized, repository, versioning..)

I feel like a voice in the wilderness :)

But...no problem!

I have decided to take it easy ;)

Bye.

You are not alone in the space! :)