Slow move component

Hi,

I've got this definition which generates 81 rather simple surfaces, and a move component that places each one of them so that they are equally spaced.

When I connect my surfaces to the move component, the laptop starts a-humming and puffing and takes forever to generate the new surfaces.

Then, the whole definition becomes ultra-slow and it's tough to manage to bake them.

Any idea what's going on ?

Cheers,

Attachments:

Slow move component.JPG, 206 KB
Generation toiles sur Wishbones-Module De rive.gh, 30 KB

Replies to This Discussion

Permalink Reply by Armin Seltz on March 17, 2015 at 3:30am

Hello.

It seems to be related to the factor with which you multiply the vectors. I tried reducing it to 70 and then 700 and it was working just fine, calculating in less than a second. You generate very large values (the highest is 560.000), which might be too large a value for Rhino to handle. I am not aware what the exact limits are, but you seem to have hit one.

I suggest you scale everything down quite a bit, the surfaces you make are really large. If I look at your starting values, they are in the 1000s. So I divide everything by 100 and viola, it works. Recalculates in less than 1 sec :)

Attachments:

GenerationtoilessurWishbonesModuleDerive_FIXED.gh, 30 KB

Permalink Reply by Olivier Suire on March 17, 2015 at 9:38am

Hi Armin,

And thanks for your help.

This really comes as a surprise for me because I've been modeling large structures in millimeters for 14 years, and I never noticed that moving objects around was such a problem for Rhino...

To prove this, you can just bake the surfaces, and try to move or copy them, even 560000mm further : it will work fine.

I would suspect that something on the GH side, or in the way GH communicates with Rhino...

Cheers

Permalink Reply by Armin Seltz on March 17, 2015 at 11:02am

Yeah, thats very strange. At a certain limit it just crashes, while normally the move component is very performant (in your example it takes less than 10ms to calculate the move). Must be a general area. Just tried something similar and it seems to be happing when moving surfaces. I tried with curves and it was fine even using insane large numbers, but for surfaces Rhino seems to go into crazy mode, when you transform something more than 500.000 units. Weird!

I suggest you re-post this in the "Errors & Bugs" section.

RSS