algorithmic modeling for Rhino
Dear All,
a new version of Grasshopper is available for download from the usual location. This release contains a fair amount of bug fixes and new features. We recommend not updating immediately if you're in the middle of a project or nearing a deadline, there may be new bugs in this release.
New features:
Added [Point Deform] component for changing the control-point locations of geometry (Transform.Morph dropdown).
Added [Bend Morph] component for bending geometry from lines to arcs (Transform.Morph dropdown).
Added component menu option to the [Entwine] component for grafting (instead of flattening) inputs.
Added [Move Away From] component for moving geometry away from other geometry (Transform.Euclidean dropdown).
Added Enable Solver UI to last chance autosave recovery window.
Added Peak Display to the Galapagos Fitness Landscape component.
Added Feature Display to the Galapagos Fitness Landscape component.
Added Slope Display to the Galapagos Fitness Landscape component.
Added Direction Display to the Galapagos Fitness Landscape component.
Added Remap Option to the Galapagos Fitness Landscape component.
Added contour accuracy options to Galapagos Fitness Landscape component.
Added [Smooth Numbers] component for interpolating numbers over time (Maths.Util dropdown).
Added [Right Trigonometry] component for solving right triangles (Maths.Trig dropdown).
Added [Triangle Trigonometry] component for solving generic triangles (Maths.Trig dropdown).
Added [Centroid] component for finding triangle centroids and medians (Maths.Trig dropdown).
Added [CircumCentre] component for finding triangle circumcentres and perpendiculars (Maths.Trig dropdown).
Added [InCentre] component for finding triangle incentres and angle bisectors (Maths.Trig dropdown).
Added [Orthocentre] component for finding triangle orthocentres and altitudes (Maths.Trig dropdown).
Added [Curve Side] component for determine on which side a curve a point lies (Curve.Analysis dropdown).
Added [Plane Region] component for finding convex regions bounded by planes (Intersect.Mathematical dropdown).
Added [Point Deform] component for modifying geometry via control-points (Transform.Morph dropdown).
Dragging individual components/parameters will now snap to horizontal wires.
Bug fixes:
Using MRU tiles would always open the GH file on the main canvas, this is fixed.
Canvas redraws would not work correctly if more than one canvas was active, this is fixed.
Instantiating components using double-click would always insert the component on the main canvas, this is fixed.
Drag and drop did not work by default for canvas instances, this is fixed.
Cull Vertices component would sometimes fail due to index out of range errors, this is fixed.
The [Arc](Plane, Radius, Angle) component would sometimes result in invalid arcs, this is fixed.
Additional changes to make Grasshopper compatible with FIPS standards.
[Surface|Line] intersection component did not correctly re-instate 'Limit First', this is fixed.
[Surface|Line] component was incorrectly nicknamed SCX (c for curve), this is fixed.
[Construct Mesh] would crash if topologically invalid faces were supplied, this is fixed.
[Quadrangulate Mesh] had erroneous tooltip texts, this is fixed.
The [Smaller Than] component did not handle comparisons with infinities correctly, this is fixed.
The [Larger Than] component did not handle comparisons with infinities correctly, this is fixed.
The [Equality] component did not handle comparisons with infinities correctly, this is fixed.
The [Ellipse] component did not correctly compute focal points for negative radii, this is fixed.
The [Cone] component did not handle negative radii correctly, this is fixed.
The [Cone] component sometimes crashed when the radius was zero, this is probably fixed.
The [Sphere] component did not handle negative radii correctly, this is fixed.
The [Sphere] component sometimes crashed when the radius was zero, this is probably fixed.
The [Cylinder] component did not handle negative radii correctly, this is fixed.
The [Cylinder] component sometimes crashed when the radius was zero, this is probably fixed.
The [Brep Topology] component did not output correct EF data, this is fixed.
Integer conversion that exceeded the 32-bit integer range would crash, this is fixed.
Curve|Plane intersections would return duplicate results on seam intersections, this is fixed.
Curve|Line intersections would return duplicate results on seam intersections, this is fixed.
Expressions entered in the Generic Data parameter 'Set Multiple' menu were parsed recursively, this is fixed.
Changes to the MRU database would not immediately affect the Canvas MRU tiles, this is fixed.
Groups containing empty subgroups would include (0,0) in their bounds, this is fixed.
BeforeRunScript override inserts in C# scripts did not include method brackets, this is fixed.
(Anti)parallel lines were not filtered in the Line|Line intersection component, this is fixed.
Preview Plane Size setting was named confusingly, this is fixed.
The [Bounds] component would output a weird domain when all numbers were nulls, this is fixed.
Opening old GH files with Value Lists would not open with the correct item selected, this is fixed.
--
David Rutten
david@mcneel.com
Tags:
Yes,My problem--
Well since you're measuring the low+high points of a flat curve in the plane of the curve, any two points would be equally valid. I.e. this is an underdefined problem. It's like finding the point on a circle closest to the circle origin.
Awesome, super excited!
Just a note, looks like this broke one of my plug-ins - "Method not found: 'string Grasshopper.Kernel.GH_ComponentServer.CopyFileToRoamingFolder(string,Boolean)'." - did this method get removed?
answered my own question. looks like it's "CopyFileToAppropriateFolder" now! Any other SDK changes we should be aware of?
Hmm, sorry. Didn't realise anyone was using that method. There may well be other breaking changes like that, I unfortunately do not keep lists about that sort of stuff (I know I should).
I've sorted it out for my own purposes, but I have a bigger question (maybe worth its own post) - in a situation like that, where I want my GHA to be compatible with two different versions of GH, and version A supports method a, and version B supports method b, what should I do? presumably I can't reference two copies of grasshopper.dll and compile against them both...
i get the same problem. how do i solve it?
Thanks David, I especially LOVE the new snapping to get straight wires, so happy with that:)
I noted a minor typo in the CurveSide R output ("Fals") but there's no harm in that.
Since I am still missing default values for some (not just the native GH) components, I was thinking about asking to implement a sort of User-Default-Input-Values-Sheet, where one could set these personal preferred values. I guess I just did :)
Nope, you have to specifically say it using the magic words.
I don't understand the "Fals" typo. Where is it?
© 2020 Created by Scott Davidson. Powered by