Jump to content

C. Andrew Dunning

Member
  • Posts

    1,032
  • Joined

Everything posted by C. Andrew Dunning

  1. Answering some of your "content" questions...: 1) You can create/use custom projectors. The tools will "see" projectors in your current file and in any VW files found in "\Libraries\Defaults\Video Screen\Projector Models." 2) You can find more detailed info on creating models in the manual found @ http://www.landrudesign.com/VWPlugIns.htm. You might also find this video to be helpful: https://youtu.be/ceP2MOpkGMI. It is several years old but the information is still quite relevant. 3) While I don't know of any extensive commercially-available projector libraries, I do know of several users who have developed some pretty impressive models. You might try inquiring here or in the Facebook Spotlight group. With the current state of our industry, I wouldn't be surprised if some of those users started baking their libraries available. 4) Creating unconventionally-configured projectors is definitely possible - no hacking necessary. It is simply a matter of how Symbols are created. I've attached a quick sample of what might be possible. I hope that this helps to answer at least some of your questions. UST Demo.vwx
  2. Agreed 100%. That is, by-far, one of the biggest things I've learned from the VW engineers who have worked with me along the way. With the initial licensing of the video tools came A LOT of work aligning them. In looking back, WELL worth the effort...
  3. You pose some good questions. As the developer of two of the tools you cite (and, a vocal critic of things that bug me, too...), I'd like to offer up a little food-for-thought: For the most part, Video Screen (or, VS4-Projection) lends itself well to being an "OIP-driven"/"one-wrapper" tool. For each object instance, individual parts are relatively few and dealing with the "whole" is fairly simple. Speaker Array (or, Audio Array 2) is another animal, entirely. An array can contain a bumper and 3 different speaker types - which, together, can comprise 40+ array elements, each inserted at different angles and tracking different data. This would be INCREDIBLY difficult to configure through the OIP alone - and, would be a huge time-hog as you'd need to wait for each and every adjustment as the OIP makes changes real-time - not to mention not being able to see the whole assembly until you had done that waiting over-and-over. Also, because a populated array is a "parent/child" or "master/slave" assembly, you can do such things as display dispersion for individual cabinets or easily create reports like hang sheets or circuiting charts - with each speaker being entries in the reports. Granted, not necessarily ideal, but I hope that sheds at least a little light on some of the "whys" behind those 2 tools. As to the stock audio tools not inserting actual Symbol geometry, you are quite right. In their current form, the tools don't do that. If inserting Symbols is important to you, you might want to take a look at the Landru Design version of the tools (links in my sig).
  4. The "Convert to Group" Command (Ctrl-K) is different from Grouping objects. That command "disconnects" the object geometry from the code that created it. If you evoke that command while in a 3D view, you'll end up with rotatable 3D geometry. That caveat is that you'll also be eliminating all of the Plug-In Object functionality. Make sense??
  5. At-present, the only way to do this without converting the LED object to a Group is to use a rotated Design Layer Viewport.
  6. What is the call to get the ID of a defined Text Style...assuming the name of the Text Style is known?
  7. Audio ToolSet 2: 3.01 SoftGoods 2: 2.300111 StageLift: 1.3201 Staging ToolSet 2: 2.41011 Stanchion Layout: 1.0302 VideoScreen 4: 5.10022 Producer's Pack 3: F
  8. You might look into the Saavy Linesets tool: https://www.benghiatlighting.com/software/products/ls-1.
  9. Also...see the "Refresh Hoists" command. Essentially, what your toggling is triggering...
  10. I'm sorry, the script/Command is only available by special-request to license holders of the Landru Design versions of the tools.
  11. My workflow: Treat VS4-LED/LED Screen instances as individual panels. Build the wall. Use a script I developed to map an image across the array. Delete the panels I don't want. While not as automated as you're probably seeking, doing that actually does work quite well.
  12. Go to [Spotlight][Hloists][Set Hoist Number and Dimension Display...]. In the "Show" Pop-Up, select "Hoist Label and Hoist Number." The "Label" is the prefix you're seeking. Turn OFF (un-toggle) "Relative X,Y On Plot." Click the "Set Hoist Data Display..." button in the OIP. Click in the "Display" column next to "X" & "Y" (#s 55 & 56). Click OK. Do you get what you want???
  13. I just found this old thread. MANY thanks to you, Pat!!!!!!
  14. At this point in time, as you've discovered, Video Screen doesn't understand overshooting. Truly sorry and now on The List...
  15. In the column header for drape count, try entering "=VALUE('Soft Goods'.'TtlDrpCnt')."
  16. For our present users interested in staying current and for anyone just looking for simple ways to improve productivity, we have just uploaded a few minor updates to our tools. In addition to the usual refinement here-and-there, 2 things you might notice: 1) We've been working with a few Audio ToolSet 2 users in adding a few fields useful for users working in the installation end of things. 2) For those of you who like the look of the graphics produced by the stock Callout tool but who want the convenience of that feature included within in your plug-in instances, SoftGoods 2 and all of the Audio ToolSet 2 tools now include text bubble options: Current users of our tools can use the usual links and passwords to get these updates. If you're not using our tools and want more info, visit: http://www.landrudesign.com/VWPlugIns.htm. Have a good one!
  17. Correct. There are 2 things going on, here: You can select a Class for one or more of the individual parts as you wish - using existing or new Classes. If you only want to assign a single part family, no problem. You can input any prefix you'd like and then automatically assign all parts to Classes, each Class having that prefix. The default "suffixes" are hard-coded. Again, you can change the names as you wish.
  18. Really? How so? Then, simply have the path follow the wall. That's how the EAPs work in all of our tools...
  19. Sounds a lot more difficult than it needs to be. Why not simply edit the Profile so that the Profile Insertion Point is on the face hanging on the wall?
  20. 2 instances in which the parts Classes are valuable: 1) For all of the "Landru-sourced" tools, by-Class attributes can be used to assign textures to the different parts - staging legs...drapery...speaker finishes, etc. 2) When assigned to embedded Classes, part visibilities can be controlled. For example, a user might want to see text labels or notes in one view/plate but not another. Just food-for-thought...
  21. Likely, the dimension data in the "__ATS-BumpModData" record attached to the Symbol you're trying to import is either in the incorrect format (must be a text field) and/or does not include units markers (like "mm"). Correcting one or both of those should get you going.
  22. I am trying to get my head around the "Truss Object" workflow as compared to the "truss Symbol" workflow - specifically, in terms of editing truss Systems/assemblies. In the attached file is a truss System/assembly created using the Truss Insertion tool and "Truss Object"-enabled Symbols. What is workflow YOU would follow (VW-ascribed or not) to...: 1) Swap out the 4 silver 10' sections for 4 black sections? 2) Swap out the right-end 10' section for an 8'? 3) Swap out the 4, 10's for 8, 5's? I've included other truss Symbols (enabled to work w. the Truss tool) for your convenience. Really simple under the "Symbol" workflow: Select a Symbol instance and, after clicking "Replace" in either the right-click menu or in the OIP, select the new Symbol - and then, if necessary, add needed sections. I'm not seeing the same simplicity w. the "Truss Object" workflow and would welcome any counsel. 2020_Truss_Tinkering.vwx
  23. Multiple answers: 1) Other than meeting the 4 criteria I posted, yes, that dialog is the only way to assign curtain/drapery color if using the "Opaque" setting. With that setting, the tool generates the fabric Texture and manipulates the color of the underlying geometry - which is used by the Texture. 2) You CAN...if you really want to...change the color by changing the settings of the Texture definition. Just don't change the name. If you do that, the tool will simply re-create and apply the stock Texture. 3) You can also change the color by choosing the "Custom" option and choosing a specific Texture that carries with it specific color (like the Rose Brand fabrics do). As to your last question, to my knowledge, the related calls in the language in which the softgoods tools are written do not allow for "By-Class" color. You raise good questions and I am investigating options. (BTW, I am not a VW engineer or employee. I am simply the developer of several of the Spotlight tools, including Soft Goods.)
×
×
  • Create New...