Full Version: Node Wish List

Show messages:  1-6  …  127-146  147-166  167-186  187-206  207-226  227-246  247-266  …  407-425

James,

Yes, the anchor points are a part of the code. I was excited to see the first conversion drop cloth running, it was released for testing before setting up anchor points option. Negative numbers, great tip.

A point array would work since Max is converting the plane to a grid point array. That would skip a step.

Wayne

---

Wayne,

"A point array would work since Max is converting the plane to a grid point array. That would skip a step."

Ideally both the geometric data input and output would be point arrays, so that they delineate curves or polylines in U&V directions. Whereas curves may be lofted or networked, polylines could be polylofted. I know that this has presented difficulties with other nodes (ImgSampler), so if it is only possible to output curves, this would still be fantastic.

"Negative numbers, great tip."

Ahh! Negative gravity: this was the underlying methodology behind Gaudi's Sagrada Familia

http://www.ipernity.com/doc/jacquespfjc/13188615

Looking forward to the next beta
James
https://www.instagram.com/nodeology/

---

James,

Added the anchor index point numbers of the grid array. No error checking...
You have negative gravity :-)

Left in the error checking "file.writefile()" outputs I use to watch the program flow.

Still working on the grid array input.

Wayne

---

Cloth2.js must be inside the folder
Moi\nodeeditor\nodes\extensions\ ?

---

Pilou,

That is correct. It is still a beta program.

Wayne

---

Thanks Wayne,

The addition of anchor selection is a great advancement.
Did you have a look at using a point array instead of a plane
as the input?

I don't know if Max'x code would even allow it, but it would
really be something, if anchor points could be dynamically
manipulated (re-positioned), with the effect of stretching &
tugging the fabric.

It hints at great promise.....
very exciting

James

---

James,

Cleaned up the inputs.
The input are mostly on the node.

Still working on moving points and setting array inputs.

Wayne

---

UPDATED
________

Wayne,

Although the decluttering of the node interface makes it more user-friendly, I think you may have pushed it too far.

It would be advantageous to dynamically set gravity (as the principle force).
The other material behaviours would in most cases only be set at the outset, so it is appropriate to have their adjustments made on the info panel.

A numerical value could be input for EndFrame, which could serve both as setting the maximum number of frames in the animation, while only outputting the geometry defined by the final frame. The user could start with a high number, and then dial it back to the frame they want to output.

Also I see in Max's code that wind is treated as a vector, so there would be interface advantage in inputting as a vector, as then a single input gives direction & magnitude. I imagine, in most cases wind would not be utilised, anyway.

This is just my 2 cents,
You are doing a fabulous job.

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


Updated: I removed net width & height inputs from node because they are, of course, already inherent within the pointArray input.

PS. the inclusion of XY , X , Y , P pulldown menu is great, & although a small thing, should more appropriately be labelled UV , U , V , Pts

Image Attachments:
FabricSim.gif 

---

James,

The latest work in progress beta version. Renamed to FabricSim. Added WindVector input. Wind calculations with vector indicator. Did come across that error in the vector code where the indicator points up when it should point down on X0 Y0 Z- values . Pilou detailed it in another thread.

Wayne

---

I will must create a new section! ;)
Specialised Nodes ?

---

Bravo Wayne,

The node UI is much improved.

Regarding pointArray input: I still believe that bypassing the plane to points conversion within the node offers advantages, even if the anchor selection remains as you have it, for now.

Keep up the good work
James
https://www.instagram.com/nodeology/

---

slot Node

Michael has just now uploaded an elegant script (http://moi3d.com/forum/index.php?webtag=MOI&msg=9876.8)
that would translate fittingly into a node.



Have a great weekend
James
https://www.instagram.com/nodeology/

PS "One Side" / "Both Sides" could be a useful menu item in info panel

Image Attachments:
slotNode.gif 

---

New Slot Node Release:

Slot node is based on Michael Gibson's script:
http://moi3d.com/forum/index.php?webtag=MOI&msg=9876.8

Thank you Michael!

Copy the slot.js to the directory:
C:\Users\<UserName>\AppData\Roaming\Moi\nodeeditor\nodes\extensions

It will be listed in the Curves2 location.

It is a start/end point and radius slot. No 'both sides' option as Michael's version.

The Srf output is a planersrf function inside the node for ease of use as needed.

I would like to thank James for helping out with testing.

Wayne

---

Hi All,

Here's a raster image composed of slots making use of
Wayne's multiprocessing slot node.

Great suff, Wayne,

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

---

Does the new Elephant version 1.1 integrated on the James Thread ?
http://moi3d.com/forum/index.php?webtag=MOI&msg=9358.10

Carko Mollino = Carlo Mollino ?

I must add some new very special cool nodes on my repository! :)

---

Pilou,

Carko Mollino = Carlo Mollino ?
Yes Typo :)

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

---

:)
And about the 1.1 Elephant inside your special Nodes Updates thread ?

---

subObjs Node

The proposed node would be built on Karsten's "Objects2/NameSubObjs" node which allows for the manual selection of faces within a BRep or polysurface. It would operate in a similar way, however after clicking a face, it's index would appear in the info panel. As well there would be with the additional facility of selecting faces by inputting a number or string of numbers into index connector or typing into index field in info panel.

At the moment, "Construct/Extrude" does not work with subObj faces, so it would also need to be updated. Perhaps tapering & extrude direction could also form part of such an update.

After the face is extruded, the new face should remain selected/highlighted so that further operations may be performed, eg an extrude with taper or perhaps an inset.

This would be a major shift in NE, of working with BReps intact rather than needing to break them apart to perform operations before then joining together again. It would mirror more closely how MoI3d is used manually.

Any thoughts?

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





PS On further thought, maybe there could be a pulldown menu in info panel to select subObj types: Faces / Edges / Vertices : See updated image above.

This could be one indispensable node!

Image Attachments:
SubObjsNode.jpg 

---

Quartz2 node

While experimenting with looping in NE, I have experienced an issue with Quartz node.
The counter runs continuously draining system resources preventing the adjustment of other nodes. It would be beneficial to have options for single cycles in addition to continuous. See below



Ralf (r2d3) has written an extension version: "Quartz2" node which could be revised to include these additional timing options. It can be found in r2d3.js in the nodeeditor/nodes/extensions folder.

Have a great weekend,

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

Image Attachments:
Quartz2a.gif 

---

If one cycle has occurred, setting hz[0] == 0 should stop the if loop (?).

Would a trigger input be of any use?

Here is an incomplete draft quartz3 node, untested.
Place in nodeeditor extensions node, to add to basic2 menu.
(More code needs to be added/modified.)


- Brian

---

Show messages:  1-6  …  127-146  147-166  167-186  187-206  207-226  227-246  247-266  …  407-425