jcogdell

Hi Jazz Do have any of the manufacturer details? I can put a content request in for it if you do. Gruße Jesse

How big is your design? Does it have a lot of symbols? or is it more geometry based? Could you post the file or PM it to me? so that the Dev team can have a look at it Gruße Jesse

Hi Dave This is the result of the interaction of the ganging tool's preferences with the label legend assigned to the lights. As you selected the option, in the ganging tool preferences, to gang 'by circuit'' you will get a 2 part label for the ganging object (this will also happen if you select the option gang 'by channel and dimmer'). This is because in both of these cases the ganging tool label label is referencing the data in 2 data fields and combining it, 'by circuit' references both the 'circuit name' (top) and 'circuit number' fields from the fixtures. The horizontal offset that you can see in your example appears if you have set the one of these fields to 'right reading' in the label legend assigned to the fixtures. The easiest way round this is to prepare a label legend for the fixtures that you plan to use the ganging tool with , that does not have any right reading data fields in it.

Cheers Mark That's an approach I hadn't considered.

First, in the edit label legend menu make sure that you tick the fields that you want active in your 3D label in the use 3D column (red) if you want to set the 3D layout for the fields in relation to the fixture use the drop down menu highlighted in blue, choose none and then use the edit 3D layout option in the label legend manager to set up the layout. Otherwise the legend will use a default layout, depending on which option you choose. After assigning your legend to the fixture make sure that in the object info pane you have selected a 3D Legend view, otherwise it will not be visible (I normally use screen aligned). Lastly you may need to use the 'refresh labels' command in the OIP if you change views.

@mharvey Although it is not directly in our library yet you can download it directly from the Elation website, I've linked below for you https://www.elationlighting.com/tvl-cyc-rgbw

Just a quick clarification As Nina ha said we are working on the DWG/DXF issue and will continue to do so. However we are hoping that other CAD developers will adopt the MVR and GDTF standards. We have had several DWG based CAD Developers express an interest and have started conversations with them. We hope that our competitors involved with developing event planning applications will get involved, as it will benefit our industry as a whole and specifically you our users.

Vectorworks as a founding memeber of the GDTF Group, is currently working on establishing a new set of file and data transfer standards and protocols for the entertainment industry. Similar to how IFC and BIM have been established for the Architectural and Engineering industries. GDTF is a universal file type and protocol for the control of lighting fixtures and any other dmx controllable device that will function for any participating Lighting console, Previs application or CAD package. Effectively it is hoped that this will replace the need for each individual console type, CAD package or PreVis application to use a separate unique personality file or symbol. MVR is designed as a universal standard and file type for 2 way communications between CAD software, Lighting consoles and PreVis packages. It will establish a base standard/protocol for how each participating application stores and references data. This in turn will mean that any participating application will be able to correctly import from and export to any other participating application. An example of the potential of this is exporting an MVR from Spotlight that will automatically patch your lighting console and include all relevant fixture personality files needed by the console (in the form of GDTF's). You can then make a change to the patch in the console and export an MVR back to Spotlight with the changes to keep everything up to date. This can be repeated as many times as needed to finish your design! For more info about both GDTF and MVR, check out the GDTF share website https://gdtf-share.com/ On the website you can find a list of companies that are involved. If you use software from a company not yet involved, I recommend getting in contact with the developers and making the case that you would like to see them take part. The more users such as yourselves that get involved and use the new standards the quicker we can establish GDTF and MVR as the standards for our industry.

Just to clarify there are 3 versions of Vision currently available Professional Vision which is limited to only 1 DMX universe, Professional Vision Plus which has 4 DMX universes and Professional Vision Unlimited with unlimited DMX universes If your license is for the plus or unlimited version please contact US tech support and have them check that you have been assigned the correct license type, as the behavior that you are reporting indicates that your copy of Vision is limited to a single license

What Version of Vision do you have, depending on which version you bought you may only have 1 controllable DMX universe (student or basic). This would explain the patch behavior you are experiencing. As for color ( i asume you are talking about gels) you will need to manually set these inside of Vision. Spotlight and Vision currently use different formats for the symbols. The color field in the Spotlight lighting instrument is only for documentation and does not transfer to Vision. To assign a color to a generic/conventional fixture First select it in the scene graph (you can multi select fixtures) then in the properties window open the color wheels tab, select color wheel 1 and click on assign this will open a dialogue box allowing you to either pick a specific gel to assign to the fixture or manually select a color to assign.

@pgorski1984 As jugfire has pointed out this is partly due to your safety factor settings in the Braceworks Preferences, there are 2 other things that are affecting the calculation, the first is the cable flat-fare in the Braceworks preferences (default 2kg per meter) and the second is the positioning of your 2 hoists, unless they are exactly symmetrically placed on the truss each will have a slightly different load as one hoist will be carrying slightly more of the truss weight than the other. If both hoists are perfectly placed then the basic calculation including the safety factor and cable flat-fare would be as follows truss 62.4kg cable 18kg safety factor 1.35 (62.4+18)/2=40.2kg 40.2 x 1.35= 54.27kg per hoist If you need further help with Braceworks contact Design Express in Poland and ask for Robert Janiak their Spotlight and Braceworks specialist. He will be more than happy to help you.

The way to do this is to select your truss (all connected sections that you wish to do this with) and toggle the draw 3D only option on in the Object Info Pane next group select the trusses and lights, change to the appropriate 3D view (front for example) select the rotate tool from the basic tool palette and use it to rotate the selected trusses and lights to the angle you want. Changing the angle of the trusses and attached lights will break the connections for rigging hoists/deadhangs/bridles so you will then need to re-attach them before you can run any Braceworks calculations.

The lighting pipe tool has not been removed. If it is missing from your rigging tool-set you can add it back in by going to Tools-Workspaces-edit current workspace once inside the workspace editor open the tools tab expand the spotlight tools on the right, scroll down till the lighting pipe tool is visible and then drag and drop it into the tool palette of your choice on the left (typically lighting or rigging) This will add it to the tool-set of your choice

Also you can save your numbering settings as a template to reuse in other documents and it can be used on any object in Spotlight that has a data record, such as trusses, hoists etc.

Hi Robert The Tomcat truss is grey because Tomcat has not provided us with the background data necessary for Braceworks. When ever we have a truss type that is missing the data for Braceworks calculations (including trusses created with the old straight truss tool), a default set of data is applied and the heat map function will not work with that element to highlight this.