Grasshopper 0.7.0014 available for download

Replies to This Discussion

Permalink Reply by Ángel Linares on May 17, 2010 at 10:45am

Mmmm...I need to try galápagos :D

Permalink Reply by Carlos on May 17, 2010 at 11:07am

Thanks David.
Small bug:
It seems the new version has some issues with polylines built with arches.
Components as Explode or Fillet, don’t work.

Thanks again for your amazing work!

Carles

Permalink Reply by taz on May 17, 2010 at 7:58pm

Thanks for dropping G-Money on us!

Permalink Reply by Steve Lewis on May 17, 2010 at 8:46pm

Is the link to the gh sdk help something new for the 0.7 release? First time I saw it today and it is extremely helpful.

Permalink Reply by David Rutten on May 18, 2010 at 1:25am

Yes,

0.7 is the first version that has an officially documented SDK. The help file is still lacking many topics and a lot of classes/methods haven't been documented yet, but this is something I'll slowly rectify over the upcoming months.

--
David Rutten
david@mcneel.com
London, UK

Permalink Reply by Andrew Heumann on May 17, 2010 at 11:26pm

Thanks so much David! Galapagos is absolutely fantastic, I can't wait to put it to use, and the new exposure and occlusion components are a great addition. I just did a quick test calculating approximate direct+diffuse shading on a mesh with the exposure component, the animation is here: http://vimeo.com/11829735

The improvements to this tool with each release never cease to amaze and inspire me. I already can't imagine working without it.

Permalink Reply by Ángel Linares on May 18, 2010 at 3:48am

A little error opening a definition from 0.6.

I've "emailed" you the definition.

Best Regards.

Attachments:

• Error.jpg, 723 KB

Permalink Reply by michaeldrobnik on May 18, 2010 at 6:57am

Great Work David! Galapagos is amazing.
It seems like "Divide Distance" has a bug in this release. It doesn't matter which geometry I'm feeding in, it just gives me the Start Point of the curve.
Thanks

Permalink Reply by David Rutten on May 18, 2010 at 3:51pm

Thanks, fixed.

--
David Rutten
david@mcneel.com
London, UK

Permalink Reply by enrique soriano on May 18, 2010 at 2:14pm

2 things
-Could it be possible to have a whislist page?
-in this whislist i would add something like: "Big O notation measurement tool to add to the debugging tools
thanks a lot anyway for the realease!!

Permalink Reply by David Rutten on May 18, 2010 at 3:56pm

The wishlist is on my iPod. Safe and sound.

How would a 'Big O' debug tool work?

--
David Rutten
david@mcneel.com
London, UK

Permalink Reply by enrique soriano on May 19, 2010 at 11:21am

I have never seen such thing.. gaphically. May be it cannot exist, or it's for a very long-term whishlist..
But I wonder if a cluster of nodes could express their time "complexity":

Inside of each node(standard, not custom for the moment), I can imagine there's a precise notation: O(n), O(n^2)..that we don't know because we do not read the code of each node (better this way)
As we keep on adding nodes and nodes..the overall complexity might be averaging or tending to something..

The point is to be aware of which parts of the patch are highly time consuming when increasing the resolution of their feed.
I guess there are nodes that when we double the points, they consume the double of time, and others that consume the time exponentially.

I was thinking that a solution similar to the smart "profiler", would be amazing for a first step. But I guess a more clustered solution would be even more understandable (maybe analyzing the "group selection")

I 'm not sure if the big O notation is something you would only be able to know from the node property or it can be quickly found by an aproximation. >> (like the fps check)

anyway, maybe it's not so useful.
but I recently crashed repeatidly GH and while I was waiting I just thought of it (and where was the limit of increasing those f***ing points) and how to be aware of super exponential time consuming nodes..

thanks!

enrique

• ‹ Previous
• 1
• 2
• 3
• 4
• …
• 6
• Next ›
• Page