Nudibranch

Comment

Comment by Marios Tsiliakos on March 5, 2017 at 4:52am

Hi @K YANG,

you can feed the same amount of sliders or fixed values in the range input of the component. for instance if you have 3 curves you can have a different range of influence for each one. this rule is working as per the longest list arrangement logic. so if less are provided the last one is repeated for the rest.

then, and providing that the ranges overlap you can choose the way the way that the values from each are accumulated (ie averaged, minimum etc. You can also choose what happens to the parts of the filed collection that are not affected by the ranges.

try the generic examples(coming with the installation package) by changing the initial values to see the different effects.

Ta,
M

Comment by K YANG on March 5, 2017 at 3:16am

Hi Marios,

I am new to here and thanks for developing this plug-in.

when using "CurveAttractor", I wonder whether I could give different weights to different curves?

Thanks!

K

Comment by Marios Tsiliakos on August 27, 2014 at 2:45am

Ty Ewa,

I have re-written most of the code and the components run significantly faster now. Hopefully there will be an update in the following months.

Best,

M.

Comment by Ewa Kus on August 26, 2014 at 11:10am

Marvelous plug-in, thank you Marios:)

Comment by Marios Tsiliakos on February 6, 2014 at 11:24am

@Ivan

Thanks for your kind words.

Range is variable if you connect more sliders to the range input. I'm afraid that force and iterations are global for the moment. It would make calculation time really slow if I made those locally defined. But I will keep an open mind about that.

A simple workarround for the time being is to connect more twirl attractors to your definition and add the resulting vectors. You will get the result you are looking for.

Best,

M.

Comment by Ivan on February 6, 2014 at 2:50am

Hi Marios,
Just downloaded your tool, that's really great!
I have a question about the Twirl Arrtactor: is it possible there to control range, force and iterations for each point?

Comment by Marios Tsiliakos on May 20, 2013 at 4:49pm

Hello Igor,
Thank you for your feedback.
I found the bug in the satellite component. (it isn't that it doesn't work with one item, it seems that its missing certain data types like GH_box. so if you reference a box from rhino(1 single item) it works, if you input a mesh from gh it works (ie mesh_plane) but if you input a single box, or sphere or cone it doesn't). Thanks for pointing that out. Will be fixed in the new release 002.
For the min/max value:
The meaning of a minimum value is that every point outside the attractor's range gets the minimum vector value (i.e 0.00 or bigger), so when the attractor is far away from the grid and the points are outside of the range of the attractor, there is no min value (is null)thus no vector to be added (so the points disappear).
in the case of the max set to true he maximum value of all the points within the attractor's range is being added to all the points outside the attractors range so there are no null points a valueis constantly added. However in this case it would be useful to set a conditional in the code so whenever the points are all outside the attractor's range the maintain their original coordinates. so thanks once again for pointing this out..

Best,
M.

Comment by Igor on May 20, 2013 at 9:30am

Hi Marios,

thanks for great tool. But....

Could you explain the logic of a attractor range?

In my example when points out of attr range and cheked Max it's allright(more or less), but when cheked Min all values are crashed.

And why Sattelite component dont working with one geometry?

Attr_range_problem.gh

Sattelite_problem.gh

Comment by jorge sainz de aja on May 7, 2013 at 8:21am

Comment by Toussaint Jimenez Rojas on April 7, 2013 at 11:32am

Humm Marios Thanks For your invitation, i will going to test it  congrats cuz looks interesting 

• ‹ Previous
• 1
• 2
• Next ›
• Page