klinzey

Enttec dmx pro drivers were dropped many years ago. The primary interface for Vision are networks protocols like Art-Net or sACN rather than USB interfaces.

Trial versions can only be activated once. Licensed versions can be activated on 2 machines. You may want to contact your sales representative and inquire about getting a trial for your other machine.

Please contact your local distributor and ask them about the student2pro program. As part of the program when you purchase a professional license we convert your files to the professional version.

"Create Label Legend from Instrument" is the wrong command, you should be using Spotlight > Object Conversion > "Convert to Lighting Device".

That's a list browser not a list box. vs.CreateLB()

Try editing the 2D component of the symbol directly in the resource manager. It looks like a class visibility problem. The preview in the Resource Manager used the class visibility when the symbol was last edited. The preview in the Edit Instrument Data uses the current class visibility. Try turning all the classes on and see what happens.

It looks like it's a problem with the importer in both Vectorworks and L8. I did a quick test and the geometry for the TV is being exported as a symbol in the MVR. The import into Vectorworks creates the symbol but it is not placed in the document. I'm not sure how L8 handles nested symbols. We will investigate the issue in Vectorworks.

Typically you will use Swap Panes to show different sets of controls depending on the options that are chosen in the dialog. This will give let you place different controls in the same location. https://developer.vectorworks.net/index.php/VS:CreateSwapPane

I'd need to see the file to be sure but from the screenshot to top one "Edit Accessory" is set to" #1 -Light ..." so you are probably editing the accessory in the top screen shot. In the bottom screen shot "Edit Accessory" is set to "<None> so you are editing the main light. For the lights you are having issues with make sure the "Edit Accessory" is set to "<None>".

Send to Vision always expects the same year version of Vision and Vectorworks. If you have different versions you need to use Export ESC... or Export MVR... and then open the exported files in Vision. You also need a licensed version of Vision to use any functionality other than the supplied demo files. The demo version of Vision only allows you to use the set of demo files that are shipped with Vision, all other capabilities of Vision are disabled in demo mode.

Vectorworks 2022 added Truss Magnets to more accurately and reliably connect truss. You can convert your existing library by running the Tools>Utilities>Update Truss Magnets. This will convert the old record data to the new truss magnets. This will work for most trusses, there may be some where you have to edit the symbol and manually adjust the magnets in order to get them to connect accurately.

You can try manually deleting your plug-in and then deleting your Vectorworks user folder. Please reach out to tech support directly if you need help doing either of these things.

@jbelsky I looked at your file and it appears that you have customized the OIP of the lighting device and removed several important controls that allow you to access the data of the accessories. You should revert to the default <Spotlight> parameter set in the Spotlight Preferences or customize your existing parameter set to include the "Edit Cell" and "Edit Accessory" parameter. Using these 2 pop-up will allow you to edit the data for cells and accessories of the selected lighting device including the assigned label legend. In your case once you add these fields set "Edit Accessory" to "All" and then set "Label Legend" to "None" to remove the label legend for all accessories attached to the selected lighting device.

Please make sure you are updated to Vectorworks 2021 SP5. There were export issues fixed with SP5.

Sort of, the locus would need to be in a symbol but you really should have some geometry. Remember the Label Legend works by using the bounding box of the symbol. Labels placed within the bounding box of the symbol use the insertion point of the symbol as the reference point, labels placed outside of the bounding box use the bounding box as a reference. This is what allows the label legend to automatically scale to any symbol, if there is no geometry then we don't know which labels you in front of the light, behind the light etc. So in all likelihood a label placed at the insertion point would be the only label that could be inside of the light all other labels would be placed somewhere outside of the light.

@mdrohn I'm not sure how this ever worked. The label legend was always designed to always contain a reference symbol. Unchecking the "Use layout symbol" should generate a default layout symbol not remove the symbol entirely. We will have someone investigate the issue.

You either have the layer with your pipes stacked above your lights and you need to change the stacking order of your layers to correct the problem. or You changed the stacking order in which you spend to select the pipes and send them to the back.

There is nothing preventing you from attaching another record to the lighting device symbols. This would allow the user to see the see the information and search the Resource Browser without the need to modify the light info record or add add additional fields to the OIP.

Please send an email directly to StudentServices@Vectorworks.net to request an earlier version if you have already downloaded Vectorworks 2022. Vectors 2021 is only available in the student portal if you haven't already requested Vectorworks 2022. The Augment 3D plugin for for Vectorworks is created, distributed and maintained by ETC, so you will need to wait for ETC to update it before you can use it in Vectorworks 2022.

It all depends on the protocol you are using. Enttec Open DMX Ethernet Mk2 should work since it takes Art-Net 1/2/3, Streaming ACN sACN as an input and Vision can read that. If you are using some other proprietary protocol Vision won't be able to read the data. We dropped support for the USB devices a while ago once Art-Net and sACN took over as standards.

@DBLD Try removing the scaling and see if that makes the windows behave better.

@Richard1 Can you post or DM me your sample file? We should be able to use the UUID to determine which objects in Vectorworks are exporting as empty 3DS files.

Vectorworks supports 2 types of accessories. Static Accessories and Accessories. Static Accessories are things like top hats and barn doors and are seen by Lightwright as Accessories. Vectorworks Accessories are things like color scrollers and are seen by Lightwright as Devices and will be shown as a separate entry (line) in Lightwright. It's important to use them appropriately in order to get the data to move between Vectorworks and Lightwright. If you set a scroller to a Static Accessory in Vectorworks, Lightwright will not be able to assign it a DMX address. If you set a top hat up as an Accessory in Vectorworks, Lightwright will see it as a separate device and it will not show up the Accessory list for the light. Lightwright doesn't support any data for Static Accessories, they just become a list in the accessory field in Lightwright. If the data is not necessary you can leave the fields empty in Vectorworks. Vectorworks uses internal data to know which accessories are attached to which light, Lightwright uses the position name and unit number of determine the association. So both applications have to make some assumptions in order to link an accessory with a light when we are exchanging data.

It's not easy but it is doable. You would need to place a texture of the tree leave on a 3D polygon in front of the light and then align it with the light. The easiest way to do this is to put the light and the 3D Polygon/texture inside of a symbol then place the symbol in the document and rotate it as necessary.

Yes it should work fine with any student version. Make sure if you are converting the file from an older version you save the file after it gets converted. The file must exist on the disk in order for the data exchange to work.