Grasshopper

algorithmic modeling for Rhino

Grasshopper 0.7.0054 is now available for download. This release focuses mainly on Galapagos improvements, but there are also some other bits and pieces:

  ● Added Nurbs Curve Knot Vector component.
  ● Added an Item Index component.
  ● Changed the InsertList component logic to be more flexible and predictable.
  ● Grasshopper geometry is no longer encased in bounding box markers.
  ● Added more selection and navigation mechanisms to Galapagos interface.
  ● Added founder population boost factor to Galapagos.
  ● Added avoidance and collision algorithms to the Galapagos genome factory.
  ● Galapagos species and population viewers now support multiple generations.
  ● Galapagos can now use output parameters as fitness values as well as floating parameters.
  ● Galapagos genome map now properly displays parental and dead-end genomes all the time.
  ● Galapagos can now maximize, minimize and optimize genome fitness values.
  ● The viewport now remains responsive while Galapagos is running.
  ○ Fixed arrow key navigation in the Galapagos Species Statistics viewer.
  ○ Fixed a bug with input parameter visual tags and erroneous grip locations.
  ○ Fixed a bug with the Curve Frames component.
  ○ Fixed Grasshopper preview geometry being visible in Page Layout views.

Enjoy,
David

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Views: 766

Replies to This Discussion

Hi David,

thanx for the update!

I see that my definitions containing the Image Sampler (definitions saved in 0.6.0059 version) don't work (the result is not the same as the old version)!

I notice that when I set the X and Y Domain as [0,1] the image limits show a "?"

Is it a bug or somethingh is changed?

thank you
yeah, it's a bug. You can fix it by writing the interval as follows:

[0 To 1]

I'll make the string parser smarter so it can handle commas as well.

--
David Rutten
david@mcneel.com
Poprad, Slovakia
Thanks David,

Would you know why i get the attached loading errors ?

Many thanks,

Arthur
Attachments:
Hi Arthur,

these components come from a 3rd party library that hasn't been compiled against the 0.7 SDK. You will not be able to load those components in 0.7, the developer in question will have to post an update of the toolset.

--
David Rutten
david@mcneel.com
Poprad, Slovakia
Hi David. Thanks for the update - I'm looking forward to working more with Galapagos.

There are a few odd behaviors I've noticed:

1. I don't know how long this has been the case, but a paste of any geometry into Rhino seems to cause a complete rebuild of the currently open GH definition. This happens even if the copied geometry has no association to the GH definition.

2. While a slider change made by moving the slider is now an undo event, changing the slider through the editor (either double clicking, or right clicking to the Edit...) or the Values control is not.

3. Lastly, you're probably aware, but the Values control for sliders is a bit wonky. There's a graphics issue on the first click of an up or down arrow that also displaces the mouse, clicking 'Cancel changes' changes the limits and puts the slider at 0. I actually do like that the Values control runs the solver without confirming the changes because it allows one to quickly move through slider values in consistent steps with just one click.
I'm encountering a problem here which didn't occur when using the stable version of grasshopper:

I was trimming a list of closed rectangles, say a brick-wall pattern, with a large closed curve that defines an area. So the application of this definition would be making tiles for the pavement. However with the current version, occasionally there are tiles cannot be trimmed. I used "Trim with Region" and "Trim with BRep" (created a solid using the large closed curve and have it intersecting the rectangles) and neither worked. However if I bake everything to Rhino I can trim them without any issue.

So I was trying to find out the problem, and what I found was that using "Curve | Curve" intersection solver to find the intersection points, and Grasshopper fails to find some points that should exist. I'm using this definition for work and if you could have it debugged I would appreciate very much.

Thank you
Actually I just solved the problem using Brep|Brep solver between the planar surfaces made from those curves. But it would still be nice if you can fix the bug.
I found a bounding box error

the bounding box is grabbing the control curve/points instead of the actual objects. see image

Hi Robert,

this is actually a problem in our SDK. We're not quite sure how to solve it yet.

--
David Rutten
david@mcneel.com
Poprad, Slovakia
Thanks, now I understand why Bounding Box not always wrap a sphere tightly ~~~
thanx for the update!

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service