Marissa Farrell

I think the primary reason we haven't included them is because they universally won't work, they'll only work in Marionette Objects, and we don't want users to be confused by their accessibility. There are a couple of other nodes that are restricted to use outside of running straight from the Design Layer, and those are Control Geometry, Control Point nodes (2D and 3D), and Set Selection, the 3 first are for use only in Marionette Objects, and the last only works in Menu Commands. (I may be forgetting one/some, but I don't think so?) When a network is run on the Design Layer, it does a fun traversal up and down the network to build the script out, and it's not really predictable. I have yet to figure out exactly how to make it generate in the same way every time. (I would guess it has to do with which node you had selected when choosing to run as well as the stacking order of the nodes attached to the selected node, but I honestly have no clue, I just know it's complicated and fussy.) The suggestion to group and ungroup is still a good one; the only other thing I can think is to make the network more linear with less branches, but the way a lot of our nodes are created won't really help you there, and I can't see a good way to rewrite the nodes to accommodate that, either.

Can you share your file so I can take a look? Marionette networks are difficult when it comes to stacking because the order the traversal up and down the network isn't really straightforward, it often works better when you create a Marionette Object to make sure what you want is on top, but once I have an idea of what you've done, we may be able to work around that if a Marionette Object won't work for you.

The output of the mirror node only outputs one object, the mirrored object, so only the object that results from the mirror will change color. If you want to also color the original, you'll need to wire from your input object to the attributes node as well.

You can certainly export the Python file and use it, but it's not very efficient. There's are a few discussions about it, I've linked two below. Unfortunately, exporting the script will result in a bunch of lines of code and logic that doesn't always play out how you want. If I were to approach it, I would copy the guts of the nodes and write my own PIO script.

Did you manually create those polylines? This can certainly be done, I'm just trying to figure the best way to guide you through it.

I'll take a look at the file later this week. Marionette Menu Commands are stored in a file called Marionette Command Library.vwx which is stored in [User Folder]\Libraries\Defaults\Marionette\. Menu commands are stored as wrappers in the RM within this file. You should be able to copy from this file into another user's file in their user folder and restart Vectorworks to have those menu commands show up in their Marionette Commands. You should also be able to rename the resource to change the name which will update after a restart of Vectorworks. There currently isn't support for Workgroup folders, though it's something I would like. I think some constraints would be the naming of menu commands, location of WG folder, etc. I'll talk to the engineers that know more about that and see how feasible it could be for a later version.

@HebHeb Can you send me the file where you're getting resulting empty groups?

On my radar, thanks!

I made some progress and shared in this file, but at this point, this is as far as it's gotten.

And here's what the replacement node should have been Marionette_Get Classes_MFarrell.vwx

Here's the Get Class List in 2026 version. I was pretty sure I added a node that just gave you a list of all of the classes as a replacement but I'm not seeing it. I'll look into this. Get Class List 2026.vwx

Can you let me know what you need this node for? The Get Class List node was removed intentionally because it took the index of a class instead of allowing a user to just choose one. Does Class Popup not work for your use case?

I don't think Marionette can reliably let you click to choose points, however, you could use the Control Point node within a Marionette Object which would allow you to place blue handles at the positions you want. It's been a while since I've written in LISP, but if control points work for you, I'm sure I could refresh myself enough to give more guidance.

Can you clarify, do you mean a Marionette Object PIO, or a Vectorworks PIO object?

Can you show me a screenshot of how you need the style to look? Because for me, that IS changing. I think it's also important to note that I believe you will need to use the English "Plant" record (not Plant Record record) to modify the style... But I think with the translation issue I need more info.