Full Version: Nodebundle for playing with nodes

Show messages:  1-7  …  1788-1807  1808-1827  1828-1847  1848-1859

Thread Split: Some posts in this thread have been moved here

Thank you James, for the clarifications, corrections, explanations, and link to Pilou.

They help with my better understanding of the node. What it could do, how it could do it.

I'll try and make some corrections, and elaborations, so as to not mislead.

The weaving was an attempt at an example.
If each input array represented (points of) one warp thread...
Output might represent weft thread location, for additional up/down weave information, somehow ???

- Brian

---

Hello James,

I tried to recreate what you have made here: https://www.instagram.com/p/CbAAG0Xrssv/

However, for me, it doesn't work! I have problems creating an Array with Knob

.nod file is attached.

Could you please help me through it?

Attachments:
Phyllotaxis Arrangement of Cones.nod

---

Psygorn,

The equation that feeds into "Z" input of point node should be:

sqrt(a-pow(sqrt(b),2))*c

Also the cone needs to be beefed up in size, & importantly
have a negative number for "Height" input so it points outwards.

I used "Radius": 15 "Height" : -35
James
https://www.instagram.com/nodeology/

---

Hi James,

Thank you for your reply I am using sqrt(a-pow(sqrt(b),2))*c to feed into "Z" input of the point node now. however, I still don't get your result!

No need to mention I changed cone specifications to what you suggested there appears only one cone!

My question is that I see your "shiftDublicate" node says "numArray" while mine says "In" what am I doing wrong?

---

Psygorn

Not sure why it is not working your end, because your NOD file with
the recommended changes works for me.

You could try replacing "shiftDublicate" node with "Basic/Progression" node.

In this setup, they are effectively the same, and "Progression" node
would be the more obvious choice, however when I built this circuit
I was initially attempting something different from what I ended up with.
Sorry if this created confusion.

James
https://www.instagram.com/nodeology/

---

"ConnectPoints" node
Update: range mode

Address: Curves2/ConnectPoints

Attachments:
ConnectPoints.js

---

An update on "idxSelect" node
Inverse mode added.

Attachments:
idxSelect.js

---

MO,

Thank you very much for update of "idxSelect" node.
This incremental change will have a profound effect on the usability of NE.

There is another node that could be revised to great effect.
Less incremental change than change to increments.
Please see link below:
http://moi3d.com/forum/index.php?webtag=MOI&msg=9581.3

There several ways this could be achieved, but perhaps the easiest would be to introduce a RMB option as per image below


What do you think?
James
https://www.instagram.com/nodeology/

Image Attachments:
knob.jpg 

---

I'm glad you liked it.
I did take a look at "Knob" node.
It looks a bit scary to be honest! :)
Maybe I can add a "step" property, but not sure.

---

Unfortunately I couldn't find a decent way to do this, But somehow I managed to reach a result.
I added a "step" property.(Default: 1 But it can be negative too)
It can increment by step number, but the incremental mode works only with mouse wheel.
I post it here in case someone wants to use or improve it.

Attachments:
Widget_Knob.js

---

"ArrayGem" node
Inputs:
Object: Objects + an optional base circle
Path: curve/curves
Surface: To set objects orientation (optional)



Address:
Objects2/ArrayGem

Attachments:
ArrayGem.js

---

"SurfaceNormals" node
Moved here
https://moi3d.com/forum/index.php?webtag=MOI&msg=9581.321

---

Show messages:  1-7  …  1788-1807  1808-1827  1828-1847  1848-1859