[Label Legend Doubling Issue]

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.

[MVR export from Vision...]

No. Vision does not support export to MVR.

[Edit 2D label legend issues]

Can you post one of your files?

[[Bug] Spotlight - Instrument Summary tool - Count function has bugs which give false counts]

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.
 

[Simple obj: a container]

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)

[MVR Import and export]

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"/>

 

[Importing MVR to VW issue]

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.

[PIO accounting for document units?]

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.

[Importing MVR to VW issue]

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.

[Remove Label Legend from Static Accessory]

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

[VWX ’23 spotlight question.]

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

[Exporting MVR file from Vectorworks Design not showing beam]

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.

[Parametric Record or Not]

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.

[GDTF Fixture Mode]

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.

[Can't seem to see LED wall content on some computers]

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.

[Viewport name already being used]

Also, worksheet only report what is in the drawing. Resources that are not in the drawing such as texture names, style names, symbol names, hatch names, etc. all must be uniquely named. Everything except for layers uses the same name space.

If you are not finding it in the document you may need to look at the resources in the document.
If you are searching for a specific name you may want to try a vectorscript such as:
{Replace NAME with the name you are searching.}
If GetObject('NAME') <> NIL then AlrtDialog(Concat(GetType(GetObject('NAME'))));
Then you can look up the object type here:
https://developer.vectorworks.net/index.php/VS:Function_Reference_Appendix_D
 

This might point you in the right direction if the name is a resource.

[Vectorworks 2022 Augment3d Plug-in Not Importing]

I would reach out to ETC about issues with Augment3d. The plugin is supplied and supported by ETC not Vectorworks.

[Disable Name OIP Field for Plug-in Object]

Yes.

Your object needs to be event enabled.

In  the kObjOnInitXProperties event you need to call.
SetObjPropVS(kObjXPropDataNameDisabled, TRUE)

 

kObjXPropDataNameDisabled = 35;

[GrandMA3 Varilite VL5 Vision]

I think all of the Vision fixture profiles for the lights like the VL5 with an external dimmer use the first address of the fixture as the intensity channel.
You don't have the ability to assign the dimmer to address 101 and the fixture to 201, if the fixture is assigned to address 201 then 201 is the intensity channel and the rest of the attributes follow. This is the way the DMX charts are setup for the VL5, the first address is reserved for the dimmer even if the fixture does not have one internally.

[Monthly or weekly Webinar/broadcast?]

Webinars along with Vectorworks Coffee Breaks are available on Vectorworks University.
Search for Webinar or Coffee Break to find them.

[Tool IDs for use in VS]

Normally Tool ID values would be available in the Function Reference Appendix, but it appears that Appendix A -C is currently missing.
https://developer.vectorworks.net/index.php/VS:Function_Reference_Appendix#settool
I have put in a request to have some investigate the issue and get the missing Appendix added back.

[Audio Tools Spotlight 2023 Symbol mode]

It's likely that the record data attached to the symbol is incorrect.
We use the record information to determine the spacing and if the record information does not match the geometry you will get speakers that are overlapping or spread apart.
See this post on how to make custom speakers and bumpers fro details.

 

[Legacy Hoist Origin Has No Graphic]

Since the the "Legacy Hoist Origin" is legacy we have not updated anything about the tool and discontinued testing. The legacy tools are delivered as-is  to provide legacy support for translated documents.
It's likely looking for a symbol named 'Hoist Origin Symbol' in a file in .../Libraries/Defaults/Hoist Tools/ that no longer exists. If you add a symbol named 'Hoist Origin Symbol' to the active document or to a file in .../Libraries/Defaults/Hoist Tools/ the geometry should show.

[Ground Stack Speaker Height]

Yes, You just need to set the Z height of the bumper once the stack is placed.
You should also be able to build your subs into ground stacked array.

If you are just placing speakers you can do the same with the speaker, adjust the Z height in the OIP after you place the speaker.

[Soft Goods - Adjustable Length Field]

In order to have the adjustable length field enabled the soft goods can only be a single straight line with only at start and end point.
I think I can see a control point in the screen shot.

 

You can double click to edit the polyline and use the remove point mode to delete the extra point or redraw making sure to only have a start and an point.