A few times I've made a pipe, then later wished I still had the curve it was made from. Any way to get a curve from the centre of a pipe?
Tags:
Permalink Reply by Pascal Golay on January 11, 2013 at 8:10am Hi Ryan- that takes a script, again. I think I have one that works at least some of the time, I'll see if I can dig it up.... Here it is.
To use the script, extract and save the .rvb file from the attached zip archive, then drag and drop the saved rvb over an open Rhino V4 or v5 window. This will load the script, set it up to load on startup in the future and register an alias
PipeCL
that will run the script much like a regular command. The alias can be typed or added to a toolbar button or keyboard shortcut (F-key).
-Pascal
pascal@mcneel.com
Permalink Reply by Ryan Wynott on January 11, 2013 at 8:11am Thanks Pascal.
Where do you put your script files? Rhino seems to look for them wherever I leave them (rather than copy the file to a specific place.)
Permalink Reply by Pascal Golay on January 11, 2013 at 9:08am Hi Ryan- I do not put them anyplace- you can put them anyplace you like- that is, unzip the rvb file to whatever location you like, and than drag and drop the rvb from that location onto Rhino. They should then be available whenever Rhino runs.
-Pascal
pascal@mcneel.com
Permalink Reply by Ryan Wynott on January 11, 2013 at 9:14am Hrmm I'm having to drag that intersectplane script on every session. Something's not right.
When I look in my options / rhinoscript it shows the isolate script as linked to the file in my downloads folder. I assume that when I eventually clean that folder up the script will break, no?
If I understand what you're saying correctly, I shouldn't have to store the script file somewhere. Rhino should absorb it and we can delete the file we downloaded.
Permalink Reply by Pascal Golay on January 11, 2013 at 9:26am Hi Ryan-
"If I understand what you're saying correctly, I shouldn't have to store the script file somewhere. Rhino should absorb it and we can delete the file we downloaded."
No. Rhino needs to find a startup script file every time it starts in order to use it. It knows where to look from the initial drag and drop operation. Not all scripts are organized this way but it is a convenient way to make a script behave as much as possible like a normal Rhino command.
-Pascal
pascal@mcneel.com
Permalink Reply by Ryan Wynott on January 11, 2013 at 9:32am Right. So I move the script to my plugins folder (or wherever but I chose that to keep that stuff together) then drag it on, and blamo it should load every time, right?
Permalink Reply by Pascal Golay on January 11, 2013 at 9:38am Hi Ryan- correct. Blamo. Then don't move them though. Also, if things have got out of kilter, it may be good to look in Options > RhinoScript and clear all the currently loading startup scripts from the list, then drag and drop from your new organized script file location to repopulate the list with no duplicates or incorrect paths.
-Pascal
pascal@mcneel.com
Permalink Reply by t.o. on January 11, 2013 at 9:49am try using
Applycurvepiping
next time. the curve is always available and you may edit with control points
Permalink Reply by Willem Derks on January 13, 2013 at 1:23pm That or enable History recording when creating the pipe form the curve;
Keep the curve ( in a separate layer) and when needed editing the curve will update the pipe.
-Willem
Permalink Reply by Helvetosaur on January 13, 2013 at 4:04pm Yes, except that makes a mesh and as such is both not smooth (faceted) not combinable with NURBS...
----H
© 2013 Created by McNeel Admin.
