algorithmic modeling for Rhino
Another minor update is available for download from the usual location. This release fixes four bugs and adds one component.
Please see the 0.9.0051 release notes for the really important messages. If you've already installed 0.9.0051 or newer you can just upgrade without problems.
New since 0.9.0052:
Added Brep Split component (Intersect.Shape dropdown).
3DM import layer filter did not work, this is fixed.
Component Aliases were never loaded, this is fixed.
Script components would not work without any RunScript code, this is fixed.
Text Format component would skip the first formatting item, this is fixed.
I fixed the problem, I'll release another incremental update today.
Thank you David,
Waiting for the new release.
By the way, What about Sweep2 & PULL POINT bugs?
Pull Point is fast again, Sweep2 hasn't changed. I use the Rhino SDK method for making those sweeps so it will take a Rhino5 release + fix.
Do you mean that Sweep2 can be fixed in the new Rhino5 release, such as Rhino5 SR4? Do grasshopper also need to upgrade?
Exactly. I do not know when it will be fixed, but the earliest possible opportunity will be Rhino5 SR4. You will not need a Grasshopper as well, the old Grasshopper will simply call the improved function whenever it becomes available.
Thanks for your patient response!
Look forward to SR4!
Best regards to you!
haha Sorry, last question:
Can it be construed as it's a rhino5 sr3 bug? So we have to wait sr4 to improve function.
I have always wondered if it was possible to show a line number when the VB component hits the "Index was out of range" error.
For example when by mistake a List is called with an index that is too high, it would be great to know where exactly that happened.
Would that be possible? Thanks.
Seems like Addition Object doesn't seem to work for Vector Addition. Having to swap all point + vector addition objects with Move.