Jump to content

C. Andrew Dunning

  • Posts

  • Joined

Everything posted by C. Andrew Dunning

  1. No issues, here. I opened the file, selected the Speaker Array instance, clicked the "Configure Array..." button, switched to the last pane and changed speaker angles, and clicked "OK." The array re-built itself just-fine. I did see that the dimension fields in the Record attached to the bumper need units markers but, as your file is in mm (the same unit used by your bumper), you shouldn't have any problems.
  2. Be sure to include units markers ("mm") in the dimension fields of this record. Otherwise, if this Symbol is ever used in a file with anything other than mm as it main linear dimension, you'll have placement and spacing issues.
  3. When in "Catalog" mode (or, "Library" in the Landru Design version), "Import" will import the data from the Symbol but will build the simplified model on-the-fly. When in "Symbol" mode, the tools will use the actual Symbol geometry. If your given Symbol has the same name as a Catalog/Library entry, you can switch back-and-forth, essentially giving you an "intricate" and "simple" mode.
  4. FINALLY have a minute to work on The List. Just added this...
  5. No problem. CurveTest.vwx FWIW, the problem I'm seeing w. the Landru Design version is new to 2022. The problem: Image is flipped horizontally and starts from the wrong end of the curve. Open this file in 2021...
  6. Here is a file containing instances of the Spotlight PIO and the Landru Design version. While the faceting issue is gone w. the Landru Design version, clearly, I need to delve back into this tool a bit... 18x132 Curved Screen.vwx
  7. Editing my response... I see the issue in every rendering mode w. the Spotlight version of the tool. I then inserted an instance (w. matching settings) of the Landru Design version. Zero issues. Likely something that got tweaked along the way that has not made it into the Spotlight version, yet.
  8. You'll need to create a Symbol for the television you're wanting to show. Toward the end of the manual found here: https://www.landrudesign.com/VWPlugIns.htm are instructions as to how to do this. We also have a movie showing this here: The movie is pretty old and the tool has undergone a little evolution but the core ideas are the same.
  9. Different Symbol = different color and texture applied to 3D portion....and, embedded text label noting color w/o needing to make record changes.
  10. If you don't mind poking around Vectorscript a little you might find the Worksheet and Script in the attached file to be helpful. While the dimensions get reformatted to the closest .XX", that would be easy enough to adjust. SG_Count.vwx
  11. ...and...if the Symbol name and Catalog/Library name are the same the tools will automatically grab the right "other" when you switch modes.
  12. You're running in Symbol mode, correct? If so, something that might help is to switch to Library/Catalog mode when initially building and placing arrays. Then, switch to Symbol mode for final drawings. That will at least help you to work quicker until you need more detailed models. Another option that may or may not be acceptable is to use less detailed Symbols.
  13. I'd argue that there is a good bit (at a certain level) of similarity. For both, the Hybrid system is good for simple hangs (think horizontal truss with bottom-hung fixtures). Things break down quickly when steering away from that - which is why things like raking Design Layer ViewPorts and Schematic Views have been pursued. Designers in both disciplines need to communicate details clearly - especially, when "non-conventional" approaches are desired. Judging from threads over the years (including this one), we're still in search of a good solution...
  14. Sorry for the delay in replying. Lots of juggling these days... Interesting food-for-thought. To answer your first question, I'll draw a parallel w. Light Plots. There is a big difference between 2D icons shown on plots and 3D models. The latter would make for illegible plots. While, perhaps, not to the same extent, I'd offer similar thinking w. projectors, screens, and other video elements. As to your 2nd question, definitely something worth giving consideration.
  15. Following up... It would appear that the issues I was having were because Vision does not include a Forte model, yet. So...not sure what mapping Vision was using. The remedy proved to be importing a GDTF model. Still sorting that out but much better...
  16. The Mode 1 Vision DMX mapping for the Robe Forte is incorrect. I have double-checked the console library with the manufacturer spec.
  17. This definitely could be changed but might be a bit. Short-term, your best bet will be to "break" instances and add the additional railings manually.
  18. Not really a bug but a simple-enough feature request/tweak. ...and...already implemented in the Landru Design versions of the tools... Thanks!
  19. Thanks. A huge part of the problem, here, is that making truss swaps and rearranging configurations are frequently part of the every-day "low-level" design process. Things like this should be incredibly simple and intuitive - so much so that, in a sense, users don't even think about it as they're doing it. As things stand, the current approach gets in the way of the process...
  20. Respectfully, I beg to differ. This whole process is light years from being intuitive. It also doesn't "understand" things like an easy swap from 4 x 10' to 5 x 8'. While, yes, a bit of adjusting after-the-fact was necessary, simple truss Symbols are profoundly more straight-forward to use day-to-day.
  21. With you, there. One of the more infuriating aspects of the Braceworks system...
  • Create New...