generative modeling for Rhino
a new, fairly major, update is now available for download. This release features breaking changes to the Grasshopper SDK and component libraries compiled against older versions may no longer work.
Be aware, this release breaks file-forwards compatibility. You will not be able to open gh and ghx files saved with 0.8.0050 on previous versions, though of course you should be able to open old files without problems. If this is not the case, please yell loudly.
If you're having trouble loading Grasshopper, note that you must have the latest Microsoft C++ Runtimes installed on your machine. They can be downloaded from the microsoft website.
The new release can be downloaded from the usual location.
Here's a list of changes, additions and fixes since 0.8.0013:
I'll add some additional information regarding some of the new UI features in subsequent posts.
Just as a wish,
while working with dinamic things it is ofthen handle to switch boolean toggles off-on-off, (two doble clicks)
Wonder if it is possible to add "bang" mode to boolean switch for this. I mean, in this mode it will switch to true just for one moment.
CreateSquarePipes is not a native grasshopper component. You will need to contact the developer for an updated version. There were some fundamental changes to the SDK for the latest release which will cause this sort of thing.
This release features breaking changes to the Grasshopper SDK and component libraries compiled against older versions may no longer work.
Thank you for your reply. I think I've tried some command from RhinoBIM to make some sort of tube. I will inform them in this regard.
I've tried to reinstalled Grasshopper, but the message still keeps on pop up. Do you any advice to stop this pop up?
Run the GrasshopperDeveloperSettings Command in Rhino to see where GH is looking to load component libraries from. You should be able to then navigate to one of these locations and find the offending gha/ghuser to remove. If you still want to use this item in older versions of Grasshopper then you will have to put up with the message for the time being.
Thank you for your advice.
Hi community, hi David,
is it just me or is the OffsetCurveOnSurface component still corrupt?
When I enter a negative distance value I would in past have received an offset on the other side of the curve (compared to a positive value). Since GH 0.8.0013 and 0.8.0050 the procedure will fail flop and whooop the component sets it's red lights on.
I recently mentioned the workaround, but will it be back alive on 0.8.0051, David?
I haven't touched it lately, so unless the Rhino core offsetter has been updated recently it'll have the same bugs as before.
kind of hard to judge, as the OffsetCurveOnSurface command runs rather smoothly in the rhino application... however there you usually use a positive value and choose to flip the offset direction...
thx for the quick response.
I'd have to dig through the Offset command code to see if and how that command uses the Core function. And I find Rhino source code to be on the severely side of unreadable.
Wouldn't be the first time I spend 2 hours looking at C++ magic without gaining one iota of understanding :(
another thing to check:
command: Toggle Preview;
keyboard short cut: [Ctrl]-[Alt]-[Q]
neither worked for me tonight
(win 7, rh50x64 latest build, gh 0.8.0050)