Jump to content

C. Andrew Dunning

  • Posts

  • Joined

Everything posted by C. Andrew Dunning

  1. Use the LED Screen tool (or, our VS4-LED) and choose the "Vert. Strips" "Base Structure."
  2. Mark - The "LYON-W" Symbol (the one NOT including the pull-back - in the file you sent) contains both Generic Solids and the embedded "Rigging Frames" Symbol. It is that Symbol that is causing issues. As to "non-Hybrid," the tools should throw errors w. that...
  3. Mark - I found the issue in the file you sent: The Symbol contained an embedded Symbol (the rigging frame) and AutoHyrid was failing at that. I converted the embedded Symbol to a group (Cmd-K) and all worked beautifully. Now...rendering/regen time w. something that detailed is another story, entirely...
  4. The Autohybrud system might not be sure what to do w. some elements. Shoot me a copy of the file and I'll take a look.
  5. DEselect all geometry. See the latter pages of the ATS manual for more detailed info on the data Symbols need and the correct formatting.
  6. Mark - At-present, the tools only recognize the 3 speaker types and a single bumper type. That being said, you CAN trick the tools by creating a speaker Symbol (w. all data attached) that is actually the pull-back bar. That Symbol would then become one of the 3 types in your array.
  7. Your signature says "VW 2019." Would you confirm that that is incorrect? (The stock Spotlight audio tools earlier than 2021 don't support Symbols...)
  8. @Mike Ross, see the attached file. Is this what you're wanting to do? If so, look at how the 2 projectors are formatted - in terms of both the geometry location relative to the Insertion Point and the dimensions entered in the attached Record. UST_Demo.vwx
  9. You can add those things to DLVPs already raked but you are correct in that you can't adjust rake for DLVPs containing those objects. This is not new.
  10. You might want to double-check that. I just created a quick raked DLVP. Works as-expected. Now...what does NOT work is fixtures' auto-focusing from within DLVPs. DLVP_Demo.vwx
  11. You have to have at least one Lighting Device in the "source" Design Layer. Insert a "Dummy" fixture and hide it.
  12. Whether P&M exists or not, you can accomplish the same thing (w. a lot more control) using Design Layer ViewPorts.
  13. @jayden.s, at-present, your best option is, as you're thinking, to illustrate resolution changes using the content you map.
  14. ...so..."Flip" IS what you want but (st-present) speakers can only be tilted +/- 90┬░ and, to do that face, you'd need ~126┬░. It looks like you'll need to create a "B" version of that Symbol - one w. the un-rotated/un-flipped orientation rotated -90 while in Top/Plan.
  15. Send me a file containing the Symbol and some sort of indication of which face you want to be "bottom..."
  16. Did you try the "Flip Orientation" toggle? That and "Actual Tilt Angle" might give you what you're wanting...
  17. Posting this in multiple places as I'm getting repeated inquiries regarding this... Many users are having issues with certain bumper and speaker Symbols when used with our Audio ToolSet 2 tools and the stock Vectorworks® audio tools - mainly, when building arrays. They're seeing things like arrays with HUGE spacing in-between elements, guide-lines being WAY longer than the bumpers and speakers of which they are part, and Symbols in the Array Config dialog preview boxes displaying at a fraction of the desired size. (Sound familiar??) The problem is that in very early versions of the "__ATS-BumpModData" and "__ATS-SpkrModData" records the different dimension fields ("Front Width," "Depth," "Thick," etc.) were defined as "Number" fields defined as Dimensions. This was all well-and-good as long as "Imperial" Symbols were never used in "Metric" models and vice-versa. When this happened, Vectorworks® got confused and did things like thinking 520mm is 520'. This was fixed several years ago but some of the content in Vectorworks'® catalog has not been updated, yet. So...if you're seeing this sort of thing...while the file containing the Symbols you wish to use is open...: 1) In the Resource Manager, right-click on either the "__ATS-BumpModData" record or the "__ATS-SpkrModData" record and select "Edit..." In the dialog that opens, all of the entries in the "Type" column should be "Text." One-by-one, select the entries that are not and click the "Edit..." button. In the "Type" Pop-Up, select "Text." Click "OK," fix the next one, and so-on. When finished, click "OK" to close the "Edit Record Format" dialog. 2) Still in the Resource Manager, right-click on the problem-child Symbol and choose either "Edit 2D Components" or "Edit 3D Component." With NOTHING selected (click in open space), click on the "Data" tab of the Object Information Palette. Either "__ATS-BumpModData" or "__ATS-SpkrModData" will be in the "Record Format" window. Select the given record and check and/or correct the dimension values that will be in the lower part of the OIP. MAKE SURE EACH VALUE INCLUDES THE APPROPRIATE UNIT MARKER (',",mm,m, etc.). As mentioned above, you might find things like 520' that should be 520mm. When all is correct, click the "Exit Symbol" button in the drawing space. Save your file. All should be good - though you might have to click the OIP "Update" button for the different object instances in order for the changes to take effect. I hope this helps some of you...
  18. Have you looked into either the Spotlight Soft Goods tool or our SoftGoods 2 tool?
  19. 2 comments / bits of info: 1) The record attached to the bumper in the demo file was an old version, one in which the different dimensions were held in "number" fields. When switching back-and-forth between Metric and Imperial (or, using Symbols created using the other unit convention), VW got confused and tried calling Metric dimensions "Imperial." The new Record format changed those fields to "Text" to fix this sort of issue. 2) When using these fields, the units marker must be included so VW knows what the number means when translating it from text. The dimensions can use whatever length units are desired - as long as the unit marker is included. This will allow, for example, "Metric" Symbols to be used in "Imperial" files. See attached. Same bumper in each array, one defined using Metric dimensions and the other, Imperial. Audio_Units.vwx
  • Create New...