Jump to content

Scott C. Parker

Vectorworks, Inc Employee
  • Posts

    534
  • Joined

  • Last visited

Everything posted by Scott C. Parker

  1. Do you have a workflow/use case example in mind? You can obtain so many items via linked text fields inside the title block that it's almost like the title block is already a de facto data tag.
  2. Thanks. Test files like the one at the start of this thread, which includes attempts to use Data Viz settings, would be helpful.
  3. I haven't played with this, so I don't know if it's already supported. I'd need a test file to play with. If it doesn't work, it's a great suggestion to add to our wish lists.
  4. In my main template file, I have several different summary keys, each in different layers for my different departments. Lighting, rigging, electrics, etc. Then, I have them in sheet layers via viewports for each type of paperwork. If I use the same objects/symbol that are in the saved summaries, all I need to do is remember to refresh them and I'm good to go.
  5. I don't know if we have one yet. Never hurts to have more. Thanks.
  6. I think you can do this in the Equipment Summary Key. I would think it should also work in the legend. Can you post a sample file to play with?
  7. If you create a summary key in a template file and you use the same symbols you used when you created the key, it should be present each time you start a file using the template.
  8. Robert, Explore schematic views. https://app-help.vectorworks.net/2025/eng/VW2025_Guide/LightingDesign2/Creating_schematic_views.htm?rhsearch=schematic views&rhhlterm=schematic views view
  9. I've had success with using duplicate along path and with duplicate array for hoists and using the centerline of the truss as the path.
  10. It was. Added yours to the list. I'm working on a task to add the single and distributed functions now avail w lights to the hoists. It'll take some time.
  11. @Stefan B. You've found a bug. I've reported it. Thanks, Scott
  12. This is a nice symbol. Have you made versions with various sized opening of the screw jaw? I would use these when making drawings of scenery that's held together using these. As seen here.
  13. Would you mind sharing a sample file showing this issue? We'd like to know if this is an actual bug that needs to be fixed or if it's a scaling issue between layers, etc. Thanks, Scott
  14. Sort of. It depends on how you are managing your symbols and the wattage info. If you're simply changing the wattage of the symbol and don't care about showing it on the plot, other than a legend or tag, the symbol remains the same. If you use the actual symbol in the resource library with the 750W cap, then it's a separate symbol. You get a bit creative depending on how you want to show the info and how you want to report it. Here, I have 11 bodies of a 26° light. In the symbols area, I have 10 at 575 and one w 750. In the Plug-in area, you see I also have 11 bodies, but I've entered different wattages in the wattage/power field of the light. On the right, I have 60 bodies at 575 and just three with different wattages. Notice that "750" is treated differently than "750 W"
  15. I haven't tried this, but if I wanted to do what you're doing, I would try it... Have you taken a hoist and edited the hoist symbol's overall shape to give a visual offset? I'm wondering if you place a larger invisible shape in the symbol and then move the visible parts to one side; the middle of the symbol would snap to the middle of the truss, but the visual image of the hoist would be offset. Braceworks would still calculate based on the centerline of the load objects. Yes, it's a workaround until when/if the feature can be developed.
  16. Funny you should mention...
  17. Could you send me a test file I can share with the programmers?
  18. I discovered this the other day and filed a bug. Please post a screenshot of what you see with the non-working form so I can submit an internal bug report. Thanks, Scott
  19. This is the hoist and truss establishing their connection for load calculations. What kind of modification are you looking for?
  20. The z-fighting is still an issue. For rendering and visual needs, setting the base structure of the LED walls to none removes the z-fighting conflict. Though this isn't a fix for the underlying issue, it does help for presentation needs. If you also want to show the thickness of the tiles behind the image, I suggest extruding a shape or duplicating the wall and pushing it back a few mm. One shows the blocks, and the other the image.
  21. They do not yet exist. The connector is present, though, so making a copy of the Edison breakout and editing the 3D parts will allow you to replace the Edison connectors with Powercon True1 connectors. Then edit the 2D for the text. To have the cables insert properly, edit the lighting symbols as well. Change the attached record with the new connector. You'll need to use this text to have True1 show in the lighting unit OIP. "NAC3FX-W and NAC3MX-W" You'll find the "UniversalName=" text in the CableConnectors.xml file in libraries/defaults/cable tools. Avoid editing the XML file. It'll break things.
  22. Sorry, no, not at this time. As the info is trapped inside each cable run, making actual database worksheets is not possible. Hence the two versions of plain reports supplied. We're doing some magic in the background to parse the info for plain counting. Each cable inside a cable run is a "sub part" and worksheets don't like listing the parts vertically. This is why the parts can be shown across using the .1, .2, indicators for each column.
×
×
  • Create New...