Scott C. Parker

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

Yes, it should work as before. If you're having trouble, please post a sample file so that the collective can take a look.

Hello @jjost I've played with your file, and with help from @JustinVanHassel, we figured out the issues. Your corner block was close (nice work), but needed a couple of things. As for calculating, check both Second order analysis and Compensate drops. Here's your file. Vectorworks Forum.vwx

Classes for this are particularly challenging, as equipment symbols can contain multiple classes within each. Can you expand on the workflow you envision that would use classes? btw, I don't disagree. Classes would be very helpful.

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

When I open your file, the truss objects do not seem to have the truss record attached. As such, when I right-click on the truss, I am not able to open the Customize Truss Symbol Data dialog. The symbols report as Invalid Truss Symbols when trying to convert the system into a Hanging Position. In the RM, right-click on the truss symbols and Attach Record to attach the truss record. Your file doesn't contain the record. Bring it in by using the truss tool and insert a truss from the stock library. This will bring in the record. Once attached, you'll need to add the appropriate info matching the truss objects you're working with. After that, you can then add the needed Truss Symbol Data. I was able to get to the Truss Properties dialog via: I opened your truss symbol and copied the truss geometry. I pasted the geometry into the design layer. I then created a new symbol of the truss object Then I used the Convert to Truss command and this is what opened the Truss Properties dialog. It is in this dialog that you need to add the needed info to have Braceworks see them as truss. More on building custom truss. https://app-help.vectorworks.net/2025/eng/VW2025_Guide/Braceworks/Creating_a_custom truss_symbol.htm?rhhlterm=convert converting truss trusses&rhsearch=convert to truss

I posted this a while back with a workaround for using the label legend version of the typical symbol, and my personal preferred workflow for typical symbols. The first half of the video, which covers the workaround and my workflow, is shown approximately halfway through the video.

To stop the lights from snapping to the actual truss, I suggest moving the rigged truss to another layer. Then, use the Spotlight preferences to turn off auto-snapping. Turn off snapping.mp4 Yes, Move by points worked for me. I played a bit and here's what I found. Movebypointverttower.mp4

Play with changing the numbers, ...parts ordered', '1', '1') The first 1 is the cable section. The second 1 is the part. So, ...parts ordered', '1', '2') will show the second part of the first section. ...parts ordered', '2', '1') show the first part of the 2nd section. As for your custom cables, Please post a sample file so that the collective can take a look.

What happened when you ran Braceworks? The answer is, if you used the Insert Connection Tool to build your piles of truss, it should work. If it doesn't, please post a sample file so that the collective can take a look.

RIght click on the power symbol in the RM and choose Edit 3D. Select the power source component (turn on the power parts classes) and use the Connector drop down to choose the connector you wish to use.

@Dylan Hovey Play with these. The one you want is =OBJECTDATA('cable section', 'parts ordered', '1', '1') Better yet, =SUBSTRING(OBJECTDATA('cable section', 'parts ordered', '1', '1'), '-', 2) ='CableObject'.'LengthPartsTotal' ='CableObject'.'CableRun_ID' =OBJECTDATA('CableObject'.'CableRun_ID') =LENGTH('cable break', 'Vertical Drop', 0) =LENGTH('cable section'.'Length') ='CableObject'.'Swag' =OBJECTDATA('cable section', 'Name', '0') =LENGTH('cable section', 'Start Slack', '0') =OBJECTDATA('cable section', 'parts ordered', '0') =LENGTH('cable section', 'End Slack') =OBJECTDATA('cable break', 'name', 0) =OBJECTDATA('cable section', 'Name', '1') =LENGTH('cable section', 'Start Slack') =LENGTH('cable section', 'End Slack') =OBJECTDATA('cable section', 'parts ordered', '1') =OBJECTDATA('cable section', 'parts ordered', '2') =OBJECTDATA('cable section', 'parts ordered', '3') =OBJECTDATA('cable section', 'parts ordered', '4') =OBJECTDATA('cable section', 'parts ordered', '1', '1') =OBJECTDATA('cable section', 'parts ordered', '1', '2') =CONCAT('CableObject'.'CableRun_ID', ' ', OBJECTDATA('cable section', 'Name', '0')) '=LENGTH('cable section', 'Swag', '1')' =Length('cable section', 'total vertical drop', [<optional section index>])

