klinzey

Make sure you are both using SP3. Do either of you have a customized OIP or custom fields added to the OIP? If so try exchanging a document using only the default OIP settings.

We want to grab the problem installer logs before you do a re-install. We know a re-install usually fixes the problem but we want to see if we can find out why the first install is failing so we can fix the problem. An installer log form a problem install should give us a lot of information on where the problem is or more importantly where the problem is not. Kevin

It's true. No April's Fools joke. You will see more details released about GDTF in the coming weeks.

When you contact tech support about the issue please provide them the InstallerLog from inside the Vectorworks application folder along with your system configuration. We have not been able to reproduce the issue on our machines an we need to see if something is going wrong with the installation process on specific machines.

We are looking into an issue where newly placed instruments are not immediately exported to LW. Any modification to the lighting device in Vectorworks after the initial insertion, i.e moving, setting the unit number etc., will cause the lighting device to automatically export to LW.

You can try to look for the state kObjectCreated (13), not sure if Vectorscript will get this notification or not. It was added for 2012. The problem is that you you are using the name field of the locus. If you attach a hidden record to the loci then duplication would be less problematic. The other issue is that the locus is a dumb object so it can't react to a change. I would try changing your logic slightly. Store the UUID in a hidden field of the PIO AND name the PIO with the UUID. With a PIO you can Hide and disable the object name so the user can't change it. Attach a record to the the loci with the UUID as a record field. (You can also name the Loci with the UUID+"Loci" to make it easier to find but you can't keep the user form changing it.) When you need to find the loci you can do a quick name search for the UUID+Loci, or do a more complex search for the record and filed value if it fails. When the user duplicates the PIO, the object name will change but your hidden UUID will stay the same. You will know the PIO has been duplicated when the UUID does not match the name. Generate a new UUID and rename the object. The duplicated Loci will still have the record attached with the old UUID but you can find it and update it with the new UUID. (For VS this portion of the workflow will fail with duplicate array because could have multiple loci with the same UUID in the record field but you can check the parent to see what the new UUID should be.)

You can use: FUNCTION DefineCustomObj( pluginName :STRING; prefWhen :INTEGER) : HANDLE; The parameter prefWhen can be one of: kCustomObjectPrefNever = 0 kCustomObjectPrefAlways = 1 kCustomObjectPrefNew = 2 http://developer.vectorworks.net/index.php/VS:DefineCustomObj

The name can be used anywhere in the document., the names are not exclusively used by the hanging position. For hanging positions I would start by looking for the position name used as a symbol name.

Check the textures applied to the object. You can set a texture to not cast shadows.

As pat said it's best to put everything into a single string before using it in the criteria. This should work: Mark := '2001'; qstr := Concat ('''Group-A''', '.', '''Mark''', '=', '''',Mark, ''''); GroupPanelCount := Count (qstr); Message (GroupPanelCount);

Make sure you have downloaded the proper version of dialog builder for your version of Vectorworks. Installing the 2018 version into 2017 will likely cause a crash.

Also be sure to consult this article from Lightwright. LIGHTWRIGHT 6 ADDRESSES AND VECTORWORKS

You can connect loads to a single hoist. Unfortunately, this is a little bit tricky with the Vectorworks Hoist. You have to place the load at the hook of the hoist, and then Braceworks will calculate the single hoist. We are working to update the snapping to better support this connection. Also, be sure you are using SP2. There were several fixes in SP2 related to connecting items to the hanging position. It's difficult to diagnose the issues from just the screenshots. Would it be possible to post the file here or email it to technical support, tech@vectorworks.net? Please put "Attention Kevin" in the subject line if you email the file. I've also asked the developer, Moritz, to post to this thread if he has any additional information or questions.

This is going to be a question for John McKernon@Lightwright. There appear to be quite a few fields that you can export from LW that are not in the available fields for the data exchange list. Note that setting the Vectorworks fixture mode to the Lightwright profile will not allow Vectorworks to properly recognize the fixture properly so the Gobo and color wheel information in Vectorworks will be incorrect. I recommend using a custom user filed in Vectorworks to store the LW profile setting.

Make sure you have the latest version of the MA plug-in. There were issues with the plug-in on Windows, Mac was OK, and MA was working on updating.