Forum McNeel Forum

Following this thread: Better paste options? Rhino for Windows Hi all - I dredged up an old RhinoScript that might help - Drag and Drop the rvb file onto Rhino to add two new aliases PasteAtCursor - pastes where ever the cursor is. PasteToCursor pastes and attaches the object to the cursor, click where you want it to end up. PasteToCursor.rvb (1.1 KB) -Pascal and having used autocad in parallel with rhino, I lacked more control over the insertion point of “PasteAtCursor” and that’s because it starts with “CopyWithBase”. To make the copy-paste between files reliable I vibe coded two scripts: CopyPaste - Copy.py (1.0 KB) CopyPaste - Paste.py (743 Bytes) Copy asks for a base point (P) → turns redraw off → moves the selected geometry from P to (0,0,0) → runs '_CopyToClipboard → moves the geometry back from (0,0,0) to P → turns redraw back on. Similarly, Paste: runs '_Paste, which natively inserts the geometry matching the file’s (0,0,0) → runs _Move → automatically selects (0,0,0) as the first point, fades away mid-command to let the user select the desires insertion point: Hope you find it useful -Dani

@DanielPiker as far as I understand you developed shrinkwrap. Could you improve the command so that narrow slivers are eliminated?

Hi @phcreates , Same issue as before. The precision error grows with distance from the origin, and converting to inches moves your surface about 25× closer to it, which is enough to keep the box flat. You found a real bug. CageEdit checks the wrong option when you change VDegree on a flat cage, so the value gets reset. I’ll get it fixed. Your “type 4” workaround is fine for now. YouTrack CageEdit ignores VDegree on rectangle cages : RH-99200 When CageEdit builds a rectangle (UV) control, changing VDegree to a value higher than the current VPointCount allows is silently undone. UDegree in the same situation works: it raises UPointCount to fit. Steps: 1. Draw a flat object, for example a... – Dale

I think we want to make sure the install is right. If you go to Package manager, is the RhinoMCP-platform installed? I so, let’s uninstall that. Then in Tools pulldown > Options > Plugins > Plugins that do not ship with Rhino should not contain Rhino-mcp-Platform. And in the list of loaded plugins you should see RhinoAI with that icon: With a version number in the upper right: See if that helps. I worry that the prompt could not figure out the version number. That tells me the Rhino AI plugin may be old.

Hi everyone, I have started a small video series called Rhino.Inside.Revit Made Simple. The idea is to answer the questions new users ask most often, one short, focused workflow at a time. Each video takes a single task, builds the definition step by step, and shows the result in Revit, so you see exactly what each component does and why. First episode: Dimensions How to create an aligned dimension between two walls using Add Aligned Dimension: which inputs it needs, how to expose the hidden Type input, and why plugging walls in directly gives you their centreline s. More simple workflows are coming over the next weeks. If there’s something you got stuck on when you started with Rhino.Inside.Revit, reply here and I’ll add it to the list. Hope it helps! Saqlain

I found one of them. This was back in 2014, wow I didn’t realize it was that long ago. Linetype scaling in model space - Rhino / Rhino for Windows - McNeel Forum

Hi Mitch, Thanks for reporting, this came in with the recent Dot dialog cleanup. Font and Height moved to their own rows and the Display text box is the one that gives up the space when the dialog opens short, so it can shrink to nothing. Logged as RH-99196 , resizing once like you did is the workaround for now.

Thanks! If you can find that thread, I’d be very interested to see it. In the meantime, I went ahead and created a separate wish with a small UI mock-up of what I had in mind: [A unified Model Space representation scale] It sounds like we may be talking about the same underlying idea.

After looking more closely at how annotation and linetype scaling works in Rhino, I think the Model Space workflow could be simplified. At the moment, if I want to work with a drawing intended for 1:5 representation , I need to keep several settings synchronized manually: Annotation Style → Model space scale = 5 Linetypes → Model space scale = 5 If I change the intended representation to 1:10 , both need to be changed to 10. This works perfectly once everything is synchronized, and I actually like the amount of individual control Rhino provides. What seems unnecessarily complicated is that the user has to manage this synchronization manually. Conceptually, my intention is much simpler: I want to work in Model Space with a 1:5 representation. Would it make sense to have a single Model Space Representation Scale control , something along the lines shown below? Annotations, linetypes, hatches, and other scale-dependent properties could follow this representation scale by default, while their existing individual scale controls could remain available as overrides. This would not change model geometry or replace Detail scales. It would simply define the graphical representation context used while working in Model Space. The individual controls are useful, but understanding and manually synchronizing them shouldn’t be required for the common case.

Martin Siegrist: Could it be that different tolerances on creation of geometry, export and import have an influence on the result? The bug is that Rhino is changing the underlying NURBS surface geometry. The surface control points and knot structure should not be changed by exporting and importing to and from STEP Scott Davidson: I think we may have found where this is changing. It looks like the Rhino STEP import is changing the model a bit. Rhino4 imports the STEP file correctly. What Rhino is trying to do is extend the surfaces in some sort of misguided attempt to fix something that is not broken. Unfortunately Rhino is often not very good at extending (as this current example demonstrates) and also Rhino is not very good at whatever decision process is used to choose where to extend (that also appears to be what this case demonstrates) Rhino handling of Step files has been buggered for many years. Rhino4 is the last version that is reliable. One of the problems starting with Rhino5 is that the STEP import often gets the file tolerance wrong. If you open a STEP file you will often see the model tolerance is set to an unreasonably tight tolerance and then Rhino proceeds to fix things that don’t conform to the errant tolerance setting. All of this is poison to any Rhino user that has to receive STEP files from customers and then needs to edit the damaged geometry. For one thing its difficult to asses where the damages is. That is because (presumably) what Rhino is doing is t

Bogdan_Chipara: arrows in the prompt area should cycle between previous prompts, exactly like in ChatGPT desktop app. That’s a nice feature. RH-99195 Up Down arrows should cycle previous prompts

There are a number of ways that AI can do this. All of them are on the table: Create a Grasshopper definition with standard components Create a GH component that is one single Python or C# component that does everything. Create a series of new custom components like plugins might that can be used and rearranged. All of these are currently possible, depending on what you instruct it to do. I am using RhinoAI , but also there are even better tools like Raven at this time that can assist with this. Here is a working definition and some of the prompts used: Creates grasshopper script that makes a 5 repeat roof trusses where I can adjust the number and distance they cover in Grasshopper