Jump to content

sbarrett

Vectorworks, Inc Employee
  • Content Count

    226
  • Joined

  • Last visited

Community Reputation

157 Spectacular

About sbarrett

  • Rank
    Journeyman

Personal Information

  • Location
    United States

Recent Profile Visitors

2,334 profile views
  1. 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.
  2. I hadn't either, but this was a request from my landscape architect colleagues and they tell me that is what it's called! I think it's a great name.
  3. Version 1.0.0

    49 downloads

    This Marionette object creates a Gravity Wall based off of a folder of symbols and a poly line. The poly line is the path of the Marionette object - to edit the poly line, right-click on the object and choose “Edit Control Geometry.” Within the Object Info palette (OIP) of the Marionette object, you can set the overall wall height, the angle at which the wall is slanted, and the pattern of the different symbols that will make up the wall. You can also offset this pattern on each row. It’s important that the only symbols in the referenced folder be ones that you wish to use as blocks in the wall, and that each block symbol should have the same Z height - if the blocks are different heights, the wall will not be able to accommodate them. In this file, there is also a network form of the script. This functions in a similar way to the Marionette object, except it creates a wall based off of a referenced poly line (a poly line that already exists in the document) instead of control geometry. To reference a poly line, give that poly a name in the Name field in the OIP and then reference that same name in the network. GravityWall.mp4
  4. 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.
  5. Yes this is correct. 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
  6. 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.
  7. I realized what was wrong. In your original script in the 2019 version, you had the prime value input into the Line node, instead of converting it to a point first. For some weird reason, this worked in 2019. I have updated the script so it works in 2019 and 2020. The other exciting thing is that in 2020 there is a big improvement in graphics performance. Swirls v2019-SB.vwx Swirls v2020-SB.vwx
  8. Also, this network is super fun to play with! Just to try it, I converted your Integer Swirl to a Marionette object with sliders and also added the ability to fill the objects with a range of colors. Swirls v2019-SB.vwx
  9. Is there a reason why you can't substitute the Count, Add List, and Int nodes for a Get List Length node because essentially isn't that what you are doing? Do values in the prime series repeat?
  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
  12. I am not sure what that error means, but I added the 2019 version to the post itself - maybe you will be able to download it from there.
  13. Version 1.0.0

    67 downloads

    Creating stories, levels, and layers can be a tedious process, especially for tall, multistory projects. This wrapper allows you to automate that process based on an overall building height, typical floor heights, and default levels. You can create up to 4 Layer Levels and 2 Layerless Levels. To create fewer Levels, leave any of the Layer 1, Layer 2, Layer 3, Layer 4, Layerless Level 5, and/or Layerless Level 6 fields blank. To use this script in a new file, simply import the wrapper into the file, place it in the drawing, and run the script. The settings of the script are very similar to the levels and layers created in the Vectorworks template, but you can customize them in the OIP of the wrapper. To change the Story suffixes and Story names, double click on the wrapper and the select the Get Story Names node. There are settings that you can change in the OIP of this node as well. NOTE: Existing stories and story-associated layers that match the names of the new stories and layers will be deleted every time you run this script. Existing stories that DO NOT match the names of the new stories will not be deleted but may interfere with the creation of new stories. It is recommended that this script is run in a file without existing stories, levels, or story-associated layers.
  14. 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.
  15. No this is not possible with Marionette as it is not possible to attach/associate the parametric record of a Vectorworks Door to an object that is not a door. However, in Vectorworks 2020, we have added a Barn Door configuration to the Door tool so in Vectorworks 2020 this Marionette object is no longer necessary.

 

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