Scott C. Parker

Here's how to replace the hook. I didn't try changing the hook symbol name after I edited it. let me know if changing the name will still associate the hook with a different hoist. If it doesn't, I'll inquire further. ReplaceHook.mp4

Hi Peter, I was intrigued by this and played around for a while. Apparently, truss crosses can only have one location where the truss meets in Vectorworks 2024. When I changed the tool to insert a drop instead of a truss cross, it worked once I had a proper offset. I had to change the minimum length for the down leg in the bridle preferences to one mm before using the tool. Here's a video I made to explain the process to our programmers. You can skip to after 2:30 to see success. insertdropparalelltruss.mp4 I'm submitting a request to allow multiple trust crosses so that the lower truss does not need to shift down at all. However, we would expect it to shift to account for the spacing of the coupling device.

Hi Peter, Yes, my truss were directly from the VW libraries. I confess I didn't seek out the same truss you used from our library during testing. The truss in the drawing you shared has had some custom changes made and I didn't want to mess with them. All truss in the VW library *should* be able to have some braceworks calculations applied. When we have the structural info from manufacturers, we get more info about flexibility. When we don't, we treat them as static systems. Hence the Grey and Green results. I'm not sure what you're asking here. I made frames, and they worked.

In this example, the strip light is aligned to the left and all others are centered. If the strip were assigned to be centered with the others, it would knock all the others far away from the left border box .

@tbexon, Widen the Spotlight Equip Summary Key dialog and use the Alignment column. Let me know if you have issues.

Update 4.1 is out and offers the centering you're looking for. Once you update to the latest release, please test again and let us know how things go. You may need to update and/or rebuild your summary keys. We fixed an issue with them between updates 3 & 4.

@Peter Telleman I don't have a direct answer other than it's something to do with the modified truss symbols you're using. I played for a while trying to figure out what but I failed. To confirm the calculations would work outright, I built two similar frames using Tomcat and Christie truss. They both calculated as expected. Here's the file I played with. Your custom symbols might not match anymore as I was making edits. Tomcat is grey as we don't have the structural info. The Christie frame is green as we do have the structural info. vertical trussframe.vwx

If you widen the report window, you'll see the lights are not connected to the truss system. Braceworks will only report on items that are fully snapped to the supporting truss system. We have a few videos here that would be helpful to take a look at. https://university.vectorworks.net/course/index.php?mycourses=0&tagfilter[category]=content+category-5-entertainment&tagfilter[type]=0&tagfilter[difficulty]=0&search=braceworks&langfilter[]=0#coursestab Basically, you have placed the lights along the front of the truss, but not actually snapped them to the truss..

Please post a sample file for us to look at. Might be those lights are not attached to the supporting structure.

Please share a file so I can play. What release/build are you working in?

@tragge8 What happens when you place a summary key in a new drawing? The underlaying file you're using was originally built five years ago. Not that this should cause issues, but it does on occasion. Let me know please.

We are hunting a bug and this file helps. For now, I recommend placing a viewport of a summary key in your rigging design layer over the title block area. The Summary key is working as we wish in Design layers. Sorry, no; you can't place viewports inside the title block style. It'll have to sit over the title block on sheet layers for now.

Please post a test file so we can see your settings.

It sounds more like you're looking for an instrument schedule based on each truss. If you create a report and use the Criteria window to limit the worksheet to each truss, you'll get what I think you're looking for.

I'm happy to take a look if you can post a sample file. Adding class to the filter is on our list of fixes we need to do.

I played with your file and changed the number shown below to 10mm and it all worked. It's like a forgiveness setting. 🙂 Keep in mind that it can get you in trouble when two truss systems you don't want to be connected together are within the accuracy limits.

Did you do the delete thing and insert into a design layer process I mentioned? I'm bug hunting and if this process works, it's helpful to know.

Lain, Would you please post a test file so we can follow the steps you mention?

Is this in a sheet layer or design layer? If you started in a sheet layer... Delete all summary keys. Insert a summary key in a design layer. If the text looks like line, adjust the text via the three text formatting buttons. Once placed in the design layer and the text is visible, placing new summary keys in sheet layers should work. Please let me know how this goes. If this doesn't work, please share with me a file. Thanks, Scott

This is what I was going to play with. It should work.

You might have used the page setup or print setup settings in the template file that carried over with the new file.

Hi @Wesley Burrows I've not played with this. Would you please post a test file so we can explore? Thanks, Sc ott

Have you played with using the slice/split tool instead of the aisle tool to separate the seating into separate sections? It might serve you better. Can you share a file for testing? Just the seating layer.

Please post a sample file showing how you used the User Field or a custom record mentioned above. It'll help us explain how to get where you need to be.

How did you build your data tag? It sounds like it might not be associated with the LED screen. I find the easiest way is first to select the object to which you wish to attach the data tag and then use the "create data tag style" command under the tools menu. This makes sure the data tag will be associated with my object. If I created my data tag for a TV, it won't work with an LED screen. With that said, you can use the small triangle of the data tag to "associate" the data tag to the LED screen. Perhaps that will fix the issue. Do you have a sample file you can share? Como você construiu sua etiqueta de dados? Parece que ela pode não estar associada à tela LED. Eu acho que a maneira mais fácil é primeiro selecionar o objeto ao qual você deseja anexar a etiqueta de dados e depois usar o comando "criar estilo de etiqueta de dados" no menu de ferramentas. Isso garante que a etiqueta de dados estará associada ao meu objeto. Se eu criar minha etiqueta de dados para uma TV, ela não funcionará com uma tela LED. Dito isso, você pode usar o pequeno triângulo da etiqueta de dados para "associar" a etiqueta de dados à tela LED. Talvez isso resolva o problema. Você tem um arquivo de exemplo que pode compartilhar?