klinzey

https://customers.vectorworks.net/support

Yes, Showcase is unlimited, 255 Universes, for all. Vision licenses are also now unlimited for everyone. You may need to contact support to get your Vision license updated to unlimited if it did not happen automatically with your renewal.

Once you import an image you have to create a texture from the image in order to apply it to a 3D object. https://app-help.vectorworks.net/2025/eng/VW2025_Guide/Textures/Using_an_image_in_a_texture_shader.htm

GetLayerOptions() https://developer.vectorworks.net/index.php?title=VS:GetLayerOptions Calling SetRField() should do it automatically for most plug-ins. Calling ResetObject() on the modified object should also force a recalculation. If neither of these work but the drawing updates simply by panning after the script is run you may need to call ReDraw() or ReDrawAll().

Nothing 2D is exported via MVR. The best way to make this work would be a 3D poly or an extrude and apply an imaged based texture. The texture will be exported as an image texture and mapped to the object if the receiving application can support it.

This works as designed. It's a little technical but once you convert it to a symbol the data can no longer be unique for each symbol instance. Also in this case you have 2 completely separate systems in the symbol which makes it even more complicated. You could build the circular truss using just symbols, not truss object, convert that to a symbol. Insert the straight truss symbols, as symbols, and then convert that to a symbol. The issue with this approach is that you would have to enter the structural data and other information about the entire circular truss and the entire straight truss. Manufactures typically only supply data for a single section of truss so it's difficult to do something like this.

I can not replicate the issue. The edit field should automatically be added to the OIP when the option is checked in the OIP. What happens if you switch back to the Spotlight Defaults in the template file? Does it correct the issue?

They should be in the non-plot class by default. If you turn the class off it should hide them.

Now that someone brought it up I had to go back and figure out what was in Appendices A, B, C. Appendices A, B, C existed in the printed MiniPascal manuals but I haven't seen it in anything recent. Depending on which manual I read, it covered how to contact support, how to encrypt, Reserved Words, Numeric Formats, Editor, Pallets and Commands, Search Criteria.

@Daniel Cortes VWXWhen you use a truss symbol or light symbol you place a truss object or a lighting device object and not just a simple symbol. Using the truss object and the lighting device object, and not just a simple symbol, is what allow you to rotate the geometry.

You have a bumper selected in the Bumper tab. You need to set it to "None" if you do not want a starting bumper.

The rotation between the Vectorworks symbol and the GDTF file is off by 180deg. We are working on correcting the issue. If you display the GDTF geometry in Vectorworks and view it in 3D the orientation of the GDTF file will match the export.

The "Black" color when rendered comes from the texture applied to the geometry not the geometry color. The default instrument texture uses a fixed black color. You can either create a new texture or modify the existing texture to use the object attribute color.

You can also check out COFFEE BREAK - CREATE CUSTOM TRUSS OBJECTS

To make a PIO paged based you have to to the math to scale the geometry that is drawn based on the layer scale of the PIO. There is no magic option to make a PIO automatically use page based units.

Scale should not matter, unless you are using a legacy setting that allows for viewing design layers at differing layer scales at the same time. If you have a sample of the document that was "fixed" by changing layer sales can you please post it or send me a DM with the file.

If refreshing the library and restarting did not work try the procedure outlined here:

Can you post a sample file?

Can you post the GTF file? Does the GDTF file open in the fixture builder without any errors? Unless there is something very wrong with he GDTF the MVR export should not fail.

@Valo Can you post a file here or contact support so we can get a copy of your file. It's likely something file specific.

I tested on Windows and it works. Are people only seeing this issue on Mac?

Is there a specific shape or configuration of the lighting pipe that is causing you issues? Can you provide a sample file? I tested with several in 2025 and had no issues exporting on importing a MVR.

Are you working with a true "Project File", a .vwxp/.vwxw file or a regular Vectorworks, .vwx file? If you are a true Project File try saving a copy as a .vwx file and exporting. I made a quick test with a simple file and the MVR exported and imported correctly from/to Vectorworks working with both a .vwx file and a .vwxw project file.

Double check your workspace. If you migrated your settings and workspace settings from 2024 to 2025 you may be seeing a workspace that was migrated form 2024. I notice that there a few other new items missing.

Make sure you are using update Vectorworks 2025 Update 2. It contains some fixes for sACN. By the look of the screen shot it appears to be responding to Pan/Tilt because it's not in the home position? Make sure the light is turned on when you view the light in Shaded mode. Try changing your DMX provider to ArtNet, exit the dialog and change it back to sACN. Make sure your fixture mode or GDTF mode is set the same as Eos.