generative modeling for Rhino
Important. You need recent Microsoft C++ runtimes in order to run this version of Grasshopper. You can download them here.
A new release is available for download from the usual location. This release mainly features a set of bug fixes. Not all reported bugs in 0.8.0065 and earlier have been fixed. OffsetCurveOnSurface and Brep internalisation is still buggy.
List of features and fixes:
To get around this you can type the full shortcut
Course I can do this manually, but is it possible to add somehow right align, center align and left align to 3d tags component?
I think there is a bug with ListItem. See attached.
Is it possible to keep TreeStructure while internalising data?
List item doesn't do what you think it does. You want the [Member Index] component in the Sets tab, Sets panel.
Ok. I see this has been discussed before:
its ticked, maybe its my rhino version...
is says: An error occured in the display pipeline @ 17:58:22(882ms)
And what version is that?
Display issues normally comes down to the last time you updated your display drivers. More often the case is it hasn't been since you got the computer. I know I hadn't updated mine for 3 years until recently.
The image above is from my work computer running GH v0.8.0066, Rhino 5 64-bit, Windows Vista 64-bit SP1 (I think), 4GB Ram, NVidia Quadro FX570 (x2), Display drivers updated last month, OpenGL version 3.3xx
Based on all the plug-in's that and components that people make that require boolean toggle in an immediate activate/deactivate kind of way, it would be helpful if there was a slingshot version of the boolean toggle. Where you slide a toggle over untill it hits the activated state, and on mouse release it slingshots back into "false" (or true, something you could change in its settings or something).
I've had a few headaches cause by long baking or exporting processes that let me forget that I have to true boolean toggle left on, and I make a little change somewhere downstream, and WHAMMO.... waiting for 2 minutes for things to calculate.
Don't know if this has been suggested before, but an idea.
I would support this. I was just going to make the same suggestion about a button that returned to 0 output when the solution was complete. I must have crashed rhino countless times this week by forgetting to return an activate input on Giulio's Bake attributes component.
David doesn't return until the 27th Feb so he will probably miss this post. on such a long thread. Either make a dedicated Wish discussion or bump this when he's back. But If you forget I won't :)