algorithmic modeling for Rhino
Due to some breaking changes in the Rhino SDK that caused bugs and crashes when running Grasshopper in Rhino5, there is now a quick-fix release available for download.
This release has some stuff that isn't quite finished yet, but I didn't want to wait any longer.
New features:
Fixes:
--
David Rutten
david@mcneel.com
Poprad, Slovakia
Tags:
It was Davids comment regarding the Rhino 5 SDK changes that made me think that the latest Rhino build may be necessary.
I have never had the issue with having to copy folders - GH runs from my Rhino 4 plug-ins folder.
interesting, mine couldn't load grasshopper right after the install on R5, but it worked fine in R4. Maybe there was something screwy in my R5 directory.
thanks,
Brian
David,
The offset problem of MeshRay intersection component in 0.8.0062 still seems to remain. Have you fixed the known problem? Please let me know. The return value of the component shows points at the location offsetted from the expected.
Thank you.
Jihoon
Hi Jihoon,
it wasn't my bug and I didn't fix it. Steve checked in a fix to the RhinoCommon SDK that seems to work, but until I release a new version this won't become available in Rhino4.
At the moment I cannot get access to the protected part of the McNeel webspace (which I need in order to release Grasshopper 0.8.0064) because we switched to some new system two days ago and it stopped working. (sigh)
--
David Rutten
david@mcneel.com
Poprad, Slovakia
Hi, David,
Thanks for Grasshopper 0.8.0063, but I am having trouble with the 'Weave' component. It won't allow my to manage/insert additional integer collections - I am only able to therefore weave two inputs when in the past I was able to weave several inputs. Not sure if this is a glitch or an intended update but this is causing a bit of a headache for some things I am working now, and will ultimately cause me some problems for past projects. Can you please shed some light on the matter. Thanks and Merry Christmas.
David,
Thanks for the updates. I'm experiencing a problem with the Divide surface isotrim feature in Rhino 5.0 Beta latest release. Where the divided surface seems to scale in the process of generating the sub surfaces. see attached screen. It seems to Scale by approximately 1.02?
Note, this problem seems to only occur with planar surface construction method as in using rectangle planar surface in grasshopper/rhino sdk. Four point surface construction does not seem to cause the same problem. The problem does not seem to occur in Rhino 4.x.
Thanks much,
-js
-js
Great stuff David... I know it's been in there for a little while, but the geometry pipeline is a huge addition for me as it eliminates one more confusing step for my less experienced users... No more referencing geometry to force auto-updates of my layer reading component! Very happy.
Cheers,
Marc
Hi David,
I currently have both Rhino 4 and Rhino 5 installed on my computer. Both running GH
When I run the new GH update only GH on Rhino4 is updated. How do I update GH on Rh5 please?
Kind regards,
Steve
Hi David,
I think there is an problem using RhinoNest for GH if you update to 0.8.0063. I described the problem here
http://www.grasshopper3d.com/forum/topics/gh-rhinonest-net-framewor...
Couldn´t figure out why.
Went back to the previous version (0.8.0062). All fine again.
Best,
Phillip
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson.
Powered by