Scott C. Parker

Please post a sample file so that the collective can take a look. It’s best to copy the problem items into a new file to keep the file small and avoid any NDA issues at hand. Please use a definable file name. We get so many named “sample.” 🙂 Thanks, Scott

VW 2026 = VW31 So, VW29 = VW 2024 The VW24 = VW 2019 In your screenshot... VW24 shows that the underlying template used was originally built in 2019. VW29 shows the last version of VW that saved the current file. If you want to have a new file show VW31 (2026) as the very first iteration of the file, you would need to delete the "blank.sta" file from your default templates folder so that VW would then open a new blank file with absolutely no starting point template settings. Then start a new blank document.

It turns out the weight you're seeing is coming from a hidden record attached to the original symbol you're playing with. Deleting the user-accessible records did not remove all the info from the base truss object symbol. When I double-click on the pipe in the RM, the Truss insertion tool is activated and places the pipe as a truss object. Since the default records are not attached to the symbol, the resulting truss object is missing a bunch of info. What's still there is the weight. Here, we see the truss properties are incomplete due to the missing symbol records. The Spotlight Equip Summary Key reads the records attached to various Spotlight objects and is hard-coded to seek the info and report it in the Key. I'll add an item to our wish list to allow reading a specific record to cover weight. What are you trying to achieve by using symbols without the expected records?

You should be able to right-click it and select Open. Then, do a save as and save it to a new location, user or workgroup folder, etc.

Well, this is odd. I'm going to send this to our programmers to see what's up. Thanks for sending the file.

Sorry, I don't know. https://www.vectorworks.net/en-US/public-roadmap

The connector for the DMX 5pin was updated in the cableconnector.xml file. Here's an updated copy of @LiteDoctor's file with the revised connector in the 5pin cable records. Christie Lites v2 v2026.vwx

Have you found issues with the replace fixture type workflow in recent releases?

Please post a sample file so that the collective can take a look. It’s best to copy the problem items into a new file to keep the file small and avoid any NDA issues at hand. Please use a definable file name. We get so many named “sample.” 🙂 Thanks, Scott

Please post a sample file so that the collective can take a look. It’s best to copy the problem items into a new file to keep the file small and avoid any NDA issues at hand. Please use a definable file name. We get so many named “sample.” 🙂 Thanks, Scott

We're working on improvements. Schematic views are wildly complicated to code.

I sent the file to our programmers, and they drilled into it and found that the 'fill' of the class in which the video image for the panels is set to none in the file you shared. When using the same panel in a new drawing, the fill is set to solid. This is why it works in new files and not your template file. To fix this in your template: While in the none class, change the fill from none to solid in the attributes palette. For walls that are using an assigned class via the LED Wall settings dialog for the video image, edit the class attributes and change the setting from none to solid.

I'm not having an issue when using your tile symbol in a new file. Perhaps it's a class visibility issue in the file you're working in.

This issue has been fixed in the upcoming update 4.

You're not doing anything wrong. This was a bug in 2024 and has been fixed since. To fix your text issue, place the key on design layers and then check the text styles/fonts/sizes applied. As for counting, there was an issue between reporting symbols vs. plug-in objects within the key. Try both and see which one works. I don't remember the actual issue at the time. If you still have trouble, post a sample file so that the collective can take a look. It’s best to copy the problem items into a new file to keep the file small and avoid any NDA issues at hand. Please use a definable file name. We get so many named “sample.” 🙂 The answer may end up being the need to update to a more recent release of VW. Thanks, Scott

I understand your frustration. Combining the two, as done for DMX, is not a trivial task programmatically. It's on the wish list. @markdd offers a great solution. I place the two fields next to each other, and right/left justify the text fields.

Double-check that you're using the default classes via the LED wall preferences dialog. And I was about to add what @JustinVanHassel just said 🙂 Please share a file.

Please post a sample file so that the collective can take a look. It’s best to copy the problem items into a new file to keep the file small and avoid any NDA issues at hand. Please use a definable file name. We get so many named “sample.” 🙂 Thanks, Scott

Here's a sampler. Explore the tool for a while. It has a lot of options. VW LED wall 2pt5degree sampler.mp4

Note... It turns out that cables contained within Favorite files will also come to play. Cables in the favorite file will be scanned before the cable files in workgroup, user, and program folders.

Sorry. No news yet. It's in the pipeline to be checked.

Do you ever share your files with other users? If you share a file with a user who doesn't have your font installed on their machine, it'll get replaced. If you do not, please let us know and send us a test file. I believe the list comes from VW reading all the available fonts on your computer. Just like a word processing program does. I often remove all the extra fonts from my font library that I never plan to use. You can create your own list of text styles and grab them from your RM instead of using the drop-down selectors. If you ask the AI Assistant, under the help menu, this "How do I set up text styles to use in all of my documents?" you'll get a set of instructions.

It's being added. Every time we help users figure something like this out, we learn what new detail is needed in the help files. Current symbols are built with the bare minimum to allow for fast rendering/processing. When building the symbol, the content team doesn't group the parts, as making the symbol itself is a de facto group. Thanks for your help in improving the help file. You should see the new text in an upcoming update.

With help from our wonderful content team... It's the light, not the top hat. In the RM, right-click on the light and choose Edit 2D Components. Ungroup the 2D parts. No groups allowed in the 2D component. It messes with the rotation. Exit. To tidy it up ever so much In the RM, right-click on the light and choose Edit 3D Components. change to a right or left view. Select all move all so the yoke is at zero/zero exit

It's not you, it's us. You've found a bug and the engineers are looking into a fix. For the time being, if you use truss symbols instead, all should work. I've made a quick symbol from your truss to play with. Custom Truss Magnet Issue - CREDO 04.02.26.vwx