generative modeling for Rhino
Grasshopper 0.8.0011 can be downloaded from the usual location. But before you do, a small notice and a warning:
In order to run this new version you need to have the latest Microsoft runtimes installed on your machine. If you're on the Rhino5 auto-update cycle you should already have these. Install the new version, and if it doesn't work, then also download and install this package:
Microsoft Visual C++ 2005 Service Pack 1 (be sure to pick the x86 version as Rhino4 is a 32-bit application)
This build won't run well on Rhino5 until the next release of Rhino5. And secondly this build contains dlls compiled with a newer platform. This should not technically matter, but don't download this build if you're worried something exotic might go wrong. In case something does go wrong, the installer for 0.8.0010 can still be downloaded here.
Changes since 0.8.0010:
Loose curve offset did not work properly on Closed and Periodic curves. I rewrote the thing from scratch but it probably gives quite different (hopefully better!) results. There are still further improvements possible, so it's possible it will change behaviour again soon.
Ribbon Layouts are customized collections of tabs, panels and buttons. They are stored in *.ghlayout files which can be created using a dedicated Layout Editor. You can start the editor via the Grasshopper File menu or via the Ribbon popup menu (you have to right click on the area of the ribbon where tabs are displayed).
The order of Tabs and Panels is maintained, but within each panel area the components are ordered alphabetically.
When multiple loaded *.ghlayout files define the same Tab or Panel names, these will be merged. Duplicate components in identically named panels will not be shown.
The editor itself is almost entirely drag+drop based, so you won't find many buttons or menu items that 'do' stuff.
Layout settings should be sticky between Grasshopper sessions. If no layouts are loaded or if all loaded layouts are hidden, then the default layout kicks in, showing all components. So the only thing you can do with these custom layouts is hide functionality.
I am using rhino 4 sr9 with windows vista 64 (It´s often the problem) and the rhino doesn,t run with the new gh, it produce an error when rhino is opening and close it. If I install the older version everything works ok.
Have you read Giulio's reply a little bit higher in this same thread? You may need to install the latest Microsoft Runtimes for this to work.
very little information in that error report unfortunately. It seems you're running .NET 2.0, which might be a problem. Can you install .NET 3.5 and see if there's any difference?
worked fine! thx
I think .NET 3.5 was installed, for this reason the link produce an error when was installing. The problem finally was solved with:
because I think that I first installed vcredist_x64.EXE thinking in my operative system, no in rhino system. Now works perfectly!
Thanks for your time.
Hi David, maybe a bug but grasshopper crashes showing the grasshopper version history
crashed first time, im trying again and it doesnt show a thing
System::Windows::Forms::Application::ThreadException event occured
MESSAGE: Referencia a objeto no establecida como instancia de un objeto.
en Grasshopper.GUI.GH_VersionHistoryForm.RepositionProgressPanel() en C:\dev\Grasshopper\1.0\root\src\GH_VersionHistoryForm.vb:línea 76
en Grasshopper.GUI.GH_VersionHistoryForm.panelContent_ClientSizeChanged(Object sender, EventArgs e) en C:\dev\Grasshopper\1.0\root\src\GH_VersionHistoryForm.vb:línea 70
en System.Windows.Forms.Control.OnClientSizeChanged(EventArgs e)
en System.Windows.Forms.Control.UpdateBounds(Int32 x, Int32 y, Int32 width, Int32 height, Int32 clientWidth, Int32 clientHeight)
en System.Windows.Forms.Control.WndProc(Message& m)
en System.Windows.Forms.ScrollableControl.WndProc(Message& m)
en System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
en System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
en System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
No. I probably have to add multiple styles to this control so you can pick whichever interface makes the most sense.