the Problem is not in your node - it's the Feedback effect of the nodefile itself. The Output of collision becomes, by detours to the Input.
I think that is catched by the nodeeditor to avoid infinity running. A Problem that has to be solved for optimisations or by a node itself.
I think about it, nevertheless we have to ping Max for his opinion.
Have a nice day
Karsten
p.s.: I don't think that you Need a new node - and try to avoid boolean in nodeeditor progamming - Max has made a decission to use numarray for that Look at his logic nodes. At the end it's the same. Only difference you can directly calculate with a result of a logical comperation.
Hi Karsten,
attached are my Barry/Collision node and the Collision.nod file.
It's a work in progress.
Am I using a Boolean in the node ?
Thanks for the clash.nod will try to see if I can use it instead but
not sure how I automate the movement yet.
Cheers
Barry
Cool nothing to translate for this one... a miracle! ...
... but how do use it? :D
(Collision tittle is in red (?) )
Must I use also the Barry.js and where i must put it ? Normal folder or extensions ? or...
Hi Pilou,
it's a work in progress at the moment so the final aim is to auto place objects touching or with a given gap.
If you place Barry.js in extensions you will be able to try the Collision.nod.
Draw 2 objects make them overlap and press run ( close error report ) and they will automatically move till they do not overlap.
To reset the quartz node value as to be manually reset to 0.
Cheers
Barry
Hi Barry,
I cannot say if "feedback" is a problem, but note that many months ago, near the beginning of NodeEditor,
I read a post in Grasshopper, of a way to do "feedback," wiring,
which as far as I know, is not normally possible...
Back then, I think I posted a brief sentence about it...
- Brian
ps: General information: The barry.js file goes in the extensions folder of nodeeditor.
Hi all.
My little contribution in the NodeEditor.
Added: Arc3pt, ArcCenter, Circle3pt, CircleDiameter, Ellipse3pt, EllipseCenter.
Allowed: node - test, and me to criticize :)
Vladimir.
It is hard to see how they could be improved upon,
except maybe compiling them into meta-nodes with RMB sub-options.
Also it would be a real improvement if arcCenter node emulated the tool's function
of having "start point" & "angle" options"
Nevertheless, as they are, they will be extremely useful,
so thank you
James
PS one thing you should probably consider is putting them under
their own menu heading "Curves2" below the line.
It has been agreed practice that Max's nodes are sacrosanct,
& extension node are kept separate.
Under extensions, same place construct2.js is located.
- B
By the way, while playing with the stock Construct/intersect node, with a circle and a rectangle, the stock intersect node does not yield the same
results as the MoI intersect script.
Hi Brian,
I did a Google search and found grasshopper as a plugin called Hoopsnake that allows feedback.
This is the link http://www.grasshopper3d.com/group/hoopsnake.
Perhaps Max or Karsten will have a look and see if it's possible to create something similar.
Cheers
Barry
Hi Barry,
Yes, hoopsnake. I wonder if nodeeditor has "feedback" detection code?
There is also a Grasshopper way to feedback to (say multiple) sliders, to increase sliders, potentially up to their maximum,
written by the author of grasshopper.
I'll post the link tonight.
Maybe sliders could have range multipliers controlled by the bounding box(s)...(?)
Hello Barry,
yep! Thats exectly what I thought. Possible to make global container to place results and read them in a next iteration back. Ralf - thanks for the contribution - has used something similar in the stream node - only problem - more than one of this node.
I need to have a deeper look - next days.
clash.nod
