Jump to content

klinzey

Vectorworks, Inc Employee
  • Posts

    2,545
  • Joined

  • Last visited

Posts posted by klinzey

  1. 1 hour ago, Benjamin Lishner said:

    the lab computers wipe everything between logins

    The last used workspace is stored as a user setting. If the user accounts are being wiped this will remove the setting and Vectorworks will select the Designer(?) workspace by default because it needs to load a workspace.

    Typically when a new user account is created, it created from a default user account setup by the admin.

    This default account need to use the Spotlight workspace. The workspace may have been accidentally switched when someone was logged in as admin or the default user.

    Your sys admin probably had to do a similar thing with the serial number so users did not need to enter the serial number and registration information each time the application was launched.
    Vectorworks support should be able to give you exact details on where and what needs to be changed but you will need to be an administrator on the machine to make the changes with your setup.

    • Like 1
  2. Vectorworks 2021 is different. The debug menu commands and the dialog builder are now installed via the Help>Install Partner Products... menu.

    Once the dialog opens select Vectorworks Developer on the left and you will see 2 items on the right, Dialog Builder and Debug Menu.

    Select one and it will be installed and added to your current workspace.

  3. It looks like the latest Vision Windows installer is adding some additional unnecessary files to the DmxProviders folder. We will work on getting the problem corrected but till then.

     

    Navigate to the DmxProviders folder in the install directory, typically C:\Program Files\Vision 2021\DmxProviders.

     

    DELETE

    • Artnet.exp
    • Aetnet.lib
    • Multiinput.exp
    • Multiinput.lib
    • sACN.exp
    • sACN.lib

     

    The DmxProviders should ONLY contain

    • 32
    • app_updater
    • Artnet.dll
    • grandMA.dll
    • Hog3.dll
    • HogPC.dll
    • Multiinput.dll
    • sACN.dll
    • Like 1
  4. It looks like the latest Vision Windows installer is adding some additional unnecessary files to the DmxProviders folder. We will work on getting the problem corrected but till then.

     

    Navigate to the DmxProviders folder in the install directory, typically C:\Program Files\Vision 2021\DmxProviders.

     

    DELETE

    • Artnet.exp
    • Aetnet.lib
    • Multiinput.exp
    • Multiinput.lib
    • sACN.exp
    • sACN.lib

     

    The DmxProviders should ONLY contain

    • 32
    • app_updater
    • Artnet.dll
    • grandMA.dll
    • Hog3.dll
    • HogPC.dll
    • Multiinput.dll
    • sACN.dll
  5. Check the values we have in our symbols. We assume a certain lamp type when we create the symbol and use the data that is available when we created the fixture. I know that some specifications have changed over the years and manufacturers have correct/updated their specification.

    We have verified that that calculations we report are correct based on the methods in  Robert C. Mumm's Photometrics Handbook 2nd Edition.

    The manufacturer's report probably uses actually measurements so they will always be more accurate.

    • Like 1
  6. Make sure the data you are supplying the Vectorworks symbol is in candle power or peak candella, not Lux, Lumen or some other value. (It does NOT use the value from the VW light emitter.)

    With that said Vectorworks uses a very simple cosine squared falloff calculation based on the distance from the source.

    It does not take into account dimmer value, color, shadows, reflections or any other objects in the drawing.

    • Like 1
  7. Fixture ID was removed from the OIP because it was being used incorrectly and sending incorrect data to Vision and other applications. Users assumed that the Fixture ID in Vectorworks operated the same as the FID in the grandMA console.

    The Vectorworks Fixture ID allowed users to filter the Fixture Mode popup. We have added search capability to the Fixture Mode popup so the Fixture ID filed is no longer necessary.

    You should be using the Vectorworks Channel as the FID or FixtureID.

    Visualizer data mapping

    • Like 1
  8. We released Vision 2021 SP2.1 today.

    The primary focus with this service pack was to add support for MA-Net3 and the grandMA3 viz-key.

    The connection requires the latest version of the grandMA3 or the onPC software and some additional steps to setup and configure.

    For additional information about connecting grandMA3 with Vision 2021 SP2.1 click HERE

    If you encounter any problems connecting Vision with the grandMA3 or grandMA3 onPC using the viz-key please let us know.

     

    The grandMA3 viz-key is available from your local MA distributor.

     

    This service pack also includes multiple improvements and fixes in the following areas:

    • The Disguise and Absolute DMX Cameras DMX patch will be maintained and will automatically disabled when a document is opened to allow proper navigation.
    • GDTF fixtures that use default geometry will not display properly in Vision.
    • Vision fixtures with customized gobo and color data are stored and recalled properly form the V3S file.
    • Issues editing with multiple selected objects have been fixed.

     

    This Service Pack is available for all licenses as a downloadable updater. To install the Service Pack, please select "Check for Updates" from the Vision menu (Mac) or Help menu (Windows).

  9. We have seen the same problem before on the ETC offline software.

    We are not quite sure why it happens but it appears that some software sees there is not valid network address and then doesn't broadcast the data over the network or it's internal communication protocol requires multiple valid IP addresses.

    The easiest solution we have found is to connect it to a router that will give it an IP address. It doesn't need to be connected to the intranet, just a router or other device that will be able to distribute IP addresses.

    Vision listens to all interfaces for for data, so if it's being broadcast Vision should see it.

  10. @Sam Jones "Load Trim" is the localized name, the call should be

     ok := GetLocalizedPluginParameter('BrxHoist', 'LoadTrim', localName2);

     

    You can get the parameter values or record information form SDK objects the same way you get them form VS objects.

    Easiest way to see the parameters is using Debug List View or you can see the parameters if you make a worksheet that looks at the hoist.

     

    If you want to do it in code you would.

    NumFields (BrxHoist Record)

    For I := 1 to numfileds

           FieldName = GetField(BrxHoist Record,I)

           GetLocalizedPluginParameter('BrxHoist', 'FieldName', localName);

×
×
  • Create New...