Full Version: Nodebundle for playing with nodes

Show messages:  1-20  …  321-340  341-360  361-380  381-400  401-420  421-440  441-460  …  1841-1859

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

Hello Friends
Another exercise,
I managed to produce an interesting Texture,
applying some transformation to the Classics
Pyllotaxis ....
link:http://www.mediafire.com/file/bn1ewtm9a6c9gan/Pendant.rar
best
al

---

Hi All,
can someone tell me if this script can be made into a node.

script: /* Hide all edges */ var breps = moi.geometryDatabase.getObjects().getBReps(); for ( var i = 0; i < breps.length; ++i ) { breps.item(i).getEdges().setProperty( 'hidden', true ); }

Also how to add your own node folder and add to the Index as this as changed from the early versions.
Thanks
Barry

---

Hi Barry,
For a partial reply, my setup in windows7 is as follows:

At C:\ProgramFiles(x86\MoI3.0\ui,
I have the following:

a. subdirectory customui, (contains Max's customui)

b. subdirectory nodeeditor, (contains Max's latest stock version, 0.93)
(I did make a few minor changes such as Quartz, Different cursor, and lighter background color.)

c. subdirectory nodeeditor.93Mod, (contains Latest Mod version, with more content)

Under customui, to access item b., I have 99 NodeEdit.htm (no - sign), which has as its last line:

command="moi.ui.createDialog( 'nodeeditor/index.html', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow );">NodeEdit</moi:CommandButton>

Also under customui, to access item c., I have 98NodeEdit2.htm (no - sign),
which has as its last line:

command="moi.ui.createDialog( 'nodeeditor.93Mod/index.html', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow );">NodeEditMod</moi:CommandButton>

So either version of nodeeditor can be accessed through custom UI.

No comment on hiding edges.

- Brian

---

Hi Brian,
thanks for the reply. My thinking is to add my own node file ie:MyBits which I can add
my experimental nodes to.
The script I posted is one of Michael's but with my novice skills in javascript am not sure
how or if it can be made to work as a node.
Anyway thanks
Barry

---

I think that that is the purpose of the nodes/extensions subdirectory, a place for "third party" nodes, but I have a lot to learn still:-)

Need to re-read Max's posts when he came out with version .85 (?)
http://moi3d.com/forum/index.php?webtag=MOI&msg=7713.572

- Brian

---

Hello Barry,

find attached a script file with comments as a object for your studies. Copy it to the extensions folder an restart moi and the nodeeditor - that's it.

Have a nice day
Karsten

Attachments:
Barrys.js

---

Hi Karsten,
thanks for the node it loads ok but doesn't hide the edges ?
I connect the selected object to it but no go.
Thanks
Barry

---

Please switch under infos to visible -> no

---

I tried out the Hide Edges node written by Karsten, and FINALLY got it to work, both with the Motor2 node, and also with Barry's bottle feed screw node,
and my model of a RH screw.

At first the node declined to work, when inserted right after get object.

The Hide Edges node needs to be inserted right before the final Output node.
Also, wire the input of Hide Edges, before connecting the output to the Output node, or a recoverable error results.

"Off" in the Node Info panel means that edges are turned off, or not visible.

Karsten, you have written a very nice node.

- Brian

---

Hello Brian,

Sorry for the error - I didn't tested it already. It is only a fast draft that should show, how it is possible, to hide the edges.

Maybe someone can improve it - I haven't the time at the moment.

Have a nice day
Karsten

---

Probably, if Hide Edges is inserted just after getting the object, other geometry nodes downstream cause edges to be re-displayed?

So put Hide Edges just before Final Output node(s).

On/Off can be changed from the Info panel, while the script is running.

- Brian

Karsten, the script is superb as is!

---

Hi fellow Noders,

I am attempting to construct a parametric weave.
Attached are 2 failed attempts:
WeaveProto1 starts with a 3 dimensional point array with variable U & V + 2 in the W dimension, while
WeaveProto2 offsets 2 dimensional array in Z direction and bundles both arrays into a 3 dimensional array.

In both cases it was possible to selectively index weave in the WARP direction. However I was less successful with the WEFT weave (better with WeaveProto2, first row but not repeated)

Also even if the WEFT weave could be successfully indexed, there remains the issue of snipping the threads so that each row in both directions, is distinct.

Any thoughts?
James

Image Attachments:
weaveProto2.jpg 

---

Karsten,
thanks works great and having the ability to switch on or off is a bonus.
Cheers
Barry

---

Hello James,

I don't have access to Moi at the moment, but a look in the file with an Editor shows me, that you used Concat2 for the Points??? Concat2 doesn't support a internal organization/grouping of pointarrays. So in my opinion, it is easier to generate 2 curves for both directions and make then a pattern of the curves. Nevertheless I will try to find some time in the evening (CET) and have a deeper look in the files.

Have a nice day
Karsten

---

Hi Karsten,

Thank you for getting back to me.

<<used Concat2 for the Points???>>
I used Concat2 on num arrays only. The point arrays were interleaved with Test/BundleArray which works perfectly for the application.

<<it is easier to generate 2 curves for both directions and make then a pattern of the curves>>
Yes it is easier, but also more limited. Ultimately I plan to map point arrays to compound surfaces for topographic woven skin.

<<will try to find some time...and have a deeper look in the files.>>

Thanks Karsten, I greatly appreciate it.

All the best
James

---

Hello James,

I have tried to maipulate the internal organization x-length and z-length of the pointarray, but the PointExt-node seems that it not support this feature/inputs at the moment. So I have to improve the node first. It is also possible to integrate the feature in the concat2-node, but that would cause wiered results with inputs of different length and wouln't help here.
The picture shows what I wanted to do:



With the xLength and zLength informations, the polyLine node can seperate the pointsequences and produces independent segments.

I will try to solve this in the next days.

Have a nice day
Karsten

Image Attachments:
Problem.png 

---

Hello James,

After a deeper look into the PointExt-Node I saw, that the feature is already supported - it was my fault. I've forgot to connect yLength. Find attached an example how to solve this issue.

Have a nice day
Karsten

Attachments:
weaveProto1.nod

---

Curve node may be used instead of polyline.
- Brian

---

Hello Karsten,

Thank you for your help, it works perfectly.

To use the curve segments as discreet sweep rails,
it was necessary to alter your Construct2/Sweep node
changing processInOut to "Long" as shown below.

Nodes/Extensions/contruct2.js LINE 62
var data = this.processInOut("Long", this.multiProcess, null, null);

Will this adversely effect its functionality?




Hi Brian,
<<Curve node may be used instead of polyline.>>

Yes, polyline was only a stand in for the purpose of clarity.
Also, Points/InterpPts node before curve node gives a more pleasing result at thread ends.

Keep on Noding
James

Image Attachments:
weaveSweep.jpg 

---

Hello James,

Yes it will effect the functionality. The node is able to process also 2 or more profiles and 1 or 2 Rails. It seems that the sweep factory uses some internal autoplacement? to distribute the profile to the rail, if this change is working for you (Just a guess - would need more details). I tried to avoid this . To distribute the profile you can use something like that:



I've chosen this way to make it possible to place also individual profiles to each rail. I don't know if this way is the right one.

Have a nice day
Karsten

Image Attachments:
sweep.png 

---

Show messages:  1-20  …  321-340  341-360  361-380  381-400  401-420  421-440  441-460  …  1841-1859