Jump to content

sbarrett

Vectorworks, Inc Employee
  • Content Count

    235
  • Joined

  • Last visited

Posts posted by sbarrett


  1. 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.


  2. 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.

     

    Screen Shot 2020-02-12 at 1.57.10 PM.png


  3. 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.

    • Like 1

  4. 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.

    • Like 1

  5. 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.

    • Like 1

  6. 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.

     

     


  7. 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.

    • Like 1

  8. 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

    • Like 2

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

    Screen Shot 2019-12-02 at 8.56.10 AM.png

     

    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.

     


  10. Perhaps you could try using the group node to group all of your points before changing their layer? In general however, I would recommend simply running the network with the layer that you want the objects to end up on as the active layer. 

     

    I also assume that it is the act of setting the layer that eats up the most time and not setting the class. Have you experimented with only changing the class?


  11. Hello All,

     

    Sorry I was late to respond to this, but there was a bug in the 2019 version of the node and I used a custom version of the Collate node. Besides the output not being lists of lists, the biggest difference between these two versions was that my custom node was looking for the number of items in each list while the default library node is looking for the number of lists. Here is a file with a slightly adjusted network that uses the fixed default Collate node in 2020. I exported it back to 2019 so that you can use this correct node in version 2019.

     

    Example 1 - Extruded Curves v2020.vwx

    Example 1 - Extruded Curves v2020 v2019.vwx

     

    • Like 1

  12. Yes, @Dishav Vasudev there is now a node in the default library that allows you to do this. Its called the Popup Dialog node and its in the User Interaction folder. the way it works is that it takes a list input generated by the script and when you run the script, a dialog pops up and allows you to choose from a dropdown of that list. 

    • Like 3

  13. You are on the right track and very close.

     

    If you want the output value to be a symbol name, it needs to be a string. In order to create a string in your script, you must use quotation marks. Assuming that HR4 is the symbol name, you simply have to put quotation marks around it to make it a string.

     

       if input == 0:
            self.Params.output.value = 'HR4'
        if input == 1:
            self.Params.output.value = 'HR5'
        if input == 2:
            self.Params.output.value = 'K4'
        if input == 3:
            self.Params.output.value = 'K5'


  14. If your NURBS surfaces always follow the same curvature and change only in the length that they lay on the floor, you can create a bunch of surfaces that are the same size, then use the Extend NURBS node to extend each in a random manner. The Extend NURBS node only takes a single length value as the extension, so inputting a random list of lengths to extend a list of surfaces should work.

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...