Marissa Farrell

@Chuck Davidson Most of the nodes will have no difference for code behavior between 2016 and 2019; the port naming is just a cosmetic change. My best guess prior to debugging this is the Rotate node, that node had a bug at one point that we fixed between these versions. I'll take a deeper look and get back to you.

@Mike Wright This is an easy fix 🙂 Marionette does not allow you to name nodes with just a number - so in this case, the Real node you've named "2" needs a different name, my suggestion is "two"

Maybe this will help - you need to use "random.randrange(value)" import random size = 50 posX = 0 posY = 0 steps = 100 for i in range(steps): vs.Rect(posX, posY, posX + size, posY + size) r = random.randrange(4) #corrected to include namespace if r == 0: posX += size posY += size if r == 1: posX -= size posY += size if r == 2: posX -= size posY -= size if r == 3: posX += size posY -= size

Here's where I'm sitting right now. The Set Record Field node is reporting that it was successful, but the field in the record isn't being updated on trusses in the Hanging Positions. I tried making duplicates of the trusses and putting them back into the hanging position without success, this is not shown in my file, (though when I do make copies and they appear on the Design Layer, the fields DO update appropriately) so it's really an issue of 'why can't I get this value to push to the object in this container?' I asked some coworkers at the office today and didn't find anyone who could help immediately, but I'll try some more next week and see if someone else has some intel. HPMarionette_MFarrell.vwx

I tried for a while to get something to work for this - but I'm having a hard time editing fields in Trusses that belong to a Hanging Position. I have no issue adding data to fields in Trusses that live outside of a HP, so I'm certain my script is set up correctly. I'll do some more digging.

Hmmm. You shouldn't need to do anything special. What is your system language set to?

I'm still not sure you're looking in the correct location. Try using the "Reveal in Finder" button in your preferences.

Can you try running the node in this file? Its purpose is to install commonly used Python Libraries to Vectorworks Python. I believe it has 5 different libraries to install. The packages will install to your user folder > Python Externals PythonLibsNeeded_v2019.vwx

@gester Vectorworks uses the Python version that comes installed in the package. Are you using 2018 or 2019? I believe in 2018 we switched to Python 3.5 for Vectorworks. It's possible that the library link in Sarah's network is not updated to download to the correct Python version. I'll need more information to help you resolve this.

Could you either share this file or a simplified version of it so I can better understand what you're hoping to do?

No problem! It's definitely a whole new world!

Generally, the libraries contain many types of corner blocks - There are L shaped and 3-way corners (please excuse my lack of industry nomenclature) in addition to other configurations. Looking at the Tomcat libraries, I see there are different configurations denoted by "C#B" which should let you know how many connections may be made off of that corner truss. (The spigoted library uses "C#S")

@Magnus Mikaelsen When inserting your symbol, make sure you have the correct alignment mode selected in the Tool Bar.

Unfortunately, I believe you cannot use a corner block unless it has connections on all ends, so since you're using the corner at the end of your truss line, the calculations will fail.

You don't need to add any more Attach Existing Record or Parent PIO nodes, you should be fine to just use the multiple Set Record Field nodes.

In many cases you won't need it, but since I needed to make sure the rectangle node was connected to the rest of the network in some way, I had to include it.

yep! That's absolutely correct.

Here's a quick example - I included a custom Popup node (I'll look into modifying the one we have in our Default Content for easier use) You may not need the Pass node as long as every node in your script is wired together in some way, I only used it because I needed to make sure that all of the nodes were connected to the network. Note: I currently have this update the record attached to the Marionette Object by using the PIO Handle (Parent PIO) node. If you want to assign it to an item inside of your Marionette Object (or if you are just using it in a standalone script), you can just wire the object you want to assign the record to there. SimplePopupStringExample_withRecords_MFarrell.vwx

I looked into this - there is something wrong with the Get Record Field node - I replaced all of the ones that existed with one from the default content library and the network now works appropriately on my end. I will note, I am using 2019, and am not sure which version you are using (though I can tell it's prior to 2019) so please let me know if you're still having an issue and I will send you a file with a new node in the correct version for you to replace them with.

It looks like you aren't getting values returned from your Get Record Field nodes (They are resulting in "<Unknown Value>"), which will affect the rest of your network. You can see that you have wires coming out of your Filter nodes that have 0 items, which will prevent the network from running correctly. I would suggest looking into why values aren't being returned appropriately from the Get Record Field nodes and going from there.

The issue is that the file name for line styles is translated in non-English versions. You should be able to change the filename in the node script to what your file is named and it should work.

Are you in a non-English version of Vectorworks? I've learned that my network may only work with English. I have a node in progress that will work in any language.

No problem! I think it's really close to what you had before, I just seem to have lost at least one node when moving things around. Creating a red symbol is easy - when creating a symbol from a Marionette Object, in the Symbol Options dialog choose "Convert to Plug-In object" You can also change an existing black symbol to a red symbol by right clicking on the resource in the Resource Manager and editing the symbol options from there. Let me know if you have any questions 🙂

If you name the Popup List node in the OIP with a name, it should appear in the OIP when converted to a Marionette Object.

Ah - I forgot to mention the step where you delete the line at the very top that starts with #COMMAND. If you delete that entire first line, the script/node will update.