Jump to content

C. Andrew Dunning

Member
  • Posts

    1,042
  • Joined

Posts posted by C. Andrew Dunning

  1. Steve -

     

    I checked your file.  You have data attached to the one Symbol instance you placed, but, the data needs to be attached to the Symbol definition, instead.  Edit the Symbol and, without anything selected, attach the Record and fill in the data.  Resave the file and you should be good-to-go.

     

  2. Phil (and all) -

     

    Answers to some of the questions posed, here:

     

    1)  Tiling like you're wanting is definitely doable with VS4-Television (and, the Spotlight Television tool).  But...you have to do it "manually" or use a rudimentary command I created for that purpose in my day-to-day work.  While that command is not included as part of the stock Producer's Pack 3 or VideoScreen 4 suites, I do share it upon special-request from license-holders of our tools.  The tool has its limits (same-size panels/surfaces, even spacing, PIO instances facing "down-screen," etc.) but does save a TON of time when tiling screens.

     

    2)  The current releases of all of our tools work in any "flavor" of Vectorworks, 2014 or newer - whether a Spotlight installation or not.

     

    3)  See the links in my sig. for pricing.  You can buy licenses for the individual sets of tools or for the "kitchen-sink" collection, Producer's Pack 3.

     

    I hope this helps you out.

    • Like 2
  3. Here's what might be a better approach:

     

    Procedure LayerClassToggle;

    CONST
     kClass = 'NonPlot-Brick grid';
     kLayer = 'BRICK GRID';

    VAR
     ActLayerName      : STRING;
     ClassLayerVisible   : BOOLEAN;

    BEGIN
     ClassLayerVisible := YNDialog(Concat('Do you want the Class "',kClass,'" and the Layer "',kLayer,'" visible?'));

     ActLayerName := GetLName(ActLayer);
     
     IF ClassLayerVisible THEN
      BEGIN
       Layer(kLayer);
       ShowLayer;
       ShowClass(kClass);
      END
        ELSE
       BEGIN
        Layer(kLayer);
        HideLayer;
        HideClass(kClass);
       END;
     Layer(ActLayerName);
    END;

    RUN(LayerClassToggle);

    • Like 1
  4. Try this:

     

    Procedure LayerClassToggle;

    CONST
     kClass = 'NonPlot-Brick grid';
     kLayer = 'BRICK GRID';
     kON = 0;
     kOff = -1;

    VAR
     LayerVisStatus,ClassVisStatus : INTEGER;
     ActLayerName     : STRING;
     DialogVisState     : BOOLEAN;

    BEGIN
     ActLayerName := GetLName(ActLayer);
     LayerVisStatus := GetLVis(GetLayerByName(kLayer));

     Layer(kLayer);
     IF LayerVisStatus=0 THEN HideLayer ELSE ShowLayer;

     ClassVisStatus := GetCVis(kClass);
     IF ClassVisStatus = 0 THEN HideClass(kClass) ELSE ShowClass(kClass);
     
     Layer(ActLayerName);
     END;

    RUN(LayerClassToggle);

    • Like 2
  5. Try this, instead:

     

    Procedure LayerToggle;
    CONST
    kTestLayer = 'BRICK GRID';
    VAR
      VisStatus : INTEGER;
      ActLayerName : STRING;
     
    BEGIN
    ActLayerName := GetLName(ActLayer);
    VisStatus := GetLVis(GetLayerByName(kTestLayer));

    Layer(kTestLayer);

    IF VisStatus=0 THEN HideLayer ELSE ShowLayer;

    Layer(ActLayerName);
    END;
    RUN(LayerToggle);

    • Like 1
  6. @rseybert...

     

    1)  The answer to your question is "both."  For all of the tools in-question, the core functionality and code are identical but some of our versions of the tools have continued to evolve, offering general refinement and additional features.

     

    2)  The need for a leg tool makes perfect sense and, as your existing system demonstrates, would probably need to be a stand-alone tool as trying to work that into a general staging tool would likely be far too limiting to be useful.  FWIW, developing such a tool would be quite doable.  Ping me off-list and we can talk about what that could look like...

  7. Jumping in...

     

    1)  What you're describing is definitely the sort of thing VW's Plug-In Objects were created to handle.  So...the potential IS there.

     

    2)  You can get staging tools 2 different ways:  the stock Spotlight set or those we offer (see http://www.landrudesign.com/VWPlugIns.htm).

     

    3)  While at-present the tools don't offer the level of leg detail you cite (the operative phrase being "at-present"), we are absolutely open to suggestions and feature requests.  Many of the favorite features in all of the tools are the direct result of user input, as I'd think many, here, would confirm...

     

    That help?

     

  8. Yes, creating custom plate sizes IS possible.  You need to add your desired size(s) to the Pop-up choices list for the “baseSize” parameter (#31 in the Landru Design version of the tool).  You do this through the “Customize…” button in the Plug-in Manager.  1 thing, though:  items you add MUST follow the format of the things already there.  Any deviation from that will not work.

     

    I just tested this in both versions of the tool...

     

    Make sense?

     

    • Like 1
  9. Grant -

     

    Have you tried the latest build of VS4-LED?  While I'll be the first to admit that it may not address every one of your requests, I have tried to tweak things so that the 2 general user "conventions" are addressed:

     

    Camp A:  "Modules" are seen as whole LED panels and a given PIO instance represents a whole wall.

     

    Camp B:  "Modules" are seen as pixel blocks and a given PIO instance represents a single LED panel.

     

  10. Here are a couple of answers to your questions:

     

    1)  The weight estimating feature does not exist in any of the Spotlight versions.  That is brand-new functionality that is unique to the Landru Design version of the tool.

     

    2)  Though addressing this is a high priority, the Landru Design version of the tool does not work with Braceworks, YET.

     

    • Like 1
  11. Happy September 17th!

    We hope you're enjoying exploring the newly-released Vectorworks 2019®!

     

    To answer a question we several people have been asking:  All of the Landru Design tools have been updated and are Vectorworks 2019®-compatible.  In addition, several have gotten a fair amount of "under-the-hood" refinement and some boast noticable changes, the most recent of which include...:

    •  The Audio ToolSet tools now offer expanded data fields and the ability to enter more info "en masse" through the "Config..." dialog.

    •  AudioArray 2 now will now create "Sub Pole" configurations of arrays.

    •  SoftGoods 2 now has a new functionality to estimate curtain weight based on fabric specification (like "22oz Encore).

     

    Also, now that versions of all of our tools have been part of Spotlight® for a while, we get regular inquiries about what the differences are. In additon to the above, here are a few features that are unique to the our versions:

    •  All of the tools work in any "flavor" of Vectorworks® - 2014 or newer - with or without Spotlight®.

    •  The Staging ToolSet tools are all "aware" of Renderworks'® and Spotlight's® stock/default Textures.  One of this suite's tools, StageRamp 2, can now have a vertical bottom face and/or extended legs for doing things like placing ramps that bridge from one StageDeck 2 model to another.

    •  SoftGoods 2 has a toggle to round displayed dimensions, includes a toggle for highlighting (or, not), non-standard pipe-and-drape sliders, and can include trims and weight in displayed text.

    •  AudioArray 2 can create "T"-style bumpers and AudioBox 2 can create Top-mounted yokes.

    •  VS4-Television can tilt TV casings on-the-fly and can create stands with stock or custom heights independent of TV casing height.

    •  The projection tools now have a "Mounted" "Vertical Position" option, letting you specify the trim of a supporting structure and the distance down from that that the projector is to hang (define truss trim and amount of drop from that).  Also, these tools now can work with projector models that use a projection distance reference point other than the lens - like, the projector's front feet (Christie uses front feet and Barco the lens as reference).  Finally, the projection tools have been reworked to allow for UST lenses/projectors.

     

    If you have purchased a license for a given tool in the previous 12 months, these updates are free of charge.  If your license is older than that, we believe that you'll find the upgrade offers to be quite generous - especially for the Producer's Pack 3 suite.

     

    Feel free to visit http://www.landrudesign.com/VWPlugIns.htm for more details, to download manuals, or to check out the upgrade offers.

     

    We continue to be infinitely grateful for our users' loyalty.  It is because of people like them (you) that that the tools are what they are today and that they are serving over 1500 users in 35 countries.

    • Like 2
  12. Ya probably caught me on one of my rants after receiving yet another intricate file in which no Saved Views were used...or, after hearing complaints from yet another user (who didn't use Saved Views) about how hard managing many Classes and Design Layers is.  Thanks for the kind words, though...

     

  13. To apply custom Textures:  In the "3D Options" dialog, choose "Custom Texture" for the appropriate piece.  The Texture chooser pop-up will be enabled.  Pick the Texture you want.

     

    To edit an existing Texture definition:  In the Resource Manager, make sure "All Resources" or "Renderworks Textures" are visible.  Right-click on the one you want to change, and choose "Edit."  Then make changes to the desired shader, in this case, "Color."  When finished, click "OK" and you should see the effects of the changes you made.

     

    • Love 1
  14. What rendering mode are you trying?  Texture color differences will be seen in Final Quality Renderworks and OpenGL.

     

    Take a look 2 the attached file.  I applied custom textures to all of the parts except the top.  For that, I changed the definition of "vsBlkDeckTexture" to be blue instead of black.

     

    That help?

    StageColorDemo.vwx

    • Like 1
×
×
  • Create New...