Hi James,
just tried to run nod on half sphere surface and just a tangled result.
Are there any restrictions on what surfaces the nod can be applied to.
Update once surface goes wrong all following selections go wrong as well
even those that previously worked correctly.
Cheers
Barry

Hi Barry

<< Are there any restrictions on what surfaces the nod can be applied to.>>

Yes, it will only work with 4 edged surface patches.

<< just tried to run nod on half sphere surface and just a tangled result.>>

This is a difficult one because you can't start with sphere solid, because it won't work with trimmed surfaces.
Attached is method for retopologizing a 3 edged hemisphere made by networked curves.


James

Hi James,
Ok that’s good will stipulate the 4 edge requirement in my other post.
However the concern I have is once a surface that does not meet that
requirement causes the macro to crash and the following correct
surfaces also crash.It would be good if a reset within the nod was possible.
The only way I see to reset the nod file is to close and reopen Moi ?
Anyway thanks for your help I think your macro is well worth developing.
Only wish I had the knowledge to be more help.
Barry

Hi Barry

Can you send me the .3dm file so that I may reproduce the error
and perhaps find a work around.

Thanks
James

Hi James,
I'm using the file I posted(http://moi3d.com/forum/index.php?webtag=MOI&msg=7777.987)
Just added a sphere and trimmed it on it's seam to make a dome surface and named it S8.
From the photo you can see the tangled result of the dome and when S7 was next applied
you can see it is also wrong.
I noticed the surfaces spike to drawing origin.

Barry

Hi All,

I feel nodeeditor has been neglected, so this weekend I decided I would play around with it.
Below is an unintended result of that play.

The other attachments are also outcomes of the same nod circuit:" surfTria.nod".

Have a great weekend
James

Hi
How it works ?
Thanks

Hi Finema,


>> How it work <<.

I doubt this will be satisfactory, but the short answer is as follows:

Set up nodes to create base surface tesselation of hexagons, each lofted to a centre point to make triangular tiles and flow to target surface.

The underlying hexagonal pattern is variable in row and column , While the triangles are height variable of ctr.

Hope this helps
James

Cool!

Some further development based on previous nod file

Hi James
Can you share the 3dm file and the library used in your nod ?
Thanks a lot

Hi Finema,

>> Can you share the 3dm file <<.

The nod file works on its own, without input curves or the like.>> .....and the library used in your nod ? <<.

I take it by "library" you mean my "Extensions" folder of node editor. Please find attached.
Also ensure that you are using Max's most recent NE: can be found here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=7713.608

If you mean something else let me know.

Hope this helps

James

PS I update nod file in my previous post, which should generate quicker, albeit still approx 20 secs.

Thanks a lot James !
It's very interesting.
In fact, my goal is to find how mapping a pattern on an existing model with Nodeeditor.

Hi James and Friends
First of all , the surfTria.nod ... James is really original ,
above all, the adaptation of polysurfs
to the target surface it's very cool....
I believe, however, that training can be simplified
of surfaces with a Macro (see file), as usual at this link:
http://www.mediafire.com/file/qezy7aq6qgbepb7/SimplifysurfTriaFlow.rar/file
have a nice day to all
alberto
P.S
also the file subsequently posted it's very very cool
compliments

Hi Al,

I know my node file is a bit of a mess. It was the result of pure "ad hocery".
I was just playing around to see what unfolded. No plan.

I probably should have gone back and optimised the circuitry before posting.
Thank you for doing this. I look forward to seeing how you have approached it.

James

UPDATED:

P.S. I have just started to see what you have done. I could not help noticing,
once adding up the nodes inside the expanded macros, that you have
used more than twice as many nodes for a similar result. That is not a criticism;
I know that node reduction does not necessarily reduce the computation load on running,
and in the end it doesn't much matter how many nodes it takes, if lag time between
clicking "RUN" and the generation of geometry is reduced to a minimum.In the end,
really that is all that is important.


UPDATED:
On your prompting, I have now replaced surfTria.nod file in earlier post with simplified
version (Essentially it is the my same method encapsulated in a macro):

http://moi3d.com/forum/index.php?webtag=MOI&msg=7777.1004

Hi All,

Having mapped surfaces with hexagon based tiling patterns with "HexTesselation"macro,
I am investigating the manipulation of individual tiles. Below is an experiment along these lines.


James

UPDATED problem solved (new image & .nod file)

Hi James and Friends
I saw your answer, and I checked the surfTria file again
adjusted by you ..
I must say that the macro ExTasselation does not respond in a timely manner
to the Row and Col inputs as well as the output exagon number
at this link:
http://www.mediafire.com/file/orqpc5jigc8lovh/M_ExGrid.zip/file
you will find the Macro that I have rectified, following
a method different from yours, but that presents an exact answer
between input data and output data ...
I did not have time to see the last files posted
I promise to do it as soon as possible
Have a nice day
alberto

Thanks Al,

>> M_ExGrid <<.

I look forward to looking at what you have done.
If it could reduce the generation of geometry of apertureVari3.nod, for example, that would be brilliant.

I am just glad that NE is been given deserved attention again.
James