klinzey

Try BuildResourceListN2() I think it accepts a fully qualified path to a file. The BuildResourceList calls are really designed to use folders so the users can add a file to a folder and the developer can update the original file without overwriting user created content.

The class Rigging-Truss-Truss is turned off in the Viewport. Once that's turned on you should see the truss.

It's likely that there is a label legend applied to the light and the accessory. Select the accessory in the OIP and change the label legend to None.

It looks like you have end markers turned on for your lines. You should be able to select the object and in the attributes palette turn off the end markers. If that does not work then change the document default line marker. Deselect everything and use the attribute palette to select no end marker for the lines. Once you do that change a value on the soft goods object and the arrows should go away. What version are you using?

What were the settings for the Universe parameter?

You can use GetTickCount() at points in the script to get a sense of time. It's 1/60 of a second. If you get the count at the start of the script then you can calculate the run time to any point in the script by calling GetTickCount again.

Try just incrementing by the DMX footprint, not the footprint +28

It sounds like someone has customized the OIP. The control should always be there just disabled when the proper conditions do not exist. Since the option is not shown at all go into Spotlight Preferences, on the Lighting Device: Parameters tab, in the Settings Popup select <Spotlight> then click OK. The parameter should then show.

The containers are shown in the Label Legend for reference only. You need to edit the container symbol itself in order to change the size of the container.

You likely have a Label Legend applied to the Light and the Accessory. With the Lighting Device selected, in the OIP, select the Accessory from the Edit Accessory drop down. Then select <None> in the Use Legend drop down.

No. Vision does not support export to MVR.

Can you post one of your files?

This is actually a feature of this tool that has existed since it was created to support older workflows and multi-circuit instruments. Multi-circuit fixtures consist of multiple symbols. The instrument summary counts all symbols with the same Instrument Type and Model name as the same. In the instrument summary this allows the user to say that it takes 3 symbols of this type to make one 3 cell light so it will not report each cell of the light. It also supports a workflow that is uses by some users that do not want to use the 3D rotation feature of the lighting device. They create multiple symbols, i.e one floor mounted and one hung. This creates 2 different symbols but the user can set the Instrument Type and Model name the same so both symbols count as the same fixture.

It's been a while since I have used a radio button in the OIP. the more standard method is a dropdown but I think it works the same way. You should just be able to use btn or pTipo rather than GetCustomObjectChoice() to return the chosen string. It's better to use the value than get the index of the item in case you ever reorder the list or add a new item. If you need the index then use GetPluginChoiceIndex('Container_00', 'Tipo',pTipo,ixd)

The exported MVR contains the class information. Most other applications do not support both a layer and class so they delete the class information. Objects reference the UUID of the class and then the class name is defined by the UUID separately. We determined that layers were a more universal concept and fit the structural organization of the MVR better than classes. <Layer name="Design Layer-1" uuid="DEB28A2B-E074-4F4D-AB1C-CBA179B2F2CA"> <ChildList> <SceneObject name="Geometry" uuid="1BCAFB2D-971C-403F-8A5B-7D68C6881D0F"> <Matrix>{1.000000,0.000000,0.000000}{0.000000,1.000000,0.000000}{0.000000,0.000000,1.000000}{4630.485185,-4165.600000,0.000000}</Matrix> <Geometries> <Symbol symdef="EE8FF232-C0CF-4A61-9C75-E699FC334E0F" uuid="00000000-0000-0000-0000-000000000000"> </Symbol> </Geometries> <Classing>7A6EC634-F65F-42BE-A1C6-79C878BA4C92</Classing> .... <Class name="None" uuid="7A6EC634-F65F-42BE-A1C6-79C878BA4C92"/>

There are multiple types of UUIDs in use. There is one UUID that is used in the MVR to link an object in the drawing to an entry in the MVR and is unique to the file. There is another UUID in the GDTF that uniquely identifies the GDTF file. I think what you really want is the UUID from the GDTF not the UUID from the MVR. Associating the UUID from the GDTF to a symbol in Vectorworks is on wish list.

The other thing to remember is that in Vectorscript a lot of the unit information form the OIP is handled automatically so you don't always need to deal with units. In the script if you are dealing with a dimension value you get into issues when adding. If you say y + 1, it will add 1 document unit to y, That could be 1", 1', 1m, 1mm depending on your document units. If you want to add 1 foot then be sure to include the unit mark y + 1' It's a lot easier than doing a lot of UPI conversions.

What is the "long fixture id"? In Vectorworks you can associate a lighting device with any GDTF file. In order to use a MVR for data exchange a lighting device must have a GDTF associated with the device in MVR.

From the Edit Accessory drop down select the accessory then set the Use Legend drop down to <None>

Have you updated the instrument summery. Updates are not automatic.

Do you have GDTF modes assigned to the lighting devices? If you do not have a GDTF mode selected when you export, Vectorworks will create a generic fixture that you would need to replace with the actual fixture once you open the file in the MA3. GDTF files can be created as emissive only, so it is possible that you could have selected a GDTF mode that is emissive only.

You don't need a loopback app, both ETC and Vision should communicate without any additional software. The one thing I have noticed with the ETC offline software is that it likes to be on a network. It seems to work better when the software has access to a DHCP server. I've had issues trying to setup static IP addresses and get Eos to connect and have always had issues. Be sure to enable the proper protocol in Eos and select the same one in Vision.

I have to search for this every time because it's buried in the middle of all the other objects-custom calls.... IsPluginFormat() Be sure to use it on the record format, not the record instance. It will return incorrect results if you supply a plug-in object (86) handle.

When you "import a fixture" are you importing a Vectorworks symbol or are you importing a GDTF file? The Vectorworks symbol does not contain the GDTF fixture and mode information, you must import the GDTF file in order to see it as a choice in the GDTF fixture mode dropdown.

It looks like an issue with Renderworks or a failed install of Renderworks. I would first check the minimum system requirements. https://www.vectorworks.net/sysreq Windows requires DirectX 11 compatible graphics card. If it meets the system requirements I would contact tech support directly.