klinzey

Vectorworks, Inc. has released a Service Pack for Vision 2023 (SP3.1). This Service Pack includes targeted fixes to address a file saving issue. Vision SP3.1 fixes file saving issues with XFroms and when using non-default textures. Users should use Save As when saving a file after the file has been opened in Vision SP3.1. If a file is opened with SP3.1 and textures are missing, the textures will need to manually assign in the document. When opening a file saved in Vision SP2/3 in SP3.1 and everything looks correct, Save As should be used to ensure the file is saved properly with the textures embedded. If textures are missing, you can fast track the manual restoration process by placing all missing textures in a textures/scene folder alongside the .vsn and then reopening the file, this should cause the textures to automatically load into the file. This requires the textures to be identical to the ones in the original file(same hash) so it may not always work (if you no longer have the exact texture used). Save As should also be used in this case to save repaired file. This Service Pack is available for all licenses as a downloadable updater. To install the Service Pack, please select "Check for Updates" from the Vision menu (Mac) or Help menu (Windows) or download the full installer from your customer portal.

@Lauren87 Just so that you are aware all the resources in the educational file are watermarked and if you use any of those resources inn a professional document the professional document will become watermarked and become an educational file. You will be notified when this happens but always use caution when working with educational files. You should be able to use your professional license on both Mac and Windows. We allow for 2 installations of the software but you can only run one at any time. For the US, and many other regions, professional version can open an educational file and the conversion from older versions should be the same. (Some regions distribute an educational version that can not be opened by the professional version.) The issue you are experiencing would also likely happen in the current educational version. I'd be curious to see what the file looks like in the original version before it's translated to the newer version.

Try to remove any un-used lighting device symbols, or even just symbols, from your document. Build List must process all lighting device symbols in document even if that are not used in the drawing and this can take some time if there are a large number of symbols in the file that are not being used.

Please be sure to run the Vision installer or repair Vision after installing the grandMA ESP Vision connection supplied by MA Lighting. The grandMA ESP Vision connection overwrites the necessary dll supplied by Vision.

@Bill McGarvin You need to have a full vision license which will unlock 255 universes. Please contact your sales representative to your options.

No, If your Vision license is only for 4 universes then Vision will only receive 4 universes from the MA2.

Can you post the file or share it with tech support directly? There is something unique about those fixtures and we will need the file to investigate the issue further.

I tried the Data Drop.vso in 2023 SP3 Mac and did not have any issues opening it in the plug-in editor or adding the tool to my workspace.

Unless something has changed the Name in MA should be mapped to Instrument Type in Vectorworks. https://app-help.vectorworks.net/2023/eng/VW2023_Guide/LightingDesign1/Visualizer_data_mapping.htm?rhsearch=visualizer mapping&rhhlterm=visualizer mapping mapped map

Data from the _VS-ModData record is used to create the object only. It uses the necessary information and then the record is no longer used.

This is intentionally a free text field to support workflows and users that do not use the focus point object. If we limited this to a drop down of choices of focus points it would break the workflow of many existing users.

I suspect it may be the insertion points of the containers that are off, not at the center. The text labels look to be in the correct location.

@DBLD The issue with the Vision updater should be resolved.

@DBLD That's SP1. I have asked our installer team investigate the issue. Till it's resolved you can manually download the installer from the customer portal.

@Sam Jones The information from the label legend of the imaged fixture are shown even if the columns are summarized.

Launch Vision and from the Help menu select Update Vision. This should download the latest version.

Most of the libraries are delivered on demand from an online server. First thing to try is to make sure your Resource Manager cache is up to date. Open the Resource Manager and click on the gear icon. Select Refresh Libraries. See if your your libraries show correctly now. If this does not work I recommend contacting technical support directly as you may need to manually clear your Resource Manager cache.

Make sure you are running Vision 2023 SP2. It contains a fix for a VizKey issue.

No there is currently noting you can add to the criteria to eliminate the labels. We are looking into this issue as an enhancement for a future versions.

In your Rendeworks Background make sure you have the "Receive Shadows" selected in addition to having the Lit Fog option checked and the fog density set. Just as a warning it rendering will take a lot longer when you enable "Receive Shadows" for the background.

No. Traversal is always done is creation order. The only way to do this would be to have the the menu run a temp tool to let the user select the objects. You can then capture the order the objects are selected as they are clicked.

If I'm reading the code correctly you are trying to add fields to the parametric object record in Vectorscript which is not possible. If you are trying to build the OIP and the underlying parametric record dynamically in Vectorscript that's not possible. You can dynamically build a variable number controls in the dialog but the you will need to need to store the data differently because you can't add record fields to the parametric record via Vectorscript. You have 3 options. If you know the maximum number of fields create them all and show/hide them as needed. (This is the easiest solution but limiting.) You can create and store the data in a standard record format, that allows you to add new fields as necessary. Store the data in a delimited list in a hidden parameter of the parametric object. You will need to insert and extract the data as needed. (You may also be able to add the controls to the OIP but you will still need to manage the data for the controls with your code, Vectorworks will not do it automatically for you.)

I would recommend you contact tech support directly. We will need to detailed machine specifications and the crash logs in order to diagnose the issue or reproduce the problem. There may be something else running on your machines that is causing issues with Vision. Even on a low end machine you should be able to open the smaller demo files included with Vision and playback the pre-recorded dmx. There were no significant increases in hardware requirements between 2022 and 2023.

It would be helpful to see the script. You should not need to click in the document when running a plug-in menu command but you will need to click in the document if you have create a plug-in tool.

No, MAnet2 does not work on the Mac. You need to run Vision on a Windows machine with a dongle to use the MAnet2 connection.