>>Caused by my inadequate english I misunderstood some of your statements<<
To clarify I made simple sweep nod file attached.
Sweep factory allows multiple profiles, giving result in image below,
but sweep node only recognises the start profile. see simpleSweep.nod
Given the recent significant developments
redoing the test , I think for exactly orienting objects
in target areas, you could use Offset and then Sweep
unfortunately, currently with only one profile.....
It would serve a Sweep Node MultiProfile and whi not MultiRail...
or, more simply use the actual Loft Node
with a Node similar to (Bundle Pts ) but that groups
curves instead Point-
I've been clear......?
I hope you understand.....
best
al
PS-Sorry for my bad English
I do everything to be understood ...
but it is not always so simple
I have to thank San " GoogleTranslation "
>>>with a Node similar to (Bundle Pts ) but that groups
curves instead Point-
my intention is not to do a seperate Node for that, rather put the curve sequences directly to the loft node (variable number of inputs). The only question is: A new node or RMB option to the actual one. I don't know - I have to look at it. That would solve the problem in a first step. A seperate node that extracts all faces is also useful. There is also a arraygem factory in the API which can do something for us, but I don't know at the moment, how to use it. For the improvement of the sweep node I have to think about it first - It depends on the possible workflows which input variants are useful and what the other nodes have to do for that. It's like the loft node or the pathArray- in a first step everything seems to be good, until you realize the limitations for a special workflow. The offset node is unfinished also. MultiIso node has also a bug, the names of some nodes are not to be understood intuitively ...
Hello Karsten Friends,
another test of new mpatharray-Node
there are several inactive output ,
activate them to see the different behaviors
shown in the attached picture...
<Karsten>
I think the changes to the existing Loft
they can be made at the entrance of the data in the
Node-
Just specify how to order
input ....
I've tested Al's CP-mPathArray - very cool, but my 5 year lenovo G575, that I use for programming, is a little bit slow for such things. Anyway - I've tried to include the RMB option into the mLoft, but I have some problems with the locking mechanism of the input slots - I have to take a deeper look in JS and Max code. So there is a little bug in the new node, that I have attached (in "normal" mode it is possible to remove the target slot ..). So it's a draft, that I have to improve. When I understand the code, I will fix it and post a new one. And we have to think about the compatibility of your posted examples, it is possible that some of them have to be reworked in the future.
It would be a pity, if they wouldn't run in newer versions.
Hi Karsten
I saw the new node and advances
occurred ....
You are truly priceless for the effort they monsters.
Unfortunately these days there it will be able to analyze
and understand the improvements occurred
patience.....
I hope to do next week
Have a nice day
al
>>mLoft2....So it's a draft, that I have to improve<<
I was just wondering, when you return to revise coding of mLoft2
if it would be possible to include polyloft capability
(i.e. selectable separate facets).
Or if easier to create a new mPolyLoft.
The below image may clarify my request.
I want to be able to address individual quads.
I don't want to come across as someone who is never satisfied.
I hope I have already expressed my gratitude for all your early xmas gifts.
I couldn't be happier, with toys I have already!
Hi Karsteen, Burrman, AL, James and all the other smart guys of Project Elephant,
I post here my reply to this post of "wastzzz" where he said (http://moi3d.com/forum/index.php?webtag=MOI&msg=8192.1) :
"....I don't understand anything, where is the last version, what is nodebundles, there is no appropriate thread or instruction.
This forum organization is a pain. My head hurts. No offense"
Well, I totally agree with "wastzzz".
Although I have already played a lot with Project Elephant, now I'm really doing confusion...
Karsteen, Burrman, AL, James and all the other smart guys of Project Elephant, could you please, if you want,
follow the suggestion that I gave you some days ago ?
That is :
I think that would be a good thing if we put at the end of all our posts with nod files this annotation :
"These nod files requires <node editor version name.zip> downloadable at <url>"
For example : "These nod files requires "nodeeditor_0_85_mod6.zip" downloadable at http://take.ms/RfzWH"
This little extra annotation to our posts will greatly help us to understand and test all of your excellent experiments.
Hi Pilou
the video shows the performance achievable
with Kangaroo Plug-in ,created by the genius of Daniel Piker for GH/Rhino ...
It is a simulator of movements, mass ,gravity ,acceleration,
etc etc applied mostly to the Mesh ....really amazing ..
Perhaps using mathematical data only (Algebric and Trigonometric)
It fails to do something like ...
personally I see it very difficult
best
al
I want to post my last snapshot:
For those are interested in - extract the file in in a subfolder and copy the folder nodeeditor.v.0.85 to e.g C:\Programs(x86)\Moi\ui\. After that, start Moi and go to Options and Shortcut keys. Click the Add button. Enter a key e.g. F8 or Alt+N. Under command place:
moi.ui.createDialog( 'nodeeditor.v.0.85/index.html', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow )
Now press close - and enter your shortcut key. - Hopefully it works. In the attached file nodes_V0.85_mod8.xls is a short overview for the additional nodes.
To start working with the nodeeditor press the right mouse button. Hold down and chose a node. A double click on a node opens the info panel on the right side - same result as pressing the info button on the right upper side and click to the node. Most of the nodes have inputs and outputs. At the moment there are three datatypes:
numarrays -> for numbers and arrays of them
pointarray -> for points and sequences of points
objectlists -> geometrical objects like points, lines, curves, bodys ...
Boolean -> at the moment unused
The node is like a blackbox, which takes inputs of the mentioned datatypes and processes them to an output. Outputs can be connected to the input of another node. Outputs of type numarray and pointarray can be connected to multiple node inputs. Objectlists can only connected one by one. If you want to connect to multiple nodes, you can use a clone node for that. To connect outputs to inputs, press the left mouse button on the output and drag the cursor to the input you want to connect. Release the mouse button over the input and Output is wired to the input. The color of the wire depends on the data type which will "transported". Under the basic Menu item (RMB) is a Output node that brings the data to Moi. To start the processing, press the start button. The Apply button pushes the data/geometry permanently to Moi.
I'm not a native speaker, so maybe can take the infos and bring them back in a improved version.
Hi Karsten and thank you very much for your post and your new "unofficial" version of Project Elephant!
I have seen that the archive contains also all my nodes and all the other nodes written so far.
That's a very good thing because it's exactly what I meant when I suggested to start to be more clear and plain
when we present new nodes to the community.
This is a good starting point for next unofficial versions of Project Elephant.
I think that this way will greatly help anyone to play with the Node Editor :
an updated zip file containing the new version and a .xls file for a basic documentation.
In the last few days, thanks to some sporadic spare time, I'm testing and coding a new node dedicated to PointArray elaboration,
and I think that soon I should be able to publish a new "unofficial" version of Project Elephant containing this new node.
CP_PanelShellKaesten.nod
