Jump to content

Scott C. Parker

Vectorworks, Inc Employee
  • Posts

    319
  • Joined

  • Last visited

Everything posted by Scott C. Parker

  1. Hello Damien, These are great comments. I will add restore "hide unused equipment" as an enhancement request for further development. The collection of available GDTF profiles is increasing in the shared resource library, and we're working on making it easier to incorporate them. Currently, the proper GDTF mode is displayed when adding the Plug-In version of the light. The symbols are getting the "1" and are on our list to remove or replace with the mode. Grabbing the channel count is tricky. If you have one type of light but use some with one mode and others with another mode, they get split in the Key into different items. This presents a conflict when using the same symbol. We're collecting comments and working on solutions. DMX footprint could replace the GDFT mode, and I'll put in an enhancement request. Perhaps a setting to choose what data field to show which would pull from the attached GDTF file. Yes. Thanks, Scott
  2. The truss shouldn’t be a sub part of the light. Can you share the file with me?
  3. If you open the resource manager and search for "table," you'll see hundreds of results. Once you find the table shape you like, you can duplicate and edit the style that closely matches your needs and insert the table of your choice.
  4. If you make a worksheet for lighting devices and include the DMX column, you can sort by DMX, and those items 'should' appear at the start/end of your worksheet.
  5. The new Equipment Summary Tool filters are in the build window, and you can create a filter-by-layer filter. Once the filter is active, it shows all items available within the criteria selected. You are correct, however, that we currently do not have a way of filtering the key again after it has been built. This is on our list of improvements.
  6. The only way to get an approximate weight of those two vertical trusses would be to add hoists to the corner junctions and calculate. The calculation would estimate the selected system and NOT give you accurate deflection calculations for the corner blocks relating to the gear hung on the horizontal spans. Engineers would do their structural analysis of the overall system once you give them the lists of gear placed on the system. Braceworks reports are a great place to start the conversation with structural engineers, who always have the final say.
  7. Hello @matteo17 Can you post a screenshot of what you're trying to do? As for objects on the ground, Braceworks does not currently calculate loads without using hoists.
  8. This is what I do with one extra step. If you edit your Label Legend and duplicate the fields you want to magnify the text for, you can control what is shown in each viewport via classes. Let's say you want the channel and unit numbers to be huge. Make a new class for each, i.e., label/channel-huge and label/unit number-huge In the LL, duplicate the channel and unit number fields. Assign them to the Huge classes and change their text size. Once done, you can show/hide the classes in the viewports. I ignored the containers, as you can see. It's about the clarity of the numbers for the crew to read.
  9. I made a video a while back that might be helpful. I'm not sure, as I made it before Magnets showed up.
  10. True. It's based on the insertion point. I'm not saying this is good or not. Certainly, something to think about.
  11. It's on our list of wishes. No ETA on the horizon, though. The issue is that Virtual Parts are assigned to the entire type of objects, not the symbols themselves. We're keeping this in mind as the tool is further developed.
  12. A quick workaround to get you going is to insert a new column and then copy/paste the database field from an existing VP. Then, change the number at the end of the string to 4, 5, 6, etc. It should pull the next virtual part into the worksheet.
  13. Yes, it was a bug. It's been fixed for an upcoming release.
  14. Correct. The info about parts is attached to items once they are in the drawing itself. This doesn't preclude anyone from adding a custom counting record to their symbols, which can then be reported using worksheets. The added parts via records are not currently seen by the inventory system.
  15. =XROTATION(), =YROTATION(), and =YROTATION() get you the Roll, Hanging, and Rotation, but they are Read Only Functions. ='TrussItem'.'HingeAngle' returns the Hinge Angle, but edits from the worksheet likely won't take. The main issue with attempting to edit the fields you mention in a worksheet is disconnecting objects from each other. As for a master list, are you familiar with https://developer.vectorworks.net/index.php/VS:Function_Reference You'll find a huge amount of resources there. This collection of forums will be helpful as well. Many scripting developers discuss how to create tools to manipulate VW objects. https://forum.vectorworks.net/index.php?/forum/4-customization/
  16. It's coded to attach to all Spotlight objects. The data manager is also coded to receive various bits of info from the device it's connected to, which are editable.
  17. There have been several bug fixes to the existing palette covering calculations. What updates are you looking for? More improvements to power are being worked on for future releases.
  18. Oh, I completely understand. This is on our list of requested enhancements. Until then, I suggest the first workflow of adding the truss to your shared template files. Best, Scott
  19. When working on a drawing, virtual parts are saved per file and will remain attached to the objects within that file. To make sure that you have access to the pins you need, it is recommended that you add them as needed and save the file as a template. Alternatively, you can add the pins to the truss symbols and save the file as a favorite. This allows you to copy and paste the symbol into a new file easily. When you do this, the pins should come from your favorite file to your working file. Virtual parts are attached to the entire collection of particular object types within a drawing. This means that all the truss in the drawing will receive the same list of virtual parts. To address this, it's recommended that you add all the virtual parts with a default quantity of zero to all the various truss you are using. Then, select all of one type of truss and change the appropriate pin type quantity to 4. Repeat this process for the other type of truss as well. When you create reports, the virtual parts with zeros do not appear in the worksheets, so you can be sure that your report accurately reflects the parts you actually used.
  20. Have you discovered the new EntEquipUniversal record which is now getting attached to all Spotlight objects? You can attach it manually to any other symbol and it'll be pulled into your reports. You can also edit it and add new fields and it'll still get attached to lights, truss, etc. As long as it keeps the same name.
  21. Regrettably, the present worksheet layout is all we have, as the independent virtual parts data signifies items absent in the drawing. Rest assured, transposing this information into an improved list format is on our radar.
  22. I've filed a bug report on the lack of seeing clamps when more than one is included in the library symbol. As Steven mentions, changing the symbols to geometry should have them appear visually.
×
×
  • Create New...