C. Andrew Dunning

Click the "Simple 2D" or "Simple 3D" toggle.

The LED tool lets you input the horizontal and vertical pixel counts of a given panel and then the tool will calculate the overall counts. Is this what you're asking? No. The parts of the panels can be assigned to different Classes but the assignments will be the same for every panel.

Showing my cards a bit...this is a good example of a convention being created to address 1 specific need/request that ended up up with a parade of "...what abouts..." and, actually, more functionality than originally anticipated. MANY thanks to those of you who gave valuable input!

Happy September! Assuming you've seen the announcements regarding Vectorworks 2024® and are eager to dive in...this week we posted new builds for all of our tools. These builds insure compatibility with Vectorworks 2024® and include updated content files. In terms of new features, in addition to the recent enhancements in the VideoScreen tools, AudioBox 2 has now gotten some special attention: "Yoke Up" and "Yoke Down" have been replaced by a single "Yoke" option with a variable tilt angle. Yokes now attach to truss correctly and speaker, tilt, and rotation changes are made relative to that attachment point. (Speakers no longer jump away from trusses when you make adjustments!) Speaker Symbols can now take advantage of a new "part" system, allowing you to do things like use custom yoke and clamp geometry, define custom yoke pivot points, and designate custom dispersion origins. (Be sure to see the manual for more information.) These updates are for Vectorworks 2020© and newer. If you have purchased one of our tool sets or a Producer's Pack 3 license since January 1, 2023, applicable updates are available to you free-of-charge. E-mail me for a link, password, and and a key code. (As a user, you know the address...) Everyone else, see https://www.landrudesign.com/VWPlugIns.htm for more info.

Think of them as enhanced versions of those that ship as part of Spotlight. (For example, in our version of the LED tool, weights and wattages update for "flat" walls as tile counts change. Our version of the tool also allows for mitered end edges.) Regarding the Tiling Command, because it is pretty rudimentary and has some limitations, it isn't distributed as part of our stock packages. I do share it with our users who ask - as it is still pretty useful.

I build the given array a VS4-LED (the Landru Design version of the Spotlight tool) instance for each LED panel. I then use a Command I created that adjusts image scaling and shifting so that each panel displays a portion of the whole image: Building the array takes a few minutes and applying and adjusting the image takes seconds...

If you're getting TV errors w. AudioArray 2, that is a REAL mystery... 😉 If you can send me a demo file w. step-by-step actions that produce a repeatable error I'll see if I can figure out what is going on. W/o both, it is going to be incredibly difficult (if not impossible) to figure out what might be going on.

Pros: - HP is one element. Click once and drag (no Right-Click + "Select System Objects") and all attached elements follow along. - Click HP and general weight info is displayed in the OIP. (Helpful for getting basic "order-of-magnitude" estimates.) - One name for the entire HP and one embedded label - not different names for individual truss sections or need for Data Tags.

Truth!!!

Insert one of your objects into a blank file. Run the "Export Script" command ([File][Export][Export Script...]) In the dialog that opens, select a target location and enter a name for your script file. A text file will be created containing VectorScript code required to create the elements in your VW file. Hope that helps...

I see this from time-to-time but have mostly written it off to the fact that I've got several tools that are currently in "development" mode with parameters and variables evolving.

I can replicate this w. the Landru Design version...

Can you just rearrange the stacking order of the Design Layers? 100% my pleasure. Happy to be able to help.

I actually take strong exception to the "old style" label as this approach has its clear strengths. I teach both methods - along with pros and cons of each.

You already have what you're wanting if you use the Design Layer Referencing approach instead of ViewPort Referencing. By using the former, you have full control over Class and Design Layer visibilities - both, on-the-fly (and, leveraging Saved Views) and via Sheet Layer ViewPorts. The catch is that the Referenced file's Class list then gets added to your working file's - thus, one of the main "points" if using ViewPort Referencing.