Marissa Farrell

@Chris Busch What issue are you running into? I'm still able to successfully make Marionette objects that have separate top/plan and 3D visuals using the current node library.

Unfortunately the way Marionette works is that it always keeps your objects contained in a group so that re-running the network will always replace everything done. You'll have to manually do this, or create a custom node that removes the object you're trying to exclude from all container groups.

To edit existing nodes, it's important to remove the first line of code that starts with #COMMAND;READONLYREFFILE; as that looks for a text source file to sync changes. After removing that line, you can edit as you wish.

It's likely that there isn't handling for multi-line input for Marionette OIP fields. Could you attach this file so I can take a look with the error presenting?

@KingChaos Have you resolved this? Visually, your network looks correct, but without the actual file I can't troubleshoot for you.

The bug I originally reported resolved itself and I verified the fix in 2019. Let me see if I can repro in 2022, if so I'll open a new report.

This has always bothered me! I'll see if there's an opportunity to coordinate those names, otherwise I'll try to throw a tag in there for searching at the very least.

What do you mean by decompose?

Is there a reason you can't use a rectangular shaped poly as your control geometry object within the container? I'm able to use the reshape tool under that circumstance. I do find it odd that a rectangle control geometry won't reshape, so I'll throw that in as a bug and see what comes of it.

@the frog This was a known issue and should be fixed! Please let me know if you see otherwise in 2022 SP3.

@Christiaan sorry for neglecting this post for so long! Running through my backlog now. Do you know what version this was created in? I'm finding that editing the script has the majority of the nodes disconnected. I'm attempting to rebuild the network now.

is this a file that was created in 2022, or is it from an earlier version?

I'm actually not sure which setting. could you possibly send me a copy of that workspace so I can take a peek?

I'm not having an issue wrapping it. Are you in a custom workspace? Which version are you working with? Does this persist after restarting Vectorworks?

can you share the file or a video demonstrating the steps you're taking?

Hi Mark - is there a chance you could share a file with the objects you're working with? I'm having difficulty assuming what your vendor's symbols are created like. Attaching here or sending to me in a direct message is appropriate.

Should be off of architecture and BIM 🙂

You can just delete the line that says REFFILE, all of the gray text there 🙂

So, Symbols cannot have different configurations, this would be a Plug In object (which is saved with red text in the resource manager) If I'm following correctly, you would have one symbol that was the same everywhere, but would want the position of the red box to move? For this, your Marionette script would place the static symbol object first and then layer the red box over the top in whatever position is defined with your option choice. I'm not sure that I am following the full goal correctly, if you could supply a simple file with a couple of the end results you're looking for I can probably make better sense of it.

Since you state that these configurations are all stored as symbols already, it should be easy enough to write a script with an input field (either text or preconfigured popup) that would allow you to choose which configuration you want to be placed. I believe this would meet you request, please let me know if I'm incorrect.

REFFILE is used for updating the scripts across all your nodes, it's useful when a node has a bug and needs to be updated in the source code, but what you've stumbled across is the small issue - each existing node in your document must be updated to refresh the script (so each time you open and close the node it will update it, but you need to do that for each existing node in your drawing). I *think* you could also use the "Tools > Utilities > Reset All Plug-ins" command to refresh the script, but I am not 100%.

I looked over these files and did not see that all of the scale symbol nodes had the "i", I often still saw an "s" When I updated these, all of the networks worked identically.

Sorry @willofmaine, I was off on vacation last week. I am looking right now!

The scale symbol node is outputting incorrect values. In the script, change the s in the last line to i and you'll get what you're looking for. Logging this as a bug now, thanks for finding it!