It could be the feet on the unit. You can always edit the 3D symbol and nudge things to match the manual. I'd double-check the actual unit with a tape measure to confirm the manual is correct.

@Matthieu Meriaux In the Starway Slimkolor 710 UHD, send the power consumer component to the front so it lands third in the list of connectors in the OIP. Then do the DMX connections first using the daisy chain workflow. Then do power.test with consumer SCP.vwx

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

@Iainy1961 Please try using #ZBBBG##fi_1_1# In your data tag, instead of "trim." Let us know how this works out. The beauty of using the bounding box and it reacts to the Trim Height field of the hanging position. "Trim" doesn't actually. It also reports properly when slanting hanging positions.

Usually, making connections on the input automatically connects to the output. But sometimes, one input is not actually the same as the connected output, most often when circuit breakers or fuses are involved. Add this to your workspace to check internal connections.

4. They're supposed to work the same for both design and sheet layers. Personally, I always recommend placing them on design layers and using viewports to place them on sheet layers. It gives more control over the resulting display, specifically the scale. I've often reduced the scale by 10-20% without confusing the crew. 5. Graphic legends do not work in design layers.

There's something about the pass-through circuit in the Coffret Tri 20Kw. I don't know what, but to get you the calculation you need for the system, if you bypass the Armoire 2 and go from the Source 2 to the Armoire 3, you'll get the calculations to work. Drawing the cable connections in the schematic view correctly, @JCodgell is correct; there's a known issue. However, if you want to draw lines, instead of connecting the two distributors using the cable tool, you can use the Connect Selected command in the schematic view, shown here. BTW, the Coffret Tri 8 lacks connections to circuits 7 & 8 N & PE

I don't know if you have tried these troubleshooting steps, but... Close VW and try number one first. If that doesn't work, try #2. Please reset your Resource Manager Cache to force a fresh download of the VW libraries. Refreshing your Resource Manager will update your library to the latest published symbols. You may need to clear your local RM cache file. Refreshing the RM doesn't always do this. Delete the RM Cache folder and then refresh the RM and it'll pull down a complete set of updated RM files. Win: C:\Users\username\AppData\Roaming\Nemetschek\Vectorworks RMCache\rm202x Mac: /Users/username/Library/Application Support/Vectorworks RMCache/rm202x Remember to replace the “username” with your computer username if you copy and paste the file paths Your file location might differ. Reset your user folder. Find your user folder for 2025 and rename it to something like 2025Cristiano so you can restore it later Start VW, and a new user folder will be placed. You might need your serial number for this. If resetting your user folder works, you can then start adding custom settings and plug-ins back in. When I'm searching for an item that creates conflicts in my user folder, I add each custom plugin, one at a time.

I agree! I've not explored my workaround enough to answer your questions with clarity right now, and I'm neck deep in some other things. I still prefer the line offsets Autoplot offers, and I hope to offer the same in VW's version as soon as practical. aka, not soon, but it's on the list. As for naming symbols, you can save the symbols with a new name for each, but use the short name field for paperwork. I never use the symbol name on paperwork, as it's always too long for the column width in my reports.

@JamesB1 I played more. I renamed a few connection components to help me trace where things were getting connected. You'll see what I did in this file. I spent my time working on getting one connection working as expected, and it calcs the three phases. Giving each component a logical name helps trace how things should be connected. I think all the work I did was inside the T4 symbol. hth, Scott PowerTest SCP.vwx

Hi James, your distro is missing a lot of internal connections. Add this to your workspace to check internal connections. Once you have edited the connections, you should have better luck.

This problem could be in the template file you are using. What happens when you paste into a new blank file instead of your template file?

All this got me thinking, and I have a workaround while data is being further developed. One issue is lighting content. VW automatically adds the power consumer parts to each light, and this doesn't help us with data connections. To fully use the cable tools for both power and data, we need to add new power components to our gear. After doing so, we can build a full set of paperwork and schematic layouts for both power and data cable runs. I've made a video and attached my test tile. CableToolsDataWorkaround.mp4 DMX cabling demo w data input w components v2025.vwx