SBarrettWalker

There is a way you can create this. You can use a Popup node in the Input folder. You have to edit the script inside by deleting the top line of the script and then adding the choices into the appropriate part of the script. The output of this node is the index value of the selection you make from the popup list. for example, if you have four choices: ['Red', 'Orange', 'Yellow', 'Green'] the corresponding index values will be [0, 1, 2, 3]. You can build a corresponding list of values and use a Get Item node to draw the correct value from the list. Popup.vwx

Here are a few scripts that work by placing 3D symbols at specific locations.

I believe that the output of the Get Cell Value node is already a string, so the Get String node is unnecessary. If you connect the "formula" output to the "s" input of the Text node it should work.

When a Marionette node creates geometry it is always placed in a group. The group is named based on the name of the node that created it as well as a random number - this ensures that when you run the script again, the object will be deleted and recreated, because that named group will be replaced. To edit any geometry created by marionette nodes, you will have to ungroup it first, no matter whether you use the group or ungroup nodes.

Thanks for catching that - it was an error in the script. I have fixed it and uploaded a new version - this version is also in Vectorworks 2018.

This may not be the most elegant solution, but I would rotate the poly to be orthogonal, create the grid, then rotate it back. Here is an example. Forum question.vwx

@Alan Woodwell This paper is on the Vectorworks website here: http://www.vectorworks.net/training/2018/getting-started-guides/transitioning-to-vectorworks/moving-from-grasshopper

Ah, for that issue, you simply need to check "rule" in the Loft Surface node. That will give you sharp edges.

Hello @Bernd Lützelberger, I noticed in all of your scripts that the Int node is somehow connected to the first Range node twice, which is causing you to get 42 values instead of 21 values - if you try disconnecting it and reconnecting it should work. just make sure that when you run in debug mode, there are 21 values coming from the Range node.

The only way to do this is to create a menu command. To create this kind of network, you will need an Object by Criteria node as the node that connects the object to the network. In the text field in that node you type "SEL=TRUE" and then convert the network to a menu command. The menu command will exist in Tools > Marionette Commands > [New Command]. To use it, select an object and then run the menu command. However, this may not be exactly the type of network that you are looking for. If you want to create a Marionette object with control geometry you can use a Control Geometry node instead, and then convert the network to a Marionette object. If you just want a network that references existing geometry (not as an MO or MC) then you must use a Name node. You have to give the geometry a name in the OIP, and then put that name in the text field of the Name node.

I believe this will always happen because of the nature of Marionette objects. In this way they are also similar to hybrid symbols - the 2D geometry get treated differently than the 3D geometry. If it becomes problematic for the script, you can use the Set PRefID To Ground node in the Object Info folder to set the object to the layer plane while your script is acting on it. However I do not know if the object will stay on the layer plane if you ungroup the Marionette network from the control geometry.

It can be difficult to use multiple control geometries - the best way I have found is to group them all together and make the group your control geometry. Then you can use a Contents node to access them. Once you have the list of control geometries from the Contents node, you can filter them by name or type, etc.

Hello DE, Whenever you convert control geometry and a network to a Marionette object, the geometry will most likely move. What is happening is the geometry is centered over the wrapper, and that becomes the insertion point/center of the Marionette object. You can think of a Marionette object as a symbol or plug-in object - it lives as a resource to be placed in the drawing - it doesn't remember its original location. Having multiple pieces of control geometry can also be tricky. Are the separate pieces of control geometry keeping the correct spatial relationship between each other?

Here is an updated file that does the same thing but without a custom node. It also does a third pattern. ArrayingSymbols.vwx

Hello Martin, Here is a script that places a symbol in an array based on a given number of columns and rows, and then sorts them and draws a line through their center points. There is one custom node, Reverse Lists Chunks, that allows you to reverse the order of lists within a larger list. I used this to create the line that swerves back and forth. ArrayingSymbols.vwx

Hi Martin, I looked at your file, and it is actually a weird glitch that I have seen happen once or twice. Somehow, your H pass node is connected to the sequence node twice. This shouldn't be possible - it is definitely a bug, but if you disconnect the H pass node completely and reconnect it, it should work properly. HTH, Sarah

I can tell you that when building templates, we STRONGLY recommend to leave the None class as None. There are a lot of different instances where the None class will be recreated even if you change its name, apart from scripts specifically. If it is important for your office to change the None class to 0, you can do this by mapping your classes to the AIA/NCS standard. Go to File > Document Settings > Standard Naming and choose AIA/NCS. This will set your None class to 0 and set your Dimension class to A-ANNO-DIMS. If you don't check "Enable Auto-classing" you can still use all of your office standard classes. hope that helps, -Sarah