MoI discussion forum
MoI discussion forum

Full Version: Cross Section script or node

Show messages:  1-9  10-21

From: Karsten (KMRQUS)
13 Oct 2017   [#10] In reply to [#8]
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:-)
From: mkdm
13 Oct 2017   [#11] In reply to [#10]
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!
From: speedy (AL2000)
13 Oct 2017   [#12]
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
From: Karsten (KMRQUS)
13 Oct 2017   [#13] In reply to [#12]
Hello Al,

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

Have a nice Weekend
Karsten
From: mkdm
13 Oct 2017   [#14] In reply to [#12]
Hi AL!

Thanks a lot for sharing.

Very cool stuff!

Bounding box is very useful!

Ciao.
From: Mik (MIKULAS)
13 Oct 2017   [#15] In reply to [#2]
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
From: mkdm
13 Oct 2017   [#16] In reply to [#15]
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 :

code:
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.
From: Mik (MIKULAS)
13 Oct 2017   [#17] In reply to [#16]
Hi Marco,
this is it! It works perfectly now.
Thanks a lot.
Ciao
M
From: Frenchy Pilou (PILOU)
13 Oct 2017   [#18]
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!
From: mkdm
13 Oct 2017   [#19] In reply to [#18]
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.
From: Frenchy Pilou (PILOU)
13 Oct 2017   [#20] In reply to [#19]
You are not alone in the space! :)


From: mkdm
13 Oct 2017   [#21] In reply to [#20]
:)

Cheers!

Show messages:  1-9  10-21