Scott C. Parker

Hi Mickey, Sorry, without looking over your shoulder, I don't know what is missing from your workflow. Perhaps you could make a recording while doing what you're trying to do? Watch out, it'll work. 🙂 Happens to me all the time when trying to show an issue to our programmers.

@MatthewW Well, at first go in 2026, the system works without issue. I did two tests here to make sure the tilt report would switch sides when I added the light. I have to dive deeper in 2025 to figure out why it's not working. It's very possible we fixed something in 2026 for this very type of issue.

I believe this should work, provided all the parts have the proper truss records/settings/connections applied. Please post a sample file so that the collective can take a look. Yes, and no. It's not designed to work as a grid builder and supports only one or two clamps for each side arm pipe.

I could not agree with you more. We're looking into this. Could you share a sample file with the different systems and steps you find yourself needing to do on a regular basis? Most of my workflows requiring changes to truss revolve around changing rental companies and swapping out one brand for another. Most often of similar sizes. Changing the truss to completely different profiles is challenging, to say the least.

I have a list for the next round of improvements to the Spotlight Equip Summary Key. Can you share some visual examples of what you're looking for?

Open the settings of the wall and then open the Support pane. In there, you can assign the double and then the single support symbols. The wall should then automatically place them for you.

In the generic LED panel library, we have 500x500 panels in both flat and curvable versions. As Mark mentioned, copy that and change the info in the record as needed. For your 500x1000, make a duplicate of it and then edit the 3D geometry and the info in the attached record to match. Key rules: 1. 3d only. No hybrid panels. 2. The insertion point must be in the lower left, front corner of the geometry. 3. Bend points must be set.

Good idea. We already do this for LED Walls and Inventory worksheets. I've added your request to our enhancement list for future work.

@Terry SmithWe're working on making the whole thing easier. As fr workflow, I usually draw it out on paper and then follow the power.

I'm seeing this as well. I've filed a bug report. Thanks!

@ColinMeyer Building Segmented Panels Use multiple symbols (segments) within the main panel symbol for dynamically curving panels. By default, the bottom-left and bottom-right corners of each segment are used as pivot points. To customize, place loci at desired pivot locations. Segment symbols do not require attached records.

I look forward to seeing your success.

Two things. Sorry... even with all the extra stuff hidden, the debugger still sees everything. I'm happy to help, but it'll be much faster if you duplicate the symbol and delete all the stuff you think is not needed. This will help be see how you built it. Perhaps it's hidden, but you're missing the power inputs to get power from the main switch.

The panels I used are in the Generic LED Panels file in the RM. You could use these as your starting point and edit the geometry as you need. As for adding the half panels to the top or sides, use the LED Wall preferences dialog, seen here. You already have a way to do this via the existing snapping tools. Adding it directly to the LED wall preferences is a good idea. I'll add it to the list for future development.

You're right. I've added a bug report to update the help files. I've seen this as well. Closing and restarting VW seems to then reset the order of the fields in the record after the merge. let me know if that works. Thanks, Scott

What does it look like when you navigate to the data tags directly in the RM?

If you can send me a version with just the first few circuit parts and connections, I can take another look. With all the extra items, it's hard for me to untangle and see what needs to go where.

Terry, I took a quick look at your file, and your distro has a lot of disconnected and cross-connected components. To test this and see the missing connections, go to the Edit Workspace editor and add the "Check Distributor Symbols" command to a menu in your workspace. When you run the command, it will list all of the missing connections. I would also suggest you make a much smaller distro to test your setup. Let's say, the three phases, one set of fuses, and just one set of outputs for the two phases of power. Once you have that working, building the larger one will make more sense.

Change the Feet Height in the Light Info Record.

Hi @ColinMeyer Some answers and comments to your post. First, thank you for taking the time to dive into the new LED wall tool. It's been a long process and we appreciate all the feedback we're receiving from users. As with any new tool, it will take a bit of time to learn all the aspects and take advantage of the power this new tool offers. We are creating training materials for all the tools, and the minutia takes time to cover. Thanks, Scott Although we don't have the FL series panels from Absen, here's a result from my experimentation with a seven-section panel, where the two end sections are half the width. Though the FL is built to offer a smooth curve along the seven segments, I played as if it could have multiple angles between segments here. Pretty cool. When I add an option to use 6 bend points, I can create an uneven panel face by clicking six times along the path. However, since the FL panel doesn't bend that way, there seems little point in worrying that it would be set to 2 or infinite. If you have an example of panels that need the granular bendability, please send them along. Users have the option to add as many choices for bend points as they wish via editing the record itself. You can set the concave/convex to whatever you wish. The 15/10 is just a starting point. If you change the two joint max numbers above to 2.5°, you'll be limited to drawing walls with 2.5° angles between columns in the wall. True. We recommend that users do a bit of pre-planning should they wish to exchange panels afterwards. If one draws a wall at 5827mm wide, we're unable to use 600mm panels to match the size. However, if the user finds out their panels are 600mm, they can edit the wall to 6 meters and then change out the panels. Well, if you prefer to build them manually, we made sure to keep that as an option. Here are two circular walls. The left uses static, non-bending, panels and the one on the right is set to two bend points. We've not only not removed the function, but we've added to it. We can now add half panels to the top, the sides, and the corners. Since these panels come in sizes other than just halves, we're calling them Perimeter panels.

Please post a sample file so that the collective can take a look.

Please post a sample file so that the collective can take a look.

Hi @Mickey I spent some time with your file and i think I've figured out why you ran into trouble and then had success. For the the two error messages shown... You had the XSF truss library downloaded when you built the initial system. When you tried to change them to Tomcat, it didn't find any symbols in your resource manager and popped up an error. Why? Likely because you had yet to actually download the Tomcat library to your resource library. Hence, the change truss dialog couldn't find it. Now, why did it work after you had dumped the ESF system and rebuilt it using Tomcat truss. This triggered VW to download the Tomcat library to your RM. After all the closing and restarting, you then had both libraries downloaded. This brought the Xmas miracle, as you had both libraries, and the truss change dialog could then find the parts from both. So, going forward, I suggest downloading all the trusses you plan to use prior to using the replacement tools. Restating might be necessary, but I'm not sure. hth, scott

I'm not sure it's been finished yet. We have a bunch of info in the help files. https://app-help.vectorworks.net/2026/eng/VW2026_Guide/EventDesign1/Creating_LED_walls.htm?rhmapfs=true#h

Have you added the weights to the Light Info Record for the lights?