[Vectorworks does it again]

Lain,

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

[Equipment summary text]

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

[Data visualisations in Equipment Summary Key]

2 minutes ago, TomWhiteLight said:

I wonder if you need two data visualisations with the same colours but one for light info record and one for lighting devices in schematic.

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

 

[Braceworks Calculation report PDF low quality]

On 4/10/2024 at 5:00 AM, Mathijs van Ommen said:

I just tried a new export without the use of my template.

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

[Data visualisations in Equipment Summary Key]

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

Thanks, Sc ott 

[Seating Tool Issue]

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.

[Lighting Position Worksheet]

 

3 hours ago, JamesB1 said:

For the manual option, either user one of the User Fields or attach a custom record the the first Fixture in each position and manually enter the Hanging Position into that field for the first fixture.  Then in Column A, use the field that only has data from the first fixture.

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.

[Data Tag para LED Screen]

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?

[Label Legend Containers]

@Tom Lightbody Could you share a small file for testing please? 

[Object elevation]

I shared this one that might be useful to play with. Though, it's not linked to layer height.

 

[Lighting Position Worksheet]

You'll need to turn off Summarize for that column.
Then, you'll need to use other columns to force sorting in the order you wish to have the info displayed.

[Braceworks Calculation report PDF low quality]

Can you provide a sample file? My test looks sharp.

[Create steelflex slings from existing slings in the library]

On 1/19/2024 at 5:18 PM, Martijn Wingelaar said:

Vectorworks provided slinging methods are actually wrong.

Hi @Martijn Wingelaar, If you can point us to incorrect symbols and the supporting paperwork from manufacturers, we're all for making needed corrections. These would be counted as bugs and would be added to the list of needed fixes as VW continues to be developed. 

[Equipment Summary / Compare to inventory not displaying]

@jkirchhofer Thanks for looking into this. We are working on solutions, but the timeline will likely not make either of us happy in the short term.

[Booms that just work when you make schematics?]

12 hours ago, Tom Lightbody said:

What's the way to do this that doesn't involve extra manipulation?

We are working on improving the schematic view workflow to deal with many of these issues. It's not you, it's us. For now, the best workflow I've seen is seen in @markdd's video on YouTube. Search YouTube for Mark Doubleday Schematic Views and see if his workflow works for you.

[Symbol Name Export from Resource Manager]

@Sam Joneshas a script that places all symbols in a file into a design layer, along with the symbol name. 

[Lustr 3 Symbol]

On 3/27/2024 at 4:24 PM, Alex Keen said:

On 2024 with updated libraries.  I can confirm that the symbol is absolutely not anywhere

@Alex Keen 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\rm2024
Mac: /Users/username/Library/Application Support/Vectorworks RMCache/rm2024

Your file location might differ.

[Cable Paths associations]

Cable paths are not obtaining the names of the objects they are snapping to yet. Here's what I do:

Set the auto numbering to match what you're snapping to before placing the paths. For example, if I'm snapping to my truss runs 1-6, I'll set auto number with a prefix of Truss- with the first number matching the first/next truss to be snapped and set the suffix to -Path. Then place paths in the order matching the truss clicks. This results in:

Truss-1-Path

Truss-2-Path

Truss-3-Path

 

You can also use the spotlight numbering tool to number after the fact.

[2024 Equipment Summary Key Tool]

This was fixed in Update 4. What build are you working with?

[Lighting Device default classes]

PS, here's the file back with my changes.Default Classes.vwx

[Lighting Device default classes]

On 3/25/2024 at 11:22 AM, ChollyO said:

for all of our in-house fixtures so that I can turn them on/off easily using our classing system

Have you played with the custom class settings in the spotlight preferences dialog? You can choose any field shown in the OIP for a light for the unit class. 

Here's a video with two methods for changing class names for symbols, which will help you build a custom library with the needed classes. 
It might be easiest to use the instrument type for the classes which removes the need to do the custom record editing I show.
 

 

 

 

 

[Data Viz in the Equipment Summary Key]

On 3/27/2024 at 9:13 AM, Tom M. said:

but not for Graphic legends, right?

Hi Tom, I confess, I don't use the Graphic legends, so I don't know.

[Data tag colours]

@LeeElston I don't know why placing the data tag as an annotation in a viewport strips it of its color. I've asked the tech support team and await a reply. However, if you place the data tags in your design layer, the colors show in the viewport.

 

 

[Static System Not Supported]

Have you tried the House Rigging Point tool?

 

[Data tag colours]

If you could share a file, it would be helpful for troubleshooting.