Benson Shaw

@Antonio Landsberger Thanks. That's basically what I am doing to move things forward, along with asking for others' help. I'm not at all a scriptor/pythonista. Often my knowledge of trig and other maths can be applied to networks of existing nodes. With that, I'm often wishing some of the nodes behave more closely to the drawing space tools and commands. @Pat Stanford Absolutely. See also comments above by @Marissa Farrell regarding node updates and breaking networks. My preferred solution would be to issue a brand new node with better functionality but with a new name, v2 suffix or the like. This way the old node is available for replicating structure and function of older networks. Witness the Enhanced Rectangle node by @DomC. And, yes. Take an alternate path when network not working. A stop at the forum might help determine whether the problem is pilot error or node problem. It was wild to see @Letti R cook up 3 alternate networks for rotation. I have since created another couple. -B

Also not clear why 3d loci are not on list of "acceptable" objects. Loci from 3d tool set respond as expected to the Rotate 3d command in the Modify menu. If I understand properly, the Rotate 3d command somehow incorporates that same Set3dRotation script? Something about a locus seems counter to the script. Or maybe script could be modified to include the 3d loci? Meanwhile, group it! And, I'm off to slider questions -B

Doh! Rotate 3d! Either way got it to work with the Group idea. Thx again -B

@Pat StanfordThanks for looking and commentary. Those such as yourself with loads of experience in the underlying VS might find and understand the limitations. I look at the Rotation node description and see nothing that indicates a 2d or 3d locus would not be an acceptable object for action by the node. Maybe there is some mathematical or VS argument that a 3d locus is NOT an object? (A locus is only a location? One is not a prime number? String theory and multiple universes are . . . um . . . something?) I am not versed in VS. That Set3dRotation line in the node script is not informative for me. (not your fault!) @Marissa Farrell is kindly reviewing some of these older nodes to update descriptions, scripts, user friendliness, etc. This presents hope for me and other occasional Marionette dabblers that I will have easier rout to success in future! I think Marionette is really cool and full of potential, but only implement it occasionally. And usually run into roadblocks. To the forum I go! Thanks all! -B

@Pat Stanford - Ja. Good idea! Thanks! I wonder about that MiniCad design decision idea. The workspace tools and commands seem to work as expected with 3d Loci. Not to take away from Pat's tip, but this seems a workaround. How would Marionette users (especially inexperienced ones) know to do that conversion. Is that perhaps addressed somewhere in those multiple hours of intro videos? Thanks again, Pat -B

Another rotation hurdle. The Rotate Node works for many types of objects, but not for a 3d locus? Or is there a method to rotate a 3d locus via the rotate node? Circle created and rotated Locus created, but did not rotate. Here is my workaround using essentially create location via sin and cos -B

@Marissa FarrellSuper! Please carry on with this! Seems such requests could be added to a specific thread. Perhaps pinned to top of Marionette forum? One problem is mods to existing nodes can break existing networks. Adding new, improved node (with similar name) to the library would be a possible solution. -B

@Letti R Many thanks for those examples! I'm guessing that if you need a rectangle in some new network, you have one or more of those saved. Or do you just make one on the fly each time? @Marissa Farrell Thanks for any efforts to make Marionette more user friendly. I'm wondering how that Rectangle node was envisioned? It certainly needs a lot of mods to make it behave similar to the Rectangle tool in vwx basic tool set. The networks assembled by @Letti R, and the Enhanced Rectangle by @DomC are more user friendly because predictable/familiar in parameter adjustment. Also, what about that Rotate node description showing rotation parameter in radians, but it behaves as expected with degree input ??? I do understand that the Angle (degrees) node in the image is a Real node, renamed. But the network by @Letti R responds as expected to angle inputs. -B

Alright. Thanks, @the frog for digging it up. This old nRectangle node is not in the current defaults library. It has limitations. . . Nice to see some old kit. Does anyone have a better way to do the rotation with this rectangle node. I could not find a "v" type (vector) node for angles., only "n" type (numeric). Sticking with @DomC custom node for now. OK, more questions later about setting and adjusting position of EAP path endpoints. Thanks -B

Starting a new Marionette project, and once again stalled at step 1. Literally! Need to create a rectangle with parametric size, center location and rotation angle about its center point. Create Rectangle node places the rectangle insertion (origin) as the lower left corner. I need rectangle to insert at its Center. I could alter insertion by tying to width & height inputs (half ea). not shown. Other ways? Create Rectangle has a vRot input, but I cannot find a node for angle in v output. How is this input controlled? I found @DomC's Enhanced Rectangle mode which is PERFECT! But would also like comment/advice on above questions for the standard rectangle node. I am always a beginner when I start exploring Marionette. It's tantalizing, but so many uncertainties and unexpected results make me reluctant to use it. -B

One scenario - Switching among several Saved Views may change the drawing’s active layer. Eg Copy or Cut objects in one Saved View, then switch to another Saved View with a different Active Layer, and then Paste. The Pasted objects manifest on the active layer of the target Saved View. -B

Does it work to join the plane edges with a tiny fillet? Might need Add Solid and Convert to Generic. Or Extract then Shell? Will try to experiment later -B

Something I would add to this is the CNC software. Some services have not updated in decades? and require dxf from customers because AutoCAD light was affordable and other software was/is not. Never upgraded. So success and cost might depend on whether the file from customer matches the capability of the shop. Newer machines and software seem to handle a lot more complexity and variety of input. "My" long time water jet service invested in "front end" software which was quite lenient compared to other shops I tried, although it still did not want bezier curves. My best outcome, though, was always from polylines with only arcs and straight lines, hence my willingness to trace. I developed arc based polyline alphabets from several fonts. Most were modified to some form of stencil-like characters, but also a few for cutout letters without the stencil bridges and gaps. No stacked points in these characters. Vertex count manageable. The CNC router service I used offered an up to date setup. Owner was a vwx user which meant my native vwx was the input I sent. He ported to dwg and the slicing app. Software could interpret beziers, and did z steps for more sculptural objects. A breeze compared to the water jet. -B

Line type might ultimately work if @daniel.mij is satisfied with series of short, straight segments inside a rectangle, with possibility that one or both ends of the rectangle are not rounded. Image shows a couple stacked lines/polys of narrow and wide weight. Draw the wide one first, Dupe in Place, adjust weight, group if desired. Downsides include extra effort to form, and extra effort to edit if needed. Editing straights: Group the two lines, move the Group corner vertices as needed. Editing curves: If grouped, Edit the Group. Delete the narrow. Edit shape. Dupe. Adjust color & weight. Class or style for each component would eliminate a few steps. Oh well. At least result matches the example. -B

Looks ok. But the rounded ends may be desired to concentrically enclose the inner line, per the OP example. I think in the line type solution, the rectangle could instead be a rounded poly, but some/many object lengths might truncate the rounds. shootin’ from the hip. -B