Jump to content

C. Andrew Dunning

Member
  • Posts

    1,158
  • Joined

Posts posted by C. Andrew Dunning

  1. Jake -

    Sorry you're having issues...

    Some questions in order to help you:

    What VW version are you running?

    Have you recently upgraded or reinstalled VW?

    Might you have copied the projector resource file from another computer that might be running a different VW version?

    Did Video Screen projector placement ever work on your current computer?

    Do the other video tools that import Symbols (Television, Blended Screen/Projector) work?

    Does the "Stand" function in Video Screen work?

  2. Greetings from Landru Design!

    To celebrate our easing into December, we've released updates for several of our Vectorworks tools:

    1) Staging ToolSet 2 (now 2.1)

    [img:center]http://www.landrudesign.com/STS21Xmpl.jpg[/img]

    Though there are several tweaks, the most noticable changes include:

    - The addition of the new StageRamp 2 tool. Using this tool, "stage-style" ramps can be created based on stage height and ramp floor length, actual ramp length, ramp angle, ramp rise:run ratio, or ramp grade. This tool features adjustability, texturing, and text display similar to the other Staging ToolSet 2 tools.

    - Several rail improvements to StageDeck 2 and StageSteps 2 (which are also featured in StageRamp 2), including a lot of general refinement, rails for round StageDeck 2 objects, and the ability to add additional horizontal and vertical elements.

    2) SoftGoods 2 (now 2.094)

    In addtion to a bit of general refinement, the most noticable change is that we've replaced Class "Sets" with much more flexible user-definable Class prefixes.

    3) Audio ToolSet 2 (now 2.503)

    We've addressed some minor bugs.

    As in the past, these updates are available free-of-charge to licensed users of each of the tools (including Producer's Pack). Users can simply use the links and passwords they were sent for initial download(s).

    If you'd like more information, please visit our Vectorworks Plug-ins page.

    Happy Vectorworking!

  3. Martin -

    I am looking to add a DL3 to a plot, assign it a custom image, and then have that image displayed on a flat surface (not a screen) on my set.

    I think Kevin and Josh are right: You're going to end up either projecting your images as gobos (treating DL3s as Spotlight lighting devices) or using pre-vis software. VS4/Video Screen would be great for making sure you're staying within the capabilities of the DL3, but you'd be restricted to rectangular or round surfaces (screens w/o borders and/or frames).

    Can you make a DL3 use VS4 tools?? Or add a DL3 type option to the list of Projectors? How sweet would that be!!

    Again echoing Kevin, absolutely. You can easily add a DL3 to your stock projector library. We've got a few users who have done that. See pages 27-28 in the VS4 manual.

    Add the ability to set a horizontal rotation in the OIP so I can "tilt" my screens and we'd be rockin'

    By this, I'm assuming you're meaning that you're wanting to "spin" the screens (somewhere in-between landscape and portrait), correct? If so, that has been suggested/requested before, but we haven't quite gotten there, yet.

    If you're actually meaning "tilt," as-in tilting the top of the screen toward or away from the projector(s), that feature is there. Look for the "Screen Tilt" parameter, about 1/4 of the way down from the top of the OIP.

  4. We're pleased to announce a few updates from Landru Design:

    1) Vectorworks 2013

    All of our tools are fully compatible with Vectorworks 2013. Current license holders can download updated versions free-of-charge.

    2) Staging ToolSet 2

    Staging2Xmpl.jpg

    We have released new versions of our tools that are used to create models of stage/riser deck sections and stage-style step units. Significant improvements over the previous version include:

    - A new "3D Options" dialog, allowing easy selection of textures for the different 3D parts.

    - Reformatted deck/step top and trim, allowing more realistic transparent or grated objects to be created.

    - Expanded text display and manipulation.

    3) Audio ToolSet 2

    We've released version 2.5, boasting a lot of general refinement and a few bug fixes. Current license holders can download the updated version free-of-charge.

    4) Producer's Pack 2

    This is an updated and expanded version of our "kitchen sink" collection, now itegrating all 12 of our tools, including both Staging ToolSet 2 and Audio ToolSet 2.

    For more in-depth information on any of these tools, visit our

    Vectorworks Plug-Ins page.

  5. Preston -

    "Open From" will only be enabled if a) your object has a "Curtain" function (not "Border" or "Pipe-and-Drape") and b) it is a straight 2-vertex (1 at either end + handle at center) object or an arc 3-vertex (1 at either end and middle + 1 at crc center) object. Any time you start adding vertices or swerving from those vertext types, the "Open From" option gets disabled.

    Make sense?

  6. I find it odd that VW has a good layer and class system that you essentially have to stop using in any sensible manor to make vertical truss.

    Actually, I'd offer that VW has a good Layer and Class system that, used in a little different manner, makes this process somewhat more managable.

    Think about how an architect might set up a drawing: Classes for each discipline/trade (plumbing, electrical, floor coverings, doors, etc.) and Layers for each floor/level in a building. Used that way, Classes are for WHAT something does. Layers are for WHERE something is.

    Apply that to entertainment/production: The WHAT becomes lighting, sound, video, scenic, etc. The WHERE becomes performance spaces or, in the case of the example I posted, project sub-assemblies. I know that this is a bit different than the way most entertainment users work, but I've found this way of, in a way "mirroring" the architectural world, to be a great way to work. Approaching things this way, the VW Class/Layer system is quite useable and makes a world of sense to me.

    So, for the way I work, I don't have to stop using the system; I simply expand my usual approach a little.

  7. Lec and Simon -

    Here's what I've done to create models of non-horizontal trusses:

    1) Create a Design Layer for each of the truss assemblies.

    2) For each of the assemblies, construct things in plan view (as a shop person would want things presented) - with each assembly on its own Design Layer.

    3) Create a "Main Model" Design Layer.

    4) Create Design Layer ViewPorts of each of your assemblies on the "Main Model" Design Layer. You'll be able to move them around and to tilt/rotate them as you like.

    This might sound a little convoluted, but you'll end up with a single drawing file that functions as both a presentable 3D model AND understandable plots.

    Make any sense??

  8. Vincent -

    You may or may not know that this tool exists in 2 formats: Spotlight 2012's "Soft Goods" and Landru Design's "SoftGoods 2." In terms of features and functionality, the tools are (for now) identical. If you're wanting to use a PIO to create your P&D objects and you stick w. the Spotlight version, you'll have to wait for either the next Service Pack or the next Vectorworks version release. Or, for $20 you can buy a licence for the Landru Design version (see http://www.landrudesign.com/VWPlugIns.htm for more info). As with our other tools that have been incorporated into Spotlight, by owning a license to our version, you gain features that may or may not eventually make it into Spotlight and, potentially, faster turn-around on fixes.

    That help, at all?

  9. Vincent -

    Are you using the Spotlight "Soft Goods" tool or the Landru Design "SoftGoods 2" tool?

    Would you mind posting a file containing the Soft Goods obejct that is giving you trouble? I created a Soft Goods P&D object with the Image option here in a fresh file and am not seeing any issues. Being able to see all of your other settings for the PIO would be quite helpful.

  10. I don't know that I'll be a lot of help, but I've been using both calls a fair amount.

    This works just fine in both Metric and Imperial drawings:

    NewObj:= OffsetPoly(OldObj,.0625",1,False,True,512,.03125"); (I'm trying to preserve curves best as possible.)

    I've not seen the deselction issue w. OffsetPolyN (yet).

    The frustrations I have had include:

    - The 2 calls seem to "polygonize" reference polylines differently. The former seems to create an offset polygon automatically but I've had much better results using "ConvertToPolygon" before using that call. The latter seems to preserve the "polylineness" but seems to give "ClipSurface" issues, even when the offset is closed.

    - I've learned to test for object type when using "OffsetPoly." Even when single polygons are created, they're sometimes contained in groups - especially, if I've done a negative offset.

    My 2?...

  11. Suppose that Landru or Dworks have a need. So they create the answer and then go about their business more efficiently with less frustration. Would it not be beneficial to then offer the item (developed out of personal need) for sale in such a marketplace? Why not?

    There are actually 2 different questions here:

    1) Would a "proprietary" developer offer a "need-met" tool commercially in-general (and, why or why not)?

    I can't speak for Dieter, but this is precicisely how the Landru Design tools came to be.

    As to the "why not" for those who've chosen not to offer their tools commercially, I don't know. I've asked a few folks but haven't gotten incredibly clear answers. I suspect that it has primarily to do w. either the "hassle factor" or, perhaps, a feeling of not being "ready for prime time."

    2) Same question, but related to a VW/NVW-specific marketplace...

    As such a beast doesn't exist, this is hard to answer but, as a developer, I'd be asking things like...:

    - What "hassle factor" exists w. this approach?

    - How would distribution work?

    - Who would be setting standards and what would they be?

    - Would there be there any moderation of comments?

    - What licensing fee percentage would be held back?

    - Would there truly be an expansion of my current audience and would that offset potential hassle and expenses?

    Don't at all hear me saying that I think a VW "Marketplace" is a bad thing. From a developer's perspective, it could be an absolutely fantastic thing. I'm simply expressing some of the questions I'd be asking.

  12. And then the poeple that wanted this need to buy it...

    Which determines further development and support of that tool - and, the introduction of further tools from that developer.

    Though there could be several somewhat more intricate variables at-play here, at one level there really are simple "chicken-and-egg" questions: Would more 3rd-Party developers have incentive to create, develop, and support quality VW tools if there were more effective ways to tell users about their wares, if more users actually purchased licenses(!) - and, if it were easier to get their products to users? ...or... Would more users actually purchase 3rd-Party tool licenses if more high-quality tools existed, if users knew about them, if the tools were easier to manage, and if users had more faith in the tools'/developers' longevity? (And, those questions could probably be rearranged in different ways.)

    My "gut" is that it's all of the above.

    The Landru Design tools were initially created because I had a specific need in my day-to-day work. As much as I enjoy the development process and responding to users' wants/needs, the reality is that our tools only exist in their present state because of the support of our users in the form of license sales. Without that, I don't believe I'd have been able to justify the huge time and effort committment the tools have required.

    My 2?...

  13. Chad -

    Thanks for the thoughts. I've added both to the ongoing and ever evolving wishlist. Youre input is MUCH-appreciated. As I've said several times, the "idea investment" of users like you are a huge part of what has made the tools grow/improve over the years. Keep `em coming...

  14. AEChadwick, below is more food-for-thought for you. It is the general/basic structure several of my PIOs follow. Others may have different approaches, but this is what works for me:

    procedure DemoPIO;

    {--------------- Declare Constants and Variables ---------------}

    Const {Constant Setting Section}

    kResetEventID = 3;

    kObjOnInitXProperties = 5;

    kObjXPropHasUIOverride = 8;

    kObjXHasCustomWidgetVisibilities = 12;

    kObjOnWidgetPrep = 41;

    var {Variable Setting Section}

    gPIOName : string;

    gPIOHandle, gPIORecordHandle,gWallHandle : handle;

    gTheEvent,gMsgData : longint;

    Result : Boolean;

    {--------------- Procedure to Do Real Work ---------------}

    Procedure RealWork;

    Begin

    End;

    {--------------- Equivalent of Master Cue List ---------------}

    Begin {main}

    Result := GetCustomObjectInfo(gPIOName, gPIOHandle, gPIORecordHandle, gWallHandle);

    vsoGetEventInfo(gTheEvent, gMsgData);

    CASE gTheEvent OF

    kResetEventID: {Event: 3}

    BEGIN

    RealWork;

    END;

    kObjOnInitXProperties: {Event: 5}

    BEGIN

    Result := SetObjPropVS (kObjXPropHasUIOverride,True);

    Result := SetObjPropVS (kObjXHasCustomWidgetVisibilities,True);

    Result := vsoInsertAllParams;

    END;

    kObjOnWidgetPrep: {Event: 41 - Section to set Parameter visibilities and enablings}

    Begin

    {lines to hide/show/enable/disable parameters and clear/populate pop-ups}

    vsoSetEventResult (-8);

    End;

    END; {Event Case}

    end;{main}

    run(DemoPIO);

×
×
  • Create New...