Full Version: Nodebundle for playing with nodes

Show messages:  1-9  …  1490-1509  1510-1529  1530-1549  1550-1569  1570-1589  1590-1609  1610-1629  …  1850-1859

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

Karsten,

It is so good to hear from you.

>> I have to look to the code - every node in subD was written quick and dirty as a platform for the development. <<

Rather than spend any of your valuable time looking at code of SimpleBridge, I would more value the addition of subDivClassic functionality and alternative option on SubD node (I'd be happy with it as a seperate node if it would male your life easier).

The beauty of subDivClassic is that outputs quads which are idea for using SimpleBridge between
&
also for populating with mFlow.

If I've piqued your interest, please let me know

All the best,
James
https://www.instagram.com/nodeology/

---

Thank you Karsten for the Blend node information.
Regular MoI Blend of the Star edgeS to Circle edge, does work outside of the nodeeditor.

I'l have to look at the Blend code, :-)
and also have a look at getting Get_by_ name to use edges...

Get_by_style doesnt seem to recognize edges either...

(Haven't got around to the slicing part yet :-)

- Brian

---

For clues about edges: There are about 9 shortcut key scripts which deal with Edges of BReps, currently available.

Karsten created BrepNameSubObjects node, as used in his Fillet.nod example assemblage,
and also there is ExtractEdges node, etc.

I think some new nodes to utilize edges would be helpful...
This time of year, my play time is limited.:-(.

- Brian

---

So as of v4 beta (version Feb-27-2019), there were:
"Added methods to a scene browser item:
item.find('name') - will search all children and return an item with that name or null if none present."

So maybe this could be added to Get by name node?, in order to select edges, as children of a Brep object, for input for Blend node, or Fillet node?

(I noticed that in MoI3, named edges could be selected in Scene Browser)
Also the very old Separate Objects by Name script (v2), does not work for named edges (with the same name.).

- Brian

---

Hi Brian, well that scene browser thing returns a scene browser item, not a geometry object. A scene browser item is the UI element that makes up one line in the scene browser UI structure. There are functions you can call on it like alterStatus() which is like clicking on the eye icon in the scene browser or select() which is like clicking on the selection dot.

If you have a brep and you want to get its edges, there is a brep.getEdges() function that you can call which returns an object list with all the edges in it, does that do what you need?

- Michael

---

Thank you Michael.
That brep.getEdges() function is used in Karsten's ExtractEdges and BrepNameSubObject, so I'll try some modifications to the code to find a matching Edge name...

- Brian

---

Hi Brian, so looking through edges of a brep to find one with a particular name would look something like this:

var edges = brep.getEdges();

for ( var i = 0; i < edges.length; ++i )
{
    var edge = edges.item(i);
    if ( edge.name == 'thename' )
    {
        ...
    }
}

- Michael

---

Thank you Michael.

I'll do more study in the next few days...
I finally located the existing "selectedEdges" node, which shows up in Objects2 (nodes) Menu, in the file r2d3.js.
It seems to be outputting the various types of edges as curves...

- Brian

---

Interwoven hexagonal meshes done in NodeEditor

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

Image Attachments:
hexWeave.jpg 

---

T-H-I-S I-S S-O C-O-O-L!!!

Congrats!!!

---

Node Editor together with James skills offers unbelievable possibilities.
Respect!
Mik

---

Thank you Mik & Marco,

I am buoyed by your gracious comments and support.

>> Node Editor.....offers unbelievable possibilities. <<
Yes, it really takes MOI3D to the next level. And great fun too!

Here's my latest experiment posted to instagram together with images showing node wiring.

There have been a number of insta-viewers intrigued as to the program used.
A number of those who have stated that they have since downloaded MoI,
and a least one has confirmed his purchase. Hopefully there will be many more!

Anyway, thanks again,
James
https://www.instagram.com/nodeology/

Image Attachments:
waveSpaceFrame.jpg 

---

For some training a very not refined and optimised thing! :)
Very rusted - not used that for a long time! :(

But can be used for some combinaisons :)

The 24 position of a dices in the space by step of 90°

Better for the moment to put your object at the origine in a box 5*5*5)



like this ...



PS I don't find the function Copy ??? only a "Clone" node...



Does it possible to add some letters to the list "a, b" ?

http://moiscript.weebly.com/uploads/3/9/3/8/3938813/24poses.nod

---

Clone nodes can be chained or stacked.

Clone is contained in objects.js, a Max S. program.
A test mod was done, by mindlessly adding and duplicating a few lines, without full understanding of all the code, and seemed to work.

Darn, my lengthy post just vanished...
Often if I bump my logitech M510 mouse, some go_back is triggered, and work is lost. The mouse has too many buttons or something.

I think a mod should be added in the extensions folder, rather than messing up Max's code...

- Brian

---

Pilou, Brian et al,

Ideally clone should be abandoned altogether. It is an impediment to workflow and incidentally responsible for excessive redundant node wiring. However, it seems we may be stuck with it until Michael delivers us with instancing (v5?).

Following is an excerpt from an earlier post ( http://moi3d.com/forum/index.php?webtag=MOI&msg=7713.591 ) :

---

>>Also as I understand it, Javi Agenjo imposed a limitation on nodes
that they can receive only single inputs, but may have unlimited
multiple outputs. However in node editor, nodes with object outputs
are further limited to single outputs necessitating the "clone" node.

This limitation caused by MoI's geometry database architecture. We can't use same objects with multiple nodes. So let's wait until MoI V4 beta. I hope it will support instances.

>>However it would be better to deprecate the "clone" node altogether,
and introduce unlimited multiple outputs to object out nodes as well.
Is this something that is even possible?
It possible, but it can cause significant slowdown. Anyway I'll think about it.

---

Brian, >> A test mod was done, by mindlessly adding and duplicating a few lines, without full understanding of all the code, and seemed to work. <<

if it was possible to resurrect this node, it would go some way towards reducing the unnecessary bottleneck.
Fingers crossed,
James
https://www.instagram.com/nodeology/

---

So there is no direct Copy function ?

---

Pilou

. >> So there is no direct Copy function ? <<

There would be no need for "Clone" node if object outputs (yellow wire)
behaved similarly to number and point outputs ( green and pink wires)



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

Image Attachments:
noClone.gif 

---

Here is a simple Clone4 node, which will appear in the Objects2 menu of nodeeditor. (In MoI4Beta of course:-)

Copy/ paste clone4.js to your %AppData%/nodeeditor/nodes/extensions folder.

Also included is a simple node file "SimpleTestOfClone4.nod.

The code is 100% Clone code, with a few added lines which are slightly modified original code.

Added were "c" and "d" output pins.

Also added were two more objectlists, cloneObj2, and cloneObj3, with associated code.
After rudimentary testing, I see that color style is not preserved. Nor was color preserved in Clone node.

- Brian

Due to being an amateur programmer, use at your own risk:-)

Attachments:
NodeEditorClone4_2019.zip

---

Thanks for the efforts!

---

@ James & others
I believe that you will love this artist! Joey Camacho
https://rawandrendered.com/projects

---

Show messages:  1-9  …  1490-1509  1510-1529  1530-1549  1550-1569  1570-1589  1590-1609  1610-1629  …  1850-1859