Jump to content

sbarrett

Vectorworks, Inc Employee
  • Posts

    285
  • Joined

  • Last visited

Posts posted by sbarrett

  1. I have not tried moving the Keynotes into the annotation space, but they are fine outside the viewport. As far as classing, it is up to you however you want to organize your drawing. Classes are meant as an organization tool for you and your team. If you already have dwgs of manufacturer drawings you can import them into Vectorworks and save them as symbols. You may also be able to download dwgs from the manufacturer website. As far as issues with Notes Manager, I am sorry I don't have any more ideas.

  2. 1. If you only want the prefix to show up as a Keynote in your drawing, the prefix should not be a part of the note. When you select the note to be placed as a Keynote you can set the appropriate prefix.

    2. I believe if you save your document and then restart Vectorworks the last notes database selected will become the active database.

  3. 1. and 2. Styles are the way to save plug-in object resources. (plug-in objects are anything that is "smart" - has multiple parameters and settings that allow you to customize it). The title block border is plug-in object, as well things like doors and windows. A style will show up in the resource manager as a "red" symbol - the text of the name will be red. A style lives in the file it was created in. If you want to put it somewhere else, you must import it (or drag and drop it) into another file. All resources are stored within files, so your Favorites folder will contain .vwx files with resources. To add a resource to your favorites, either create a new file, import that resource into it, and save that file to your favorites, or if you already have favorites files, import resources into those existing files. I know the system is a little different than AutoCAD, but the most important thing to remember is that resources are ALWAYS stored within files, and in order to have resources available in the Resource Manager, those FILES must be saved in an accessible location like a Favorites Folder.

    3. To scale the image within a texture, go to Set by Image in the texture editor and drag the bar to a certain distance along the image and then type in the distance below. For example, if you have a ceramic tile texture, you can align the bar to the length of the tile and type in the length of the tile in the box below. To edit a texture, right-click on it in the Resource Manager and choose Edit. If you like, you can create multiple textures from the same image at different scales - just duplicate and edit the copy.

    4. To nest classes, put a hyphen after "Dimension" in each of the names and make sure that you classes are set to be viewed in Hierarchical Display.

    5. Activate Titleblock allows it to be calculated in worksheets. Titleblocks should always be activated unless you have so many title blocks that performance is affected. And by many I mean hundreds.

    6. To create a template file from a current file, simply delete the geometry in the design layers and then Save As Template. All the classes, layers, sheet layers, and resources will be in the template file when you open it.

     

    • Like 3
  4. Dimensions can be associated from any design layer, and also from the annotation space of a viewport. If you are planning to dimension the same object in drawings at multiple scales, I would recommend putting them in the annotation space of a viewport. Otherwise, the same layer in a different class works too. It is really up to you, whatever works best for your workflow.

  5. I don't think Get Degree get you any useful info. It is a degree of curvature that is specific to NURBS, so it will be a value of 1 if the point is a sharp angle, 2, or 3, etc. for less sharp angles - it is a value that is specific to NURBS geometry and not a real-world degree value. I believe what you are looking for is the Normal value of a Surface at a certain point. There are NURBS nodes that give you the Normal - the direction of the vector that is normal to the surface at that point. You can use this value to orient objects along a surface, for example. I can't remember the exact name of the node or nodes, but it should have the word Normal in either the name or the output value.

  6. You can extract a point anywhere along a NURBS curve and get the Z value, but the point has to be relative to the length of NURBS curve, not the coordinate space. Get degree gives you the curvature of the NURBS curve at that point, I don't think it will get you the Z value.

  7. Hi @KroVex

     

    In the script that I created, there are two levels that aren't associated with layers in the stories, and to create those I made a custom node that creates default levels that are not associated with layers and then adds them to each story. I did not associate them with a layer after creation.

    Screen Shot 2021-07-21 at 10.26.35 AM.png

     

    This is the script inside the "Create Layerless Default Story Level" node - I simply used a blank string for the layer name.

    Screen Shot 2021-07-21 at 10.37.28 AM.png

     

     

     

    Screen Shot 2021-07-21 at 10.31.54 AM.png

     

    This is the script inside "Add Default Store Level to Story". If the default level does not have a layer name associated with it, it will not create one when added to a story.

    Screen Shot 2021-07-21 at 10.31.49 AM.png

     

  8. The sure way I have found to set the stacking order of objects is after they are created, you put them through an ordered list node, put that list through a group node, and then an ungroup node. The group node puts a copy of each object in the group and deletes the original, so the objects are recreated in the appropriate order.

    • Like 1
  9. I made some changes to the network. Mainly, instead of having the object sent through lots of different Set Record Field nodes at once, I had them pass one through the other. This may not have been necessary but it seems to have fixed the problem. Also, there were a few of the Set Record Field nodes where the Record Name string was not attached. In order to convert this to a menu command and have the fields pop up (instead of being available in the OIP), you can replace the purple Input nodes with User Interaction nodes. There is a User Interaction folder at the bottom of the list of Marionette node folders. These nodes produce dialogs that pop up every time you run a network.

    Cavity Barrier-SB2.vwx

     

  10. No, it is not necessary for the particular network you are creating, but if you want to look for specific types of IFC objects, that is a helpful node. The other thing I did was change the info in the Obj by Criteria node. You can't run a network on selected objects, because a node within the network always has to be selected for the network to be run. The only way to use Marionette on selected objects is to convert the network to a Menu Command. You can do this once the network is complete, but while you are building the network, the Obj by Criteria cannot refer to Selection State.

  11. If you are using Vectorworks 2018, then I believe the menu command you are looking at is IFC Data Mapping. What you are seeing with "[Object.VW_Name] ELSE [Object.IDPrefix] + [Object.IDLabel] + [Object.IDSuffix] ELSE 'Window' " is the Field Value that is generated from pulling information from the Window object itself. With the Get IFC Property Node, you need to input the Field Name in order to get the Field Value. I believe in your example, the Field Name is Reference or IFCReference or something along those lines. When you input that into the node, the output will be the string value for this formula: "[Object.VW_Name] ELSE [Object.IDPrefix] + [Object.IDLabel] + [Object.IDSuffix] ELSE 'Window' ", or whatever the Field Value may be for the particular object you are querying.

  12. You were almost there. You got the list of vertices correct, but the hPoly input of the Change Vertex Type node needs to have the correct polys compared to the list of vertices. What I did was I "repeated" each of the poly handles so that the polys and vertices matched. I didn't duplicate them, I just repeated their handles in a list so the node would know to go back to that poly each time. This is one of those times when it is important that you have the same list lengths going into the inputs because if they are not the same length, the last item in the shorter list will simply be repeated over and over until the longer list is complete.

    Fillet multiple polys v2021 SB.vwx

     

    • Like 1
  13. I am not aware of any way to automatically ungroup geometry. FYI, the reason that Marionette scripts create groups is so that the geometry is "tied" to the script. The script not only creates a group, but names that group with a name related to the script, so that when the script runs again, the named group is deleted and replaced.

    • Like 2
  14. 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.

     

     

     

    • Like 2
  15. 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.

×
×
  • Create New...