Niels Timmer

I'm still experiencing the same problems with Marionette in a Project Sharing environment. This is how the network of one of the Marionette Object Style looks when opening the project file again after the weekend: Except for two or three, all connections are lost. All 31 instances of the Marionette Object disappeared. Does anyone know how to prevent this? Are there best practices when working with marionette in project sharing files?

Yes, sure. Most of the naming of layers/classes/objects is in Dutch but I think you will manage to understand what I'm trying to do. It would be great if you could look into it! 231002 Standaardkozijn_purged.vwx

Hi, I created a Marionette Object and converted it into a red symbol (plug-in style). When I right click the symbol and choose Edit... to edit the marionette script, the parameters of all instances are reset. Is there a way to prevent this? Can I set the marionette input nodes as 'by instance' parameters of the plug-in style? (sorry for this unclear English sentence, I'm a non-native 😁) The image below may clarify what I mean:

In VW2022 it was possible to set the Custom Sash Options 'by style'. In the user interface the button looks more like it is part of the Sash or Operation setting that can be set 'by style'. Maybe Tom is right and this is by design, in that case my bug report becomes a feature request 😄

Hello, The window tool has a very annoying bug in VW 2023. Configuration and operation settings are not updated when I edit a window style. This is how to replicate the problem: (configuration is set to 'by style' and not 'by instance' off course) Step 1 Draw a wall Step 2 Place a styled window in the wall with Configuration set to Custom Step 3 In the Custom Configuration Options dialog, edit the configuration and operations of a few sashes Step 4 Discover that the window with the style you just edited isn't updated in the model Step 5 Place the window from the resource manager in a new wall and see that the new window has the new configuration settings See attached file. Window Tool Bug.vwx

Hi, I had time to take a look at the latest version of your network. You added a "Series"-node to scale every single duplicate of your shape. The description of this node says that it "Creates a series of numbers beginning at start and increasing by step for count cycles" and that is exactly what it does. I added the "Print Debug"-node to show what the output of the "Series"-node is. That's why the shapes are scaled to 190%, 285%, 380% et cetera. What I would suggest is that you scale the input object at the very beginning of your network, before duplicating it. Then you don't have to scale every single duplicate because the original object is already at the right scale. Instead of the Print Debug-node you can also use the Debug Mode of the Marionette Tool to see what data flows through your network. You can read more about this here: https://app-help.vectorworks.net/2023/eng/VW2023_Guide/Marionette/Inserting_a_node with_the_Marionette_tool.htm Good luck!

Hi @Ben59, Here are my answers to your questions: I think you already found the EasyText node. I quickly added prefix and suffix functionality, so now you are able to change the insertion point and still have a suffix. If you want the slider to display the stand height instead of the moving distance of the second tube, you'll have to put some math between the slider and the "Point 3D"-node. I didn't add that to your network now. For the bonus question I used the "Set Record Field"-node. I used the "Marionette Object"-node to attach the record to the Marionette object your network creates. I hope this helps. Good luck! stand marionette in blank file02.vwx

What you could do to get rid of the 3D polys that you don't need is just delete them with the delete node like this: I noticed that the last 2D poly was rotated but wasn't moved. So this is another change you could make to the network to fix that. Link the "add 1" node to both "Series" nodes. Because the Series node produces a list that looks like this: 0 - for the original object Spacing * 1 - for duplicate 1 Spacing * 2 - for duplicate 2 Spacing * 3 - for duplicate 3 Spacing * 4- for duplicate 4 Spacing * 5 - for duplicate 5 As you can see, this list has a length of 6 (Number of duplicates + 1).

I made some changes to the network: Rotating Extrudes v2022 Copy.vwx

Thanks @Marissa Farrell, that helps! I updated to VW 2023 SP4 this morning.

Hello Ben, The same thing happens when I open "stand marionette in blank file.vwx". I found a workaround: before changing the height, dubble click the Marionette Object, it will show this message: Don't change anything, click Exit Marionette Script, and now it works. Don't ask me why 😄 I changed your network and added a slider that ranges from 0 to 1000. You can change the min and max values by editing the Python script inside the slider node. stand marionette in blank file.vwx

Yes, correct, I exported the file to a VW2022 version for you. Rotating Extrudes v2022.vwx

Hi CalCurated, I created the Marionette network that you described. A good way to understand what is happening is using the debug mode of the Marionette Tool (click the bug that is shown in the screenshot below). With the debug mode selected, you can click on the lines that connect the Marionette Nodes to see what data flows through them. Rotating Extrudes v2023.vwx

Hi all, The Get 3D Info node seems to have a bug. I made a very simple Marionette Network with only one 3D object (extrude) and it gives the following error: Is this a bug or did I do something wrong? Get 3D Info error v2023.vwx

For Grid Lines we use the Grid Line Tool. The tool works great in general, it saves us a lot of time when grid lines are changed and automatically updated in sections and elevations. One problem that keeps coming back in multiple projects is that the setting "Show Bubble at" changes from End Point to Start Point when we use Project Sharing. Does anyone know how to fix this?

An AI chatbot can only produce sensible answers if there is extensive documentation on Marionette and Python scripting in Vectorworks. Without enough documentation nothing can be 'fed' to the chatbot. I did some quick tests with chat.openai.com. It produced code but the code made no sense (it made up functions, stuff like that). What we need before an AI assistant: adequate documentation. EDIT: Some examples of the (nonsensical) answers ChatGPT produces:

I do, and I experience similar problems as you described.

I played around a bit with ChatGPT but I have the same experience: the AI writes code with a lot of functions that simply don't exist. I think it has to do with the very little documentation that is provided at developer.vectorworks.net.

SP2, it seems fixed. I tested a few complex subtractions and found no errors yet.

I did a quick test and in VW 2023 this bug seems to be fixed 🥳

I downloaded VW 2023 today, the bug seems to be fixed! @AlanW Thanks for your time!

@AlanW, thanks for having a look. Your setup with classes works but the hatch shown in Top/Plan view is not the 2D fill of the chosen material. An object that uses a material and is cut (horizontally or vertically) should have the Fill Style set in the Edit Material dialog I think. Or do I misunderstand how materials are supposed to work?

Hi, When I use materials in auto hybrids the 2D geometry shows a fill color instead of the material hatch. This worked perfectly fine in VW2021 but not in VW2022. See comparison: I think this is a bug and unfortunately Service Pack 5 doesn't solve the problem. Auto Hybrid Material Hatch v2021.vwx Auto Hybrid Material Hatch v2022.vwx