Jump to content


Vectorworks, Inc Employee
  • Posts

  • Joined

  • Last visited

Posts posted by klinzey

  1. The Stage Deck object does not allow control over the individual leg lengths.

    If you need a stage deck with varying leg lengths I would recommend either using the Stage Deck object with no legs and manually adding the varying height legs  or duplicating and editing a stage deck symbol form the Objects - Ent Stage folder.

    • Like 1
  2. @Safak Sari Give ETC EOS/Nomad a try. https://www.etcconnect.com/Products/Consoles/Eos-Family/

    It's probably one of the easier more powerful ones to learn and they have some great tutorials.

    In the Visualization mode you can connect to Vision with sACN or ArtNET but it will randomly take the intensity of all lights to 0 to prevent you from using it on a real show.


    If you want something very simple you can use QLC+ https://www.qlcplus.org/

    It's simple but can be a little buggy at times and doesn't have a lot of moving light profiles built-in.


  3. @virk You will probably get better information by posting in one of the Customization forums.

    Depending on your knowledge of coding you can decide if the Python Scripting, SDK(c++), or the Vectorscript(Pascal) is the best place to post your question.

    If you are not familiar with any of these programming languages you might want to start by trying Marionette.

  4. You should check with your local distributor for the exact restrictions as they may vary slightly.

    In general, licenses expire after 1 year, the file and the resources in the file are watermarked, PDF exported from Vectorworks are watermarked and protected so they can not be edited, printing will contain the watermark, and you are limited to only a few prior versions of Vectorworks.

  5. Also, remember Vectorworks does have white balance setting. View>Set Lighting Options...

    By default Vectorworks is white balanced at Indoor (3400K), I think Vision is set for something closer to 5500K.


    By default, the 3200K light will look "whiter" leaning toward blue in Vectorworks than it does in Vision but if you adjust the white balance in Vectorowks to 5500K it will look more amber. If you want to experiment in Vectorworks, Viewports have their own individual White Color Temperature setting and it's rather sticking to see the difference changing the white balance makes.

  6. We did not make the fixture profiles for EOS. Not sure who did.

    I pulled up the profile, it looks like an old profile because there is not "Dead" space at the bottom or middle of the range.

    The ETC profile lists only 3 ranges from 0-31794 (0 to -270), 31795-64886 (0 to 270)  and 64886-65535 (Off)

    (Zoom looks right but all the other ones look incorrect.)


    There should be 5 ranges:


    0289h-7C32h (0 to -270)


    83CDh-FD78h (0 to 270)


    If you edit the profile you should be able to use the relative camera.

    (You should be able to copy the range values from the zoom parameter.)


    EOS is limited to a 16bit parameter. It's more work but to get the control you need you can just use 3-8bit parameters or 1-8bit and 1-16bit. This will give you full control. Depending on the size of your scene and the level of control you need may determine if the 16bit parameters need the be the MSB or the LSB.

  7. Try this:


    Procedure ASDF;
    vwMode : LongInt;
    ModeCheck : Boolean;
    FUNCTION BitCheck(largeNum, smallNum :LONGINT) :BOOLEAN;
    {Returns true if smallNum is a power of 2 present in largeNum.}
    bit :INTEGER;
    BitCheck := FALSE;
    bit := 15;
    while bit > -1 do BEGIN
    if largeNum >= (2 ^ bit) then BEGIN
    largeNum := largeNum - (2 ^ bit);
    IF (2 ^ bit) = smallNum THEN BEGIN
    BitCheck := TRUE;
    bit := 0;
    bit := bit - 1;
    vwMode := GetCurrentMode;
    {vwMode := 456;}
    ModeCheck := (BitCheck(vwMode, 4)) | (BitCheck(vwMode, 8));
    {ModeCheck := (BitCheck(vwMode,1));}


  8. The symbols must be in the active document in order for VS to get any info about them other than than the name, so you will have to import them into the document in order to get any record information form the symbol. You should also look at using BeginContext() and EndContext() rather than just deleting the objects, it works better with the undo system and project sharing.

  9. We no longer require lighting devices to be named and the field is now editable by the user. We used to use the name for tracking and detecting duplicated lighting devices but that is no longer necessary.

    The name shown in the Visualization palette is the name of the internal light object inside of the lighting device. It must be unique and is automatically assigned by the lighting device as Channel Purpose Instrument Type #.NNA-#. The user can edit the name if desired but each light must be assigned a unique name.

    • Like 2
  10. Check your Spotlight Preferences.

    IN the Lighting Device: Parameters pane check the value of Default Insertion Angle. The default for new documents is 0 and your setting may be different.

  11. The UniversalName required by the function is the Universal Parameter name field, in this case "Symbol Name".

    We use the same filed names as the lighting device for accessories and cells.

    SymbolName  := LDevice_GetParamStr(handle, cellIndex, accessoryIndex, 'Symbol Name')

  12. @e26Design_marc j Can you post your file? I tried a simplified example with only a few lights and I could not reproduce the issue in SP3.

    It's likely that the lights on the ladder were not properly associated with the ladder and when it was moved the lights found the truss and were automatically associated with the truss.

    You can control this in the Spotlight Preferences. In your situation you may want to turn off the option "Enable auto positioning when moved" and/or make the pick radius smaller.

  • Create New...