jcogdell

If you create a new text style in your document resources it will then be available in the hoist properties text style dropdown. otherwise you can try setting a class text style for the measurement label class of the hoist Another option is t create or customise a data tag to display the hoists coordinates and use that instead of the measurement label

@matteo esposito There are a number of things that can cause this but without being able to look at the file it is difficult to say what the actual cause is. If you can DM the file Tom or myself can have a look and figure out what is wrong.

@Erik Koehler Nothing should have changed as far as i know, can you DM me the file to have a look at?

As far as I know this is pretty much the only dedicated Braceworks spot, I know of several Facebook Spotlight groups but like you I'm not active on Facebook and have no idea whether they discuss Braceworks on any of them.

Yes there are 2 options, Calculate visible, which uses the current class and layer visibility settings to control what will be calculated or Calculate selection, where only the selected the objects will be calculated

The maximum chain length is contained in the hoist symbols data record, The easiest way to customise it is to import an existing hoist of the desired type, in an empty file give the hoist a new name, for example hoist x 100' in the resource manager right click on the duplicated hoist symbol and select attach record in the context menu, then select the hoist record and hit the edit values button. You can now edit the maximum chain length field (or any of the other fields) once you are happy with the new hoist save it into your user or workgroup library folder so that you have it available for future projects, you will probably need to refresh your resource manager afterwords.

Can you DM me the file so I can see if I can figure out what is going on here?

The easiest way is to select the instrument summary and then run the create data tag style command. and in the dialogue choose the active filter parameter.

I've opened a bug report for it

I just had a quick look on the ETC Augment 3D forum and found the following info from ETC "Howdy! As mentioned above, with VW2023, we are not developing a plug-in, but instead are using MVR export. For this, you will need VW2023 SP2, and Eos v3.2. Eos v3.2 is going into open beta next week, so keep an eye on these forums to sign up and download the software." You will need to reach out to ETC directly to get more info

You can use a Data tag to display the position that the summary is set up to display, choose the active filter parameter of the Instrument summary object when you set up the tag. This can also be used as another route to change the filter setting as well! As far as I can tell the position height and fixture weight options are broken, I'll get a bug report opened

This is a bug, I'll open a bug report for it.

I just tried to reproduce this and as far as I can tell it is working correctly, I used 2023 sp2 on a win 10 laptop can you post a sample file?

Hi Martijn at this point I can't find a way to do this, so I've put an enhancement request in

Hi Dan I'm not sure if its an oversight (bug) or works as designed with the new hoist but I agree it makes it much easier to understand by having the visual cue of the rotated dimension arrows Either way I'll open a JIRA for it and try to get it addressed

Thanks I'll get it fixed

I'll put in a request to have the help updated,

There is now a modifier key to control whether the cable can leave the path before the end of the path. on windows the modifier key is alt

I just tested this using 2023, using the Hoist report command and the worksheet export excel function, and as long as you change your document units to feet and inches with no fractions or decimal places before creating the report it will display correctly in Excel top image is the Spotlight hoist report and bottom is the Excel sheet that was exported using the worksheets export to excel command

@Ben59 The replace truss type will only work when both truss type libraries have the same lengths available, from looking at the ST500 library it doesn't include any trusses of the same standard lengths as the sc390 library. Normally in this scenario you would select the truss line and use the change configuration button in the truss object properties to change the truss lengths in the line before running the change truss type command, this way the lengths in the line will match what is available in the new truss types library.

The most likely cause is the custom furniture symbols, if they have a lot of heavy geometry (meshes, NURBS etc..) it can have a big performance impact on seating section, due to the number of symbol instances that the section can contain. The size of the seating sections can also have a big impact on performance. In the case of the custom furniture make sure that the 3D geometry component is made up of generic solids and look at the level of detail of the symbol

I've opened a bug report for this as it shouldn't be happening

Hi @åge-marius This Data tag is not correctly set up, Roof force should be the total force acting on the rigging point including the hoists own weight and should be in kN In 2023 it should be using the parameter 'High Hook force - #ReactionForce#', Workload should be the total weight acting on the hoist not including its own weight in Kg in this case it is the total weight acting on the rigging point It should be using the parameter 'Hook weight Equivalent - #ReactionForceWeight_formated#' I'll get a bug report in to have it fixed,

A loom can include any type of cable. The feeder, jumper multi and data cable type classifications are from the original Spotlight cable tools, and were carried over into the new tools to avoid changing terminology that was already standard in Spotlight. There isn't a fixed use for the tape color code field in the cable object, though its more commonly used for loom or truss color codes, rather than a company specific cable length or id marking. I'll add this as a enhancement request

@Mark AcetoI've had a look at your file and as far as I can tell the issue is being caused by the lower layers of unistrut being too close together, I found moving them each about an inch apart stops the duplicate truss crosses being created. I've Dm'd you a fixed version of the file