MOVE extrude geometry in a series of points

[MOVE extrude geometry in a series of points]

@Sebasrougs when you create your list of points to move your duplicates, you need to use the Mix2 node and select the Cross Reference mode in the dropdown. You need to create XYZ coordinates of every possible combination. 

[Attaching room numbers and names to polygons and Spaces]

What you are talking about is the same idea as this file. This takes loci and nearby text taken from a survey and converts them to the Existing Tree PIO. It could be adapted to the Space object. Because the Space is a path-based object (each Space shape is potentially unique, based on a path), you would have to adjust the script a little.

 

 

 

[Creating OIP controls?]

Most nodes new nodes will work in 2016 because they use pre-existing python functionality, but some nodes have Marionette-specific functionality, such as the Valve node, the Slider node, and the Chart nodes.

[Text height/size]

Hello,

 

You need to use the node "Get Font ID" between the String node and the iFontID port of the Set Char Properties node. When in doubt, check that the prefixes of the output and input ports match. (They won't always match because of generic prefixes like "item" and "list", but they can be helpful in these situations.)

[Create Focus Points from objects or text]

I am coming in a little late to this conversation but I created a network for Landmark users a while ago that sounds very similar to what you want. Now that you have gotten started, you may not need this, but it might still be a helpful resource.

 

 

[Reshape handles on marionette objects]

Once you move the control points of a Marionette object, they will stay that way. What I would recommend is naming the Control Point node so it's values will appear in the OIP of the Marionette object. You can manually reset them there if you need to.

[Run Marionette on selected objects]

Hi @halfcouple - you are correct in that you have to use a Menu Command to run a network on selected objects, you cannot do it with a regular network or a Marionette object. You can give yourself access to options in a menu command by using the nodes in the User Interaction folder in the Resource Selector. If you replace the regular input nodes with these dialog nodes, when you run the command, dialogs will pop up for each node asking what you want the parameters to be.

[Reshape handles on marionette objects]

Yes, you can use a Control Point 2D node. I have added it to one of your Marionette objects.

 

rectangles with grids.vwx

[Data tagging objects with marionette]

I have edited the node so that the "result" shows up and the associated data tag is now an output as well. This network will work when running it on a single design layer, but because of how Marionette works (creating groups of objects), placing them on multiple layers at the same time is rather tricky and I don't recommend it. Also, I don't recommend trying to use this with viewports. If you are tagging objects in viewports, I think using the data tag as-is works better than trying to script it.

DT_AssociateWithObj.vwx

[Data tagging objects with marionette]

Hi @Martin Lerch, I tested it and it appears to work great. The issue that you will have is that any geometry created by a Marionette script will be grouped. after the script is run and you ungroup the data tags, they appear to be associated properly with the space.

 

I would recommend having the data tag also be the output of the script, that way you can manipulate it further along in the script (after it has been associated) if you wish.

[Data tagging objects with marionette]

You can do this by choosing "Select Eligible Objects Mode" in the Mode bar of the Data Tag tool. If your tag is set to read a field from the Space object, you can hover over a Space with that Data Tag style selected and all spaces will highlight red. This works with any object type that the Data Tag is looking for. I took a screenshot of it using Doors and a Door-specific tag.

 

[Data tagging objects with marionette]

Hello Martin,

 

There are no default nodes, but there are a few scripting calls that have been added to Vectorscript and Python in 2019. You can find them here. https://developer.vectorworks.net/index.php/VS:Function_Reference#Data_Tag_Interface_Library

 

In order to place a data tag, you could use the Symbol node and then I imagine you could create a custom node that uses the first command, https://developer.vectorworks.net/index.php/VS:DT_AssociateWithObj, to associate it with a Space. I think this would work if you are placing these Data Tags in design layers, but if you are trying to place them in the Annotation Space of a viewport, I would recommend adding Data Tags manually. There is a way to tag all relevant objects at once, so I imagine a script wouldn't bring much added efficiency.

[can Marionette isolate letters from a word]

Yes, there is a node called convert to Poly Group. Here is a quick example of how to use it.TextToPoly.vwx

 

TextToPoly.vwx

[Help with understanding List on creating a Truncated Cone]

Hey @Todd Drucker - I am excited to see you have started with Marionette! The first thing to remember though, is although Marionette is the same type of tool as Grasshopper, it's based off of Vectorworks' functionality and just as Grasshopper is based off of Rhino's functionality. Marionette doesn't really have an equivalent to "Morph" - some people have created arrays along surfaces with it, but they usually have to do it mathematically. There is however a command in the model menu called "Create Surface Array" that pretty much does this. It take a 2D or 3D object and arrays it across a NURBS surface, So I think you might have better luck if you model the column using curves and a loft surface (you can create this with Marionette if you like or just model it manually), the modeled pattern, and then use the Surface Array command. Tip, if you convert the 3D object to a mesh, it will morph around the Surface Array.

[Set Record Field for several identical items]

I think you could try using a Mix2 node and choose the Cross Reference mode in the Object Info palette of the node. The important thing for list handling in this instance is that there are the same number of values flowing to each input. The Mix 2 node allows you to repeat values in the way that you want.

 

Mix2 Cross Reference Example.vwx

[Bulkhead tool]

Actually, if you uncheck smooth corners, you don't need the Change Vertex Type node at all, so you can remove that whole section.

[Bulkhead tool]

also, you should remove the Get 2D Vertex node and instead connect the Series node directly to the iIndex input of the Change Vertex Type node - its looking for integers, not points.

 

[Marionette Object > Symbol]

I am not sure what is going wrong here based on the image. Can you send the file?

[Obj by Criteria. Selected to Wrapper and Command won´t work]

When you use the "Sel=True" criteria in an Obj by Criteria node, the network will ONLY work once the network becomes a Menu Command. So when you are building that menu command, use a different criteria to test the rest of the network. When everything BUT the Obj by Criteria node is set how you want it, you change your criteria to be Sel=True, wrap it, and convert it to a menu command. 

 

As far as your wrapper in that file, I believe it is because the name of the wrapper is only a number. If I delete the name it works fine. When naming your nodes, you can use numbers but only after letters. If you use numbers at the beginning of the names of your input nodes, the numbers will disappear when the network is wrapped and instead be used to order the inputs in the OIP.

[Solid Boolean node operation in the Marionette Object OIP]

Unfortunately it's not that simple. The dropdown from the Solid Boolean node can't be exposed in the OIP of a Marionette object. In order to have the functionality exposed, you have to use a Valve node and place two Solid Boolean nodes in the drawing, where the Valve node would turn on and off the two Boolean nodes, depending on the True or False value you give the Valve node. The True or False value can be made accessible in the OIP. This would give you access to two of the Boolean functions. If you want access to all three Boolean functions, that makes it even more complex - I believe you could do it with multiple Valve nodes, but I would have to test it.

[If Node List Handling Confusion]

This is how default list handling happens in Marionette nodes. When a node receives input lists of multiple lengths, it repeats the last value of the shorter list until it has run through all the values of the longest list. You see this in nodes that are built to "expect" lists that are the same length, such as geometry creation nodes, like the Circle or Rectangle node. There are certain nodes that have special list handling, but it is usually mentioned in the description. In this instance of using the If node with multiple list lengths, you can use a Mix2 node before the If node, and you can decide with that node how you want the lists to be handled.

[Set Story Elevation not working?]

Hi @Nomi - The reason this is not working in your node is because vs.SetStoryElevation() takes mm as the input. You need to convert your document units to mm and then use that value as your elevation. I recently posted a network that creates a series of stories based on an overall building height. There is a Set Story Elevation node in that network that shows how to do this.

 

 

[Weather Analysis Tools]

5 hours ago, jpccrodrigues said:

Just one situation to report: the precipitation chart doesn't work for my location. I attach the file so you can see if it is something from my location (absense of data?) or

 

Yes, unfortunately the precipitation data can be incorrect - these weather stations will often report precipitation as 0 when they should be reporting it as "missing" or "unavailable." It only seems to be true of the precipitation data. I haven't been able to figure out a solution.

[Where's a marionette network supposed to "live"?]

17 minutes ago, line-weight said:

Regarding using a network without making it a menu command... whether it's in the form of a symbol or not, the idea is that you place it into the drawing space of whatever you're wanting to use it to work on, and then delete it from there once it's no longer needed?

Yes this is correct. 

 

18 minutes ago, line-weight said:

Once it's in the drawing space, what does and doesn't it act on - does it act on anything in that file, or just on that design layer?

It depends on the network/wrapper. Whatever the criteria of the network is, that is what it will act on. Most menu commands are created to work on selected objects, which is not possible with regular networks (because the network and the network alone must be selected in order to run),  but if for example your network is set to look for every rectangle and change the attributes of them, it will do that, no matter what layer each rectangle is on. I have attached an example file doing this - each rectangle is on a different layer, and no matter whether the layers are visible or not, modifiable or not, the rectangles are changed by the script. If you want to specify layers or perhaps visibility, you can do that with the criteria node. To test this out, go to the criteria node in this script and add the criteria of visibility.

 

Marionette Criteria Test.vwx

[Where's a marionette network supposed to "live"?]

hello @line-weight - the Marionette menu commands that you create live in a file in your user library. 

 

You can see in the image that I have a single menu command: Rotate X 90. If I wish to remove that menu command, I can open that file, go to the resource manager and delete that wrapper. If I wish to edit a menu command, its a little trickier. I can open that file, place the wrapper in the drawing space, edit the wrapper then RESAVE it as a menu command. If you give it the same name as the old menu command, the new one will replace the old.

 

If you wish to save a network to use in multiple files but NOT turn it into a menu command, you can simply wrap that network and save that wrapper as a symbol. If you have "Convert to Plug-In Object" checked when you convert it into a symbol, it will be a wrapper when you place it in a new drawing. You can transfer it to other files just like you would transfer a symbol. You can also see in the image of my Resource Manager that I have a favorite file called My Custom Nodes. That is where I keep custom Marionette nodes as well as wrappers in the form of networks that I may wish to use in multiple files. It's easy for me to import from that Favorites file into any open file.

I hope that helps.