Jump to content


Vectorworks, Inc Employee
  • Posts

  • Joined

  • Last visited

Everything posted by jcogdell

  1. There are potential workarounds that you can try use a point load to represent the total weight of the lights and ladder, in your case since you are using 2 hoists I would add a short pipe for the hoists and point load to attach to Another option is to try converting the ladder into a hanging position, I'm not sure how well this would work as it would still not have the full structural data in the background for how the ladder itself will behave under load but it should give your the correct loads acting on the hoists (I'm not 100% sure though)
  2. @Projx_CA This is goes back to the issue of the lighting pipe ladder not being Braceworks enabled. In the load detail pane the lights are highlighted red to show that they are not hung from/connected with a Braceworks structural object. This means that although they display in the load detail view and each has an associated weight, they do not apply that weight to the rigging system, this is why the force column is empty. In the load overview they are present as load categories because you have them selected but none are connected to the rigging system so no total load for them is calculated, displayed or applied to the rigging system.
  3. Hi Patrick Did the file start of in Spotlight or was it imported from another application? If your file started out in another application it is likely not the GDTF lighting devices that are causing the problem but all the other non GDTF geometry that will have been imported as meshes. If this is the case a workflow that may help is to break down the MVR import into separate smaller steps by using the import dialogue to only import a part of the MVR at a time, then work over (converting from mesh to VW symbols/objects or into generic solids the imported geometry before importing the next part. If this doesn't help please DM me both the MVR file and the Spotlight VWX so I can have a look and see if I can figure out what is causing the issue
  4. Hi Luke The new cable tools are designed with this workflow in mind. The only thing the cable object doesn't do at this point is add the load of any cable hanging off the ends of the truss (down to the ground or to a cable pick) which needs a point load added to account for. The Vectorworks university has a complete learning path for the new cable tools, which can be accessed through the featured content section. https://university.vectorworks.net/
  5. You can convert Spotlight trusses into a hanging positions as well, so you can give the structure a name. Changing the Truss system name can be done in the Replace Truss dialogue (found in the Spotlight>Rigging menu) once the dialogue is open double click on the truss system you wish to change. The main issue with this is that as you draw more truss Auto-connect may override your system name. Another option is to use the 'Rigging Object Info record' that is attached to every truss at insertion Select all the sections of truss you want to give a name to go to the Data pane of the OIP click on the arrow icon beside position name so that you can manually enter the new name enter the name Once this is done you can use any of the Rigging object data tags as a label for the truss line or construction
  6. Is this a truss construction that has been imported from another application? if so they will have likely imported as 2D/3D symbols rather than as truss objects. You have a couple of options for how to deal with this select the truss construction (or just part of it) and convert it to a hanging position. This will allow you to give it a position name and attach lights to it convert the imported truss symbols/blocks into Spotlight truss symbols, The thread linked below explains the process of creating your own truss symbols redraw the truss construction using the Spotlight truss tool. Which option is the best for you will depend on what you are trying to achieve and who you are working with.
  7. You need to enable lit fog in the 'Set Spotlight Rendering Options' dialogue (Spotlight Menu > Visualization)
  8. At this time the only way to change this is using a worksheet, create a cable worksheet that displays the cable run ID, start and end parameters. Then when you change the parameter in the worksheet the cable object will automatically be updated. There are a couple of issues with this that you will need to watch out for, changing the start and end fields doesn't automatically change what the cable's geometry or redraw the cable, also it won't push any data into the devices connected to the cable, for example the circuit name or circuit number fields of a lighting device As far as I know the root cause of the problem is that the cable tool is required to push data between the individual objects data records. The electrical components will document the changes but they are not accessible to a worksheet at this point, only in the power info drop downs or in the power planning palette patch table. The dev team has a solution for this issue that will be in Spotlight 2023 which is released in September Normally this happens whenever the cable either starts or ends at an object that doesn't include electrical components (input, output, etc...).
  9. the underlying bug was fixed in 2022 sp3 and the truss content libraries should have been fixed with the release of 2022 sp4
  10. Hi Mucai No that was specific to that particular corner block It should be exactly half the length of the truss block in the X axis so for a 40cm block style truss corner it would be 20cm or 200mm The Truss properties has a diagram in the Geometry pane that shows where the reference coordinates should be take from for each point (P1 thru P6),
  11. Please reread my previous post, you have to link an imported GDTF file to the currently used Spotlight symbol to be able to use it as part of an MVR export, in a similar way to how you have to assign a DMX mode or Fixture type in the lights properties. You do not need to swap out fixtures. Neither Wysiwyg nor Capture fully support GDTF files, this is why in Wysiwyg you have to map the GDTF to a Wysiwyg symbol/personality at import for example. They both do not export a full/complete GDTF, instead they use place holder geometry and only include basic DMX patch, mode, fixture Id, type/name and location data as that is the only data that the MVR file format can document without a full GDTF being present for the fixture. Which means that the resulting MVR cannot be used to automatically set up a compatible console or other receiving software, without the user having to manually re-patch/configure/replace all the fixture data. The primary goal of MVR and GDTF is to make it unnecessary to have to manually map any data in the receiving software, this should be completely automatic. Sadly it is taking longer than the GDTF group had hoped to create GDTF's for all the existing fixtures available and in use around the world today. This process is starting to speed up and more manufacturers are getting involved but there are some of manufacturers that will likely never produce GDTF's for their products. It takes time to establish a new standard and have it fully accepted by our industry, for example DMX took 10 or 15 years to be fully accepted by the whole industry, hopefully GDTF won't take as long. This is something we need to improve upon, we are looking at several options to make GDTF's more accessible directly in Spotlight without having to manually run the import command. There are several other area's of the MVR and GDTF workflow that we will be improving over time, the most recent update was adding full support for the new 1.2 DIN spec, which meant adding GLTF (and GLB) file support to Vectorworks Spotlight exports all the Data that is supported by the MVR standard, however there is lots of things that are not supported like worksheets, exporting the contents of data records attached to objects that are not GDTF based since these are not part of the MVR standard and every other receiving software uses different standards for data transfer. If no GDTF is present for a fixture MVR will document a range of data including fixture number, dmx patch (mode and address), location and orientation and colour. There is some custom data that is included in the MVR that can be read by Vision but this is not necessarily usable by any other software. Data like shutter cuts, beam angles and so on are not part of the MVR standard and are normally configured in the receiving software based on the fixtures GDTF profile or the internal personality assigned if the receiving software doesn't fully support GDTF's
  12. You do not have any GDTF files in the Vectorworks file resources, which means they will not be included in the MVR To be able to export an MVR with valid GDTF's, the GDTF has to first be imported into your active files resources using the import GDTF command (located in File>import), once its in your active file resources you then use the GDTF Fixture dropdown in the Lighting device properties to select the desired GDTF and the GDTF fixture mode to assign the mode. This will link the Spotlight lighting device to the GDTF and enable it to be correctly included when exporting and MVR. To obtain GDTF files you will need to download them from the GDTF share website. Personally what I have done is download the complete share and use it to create my own custom GDTF library in my workgroup library folder. This way I only have to import the fixtures once and can then use the right click import option in the resource manager to bring the GDTF's into my active file as needed If the share doesn't have the fixtures you want then you can either create them yourself using the GDTF builder or send a request to the manufacturer to have them do so, I think the GDTF website has a standard format email that you can use for this.
  13. There are a number of different types of clamps, stands and so on for mounting fixtures in our library, mostly in either the ent lighting accessories folder or the ent stage folder. I have no idea whether they are as specified in the DIN spec but there are both generic options and manufacturer specific symbols. If you know the manufacturer try searching the library to see if there is something appropriate
  14. The Fixture type pane of the MVR export dialogue tells you what GDTF files (and the assigned DMX modes) will be included in the export. If an entry in the GDTF name column starts with 'Custom@' it shows that the light has not been assigned a GDTF fixture or fixture mode.
  15. Hi Juay I'm guessing from the lack of slings that you are using the default Spotlight bridle parts library, which doesn't contain any round slings. You can create your own custom bridle parts library with slings and other objects by opening the Stock Bridle.vwx library file. Its located in your application folder>Libraries>Defaults>Stock Bridle Material and can be edited like any other library file. Bridle parts should be stored in the file resources and have to have the BridleItemRecord attached to them to be classed as bridle parts The record defines the parts behavior with the bridle tool and object. Once you have added the new parts save the file back into the same location, make sure to create a back up of it as well as it will likely get overwritten if there is a update to the default libraries. open a new empty file, open the bridle parts manager and hit the update button to import the new parts into Spotlight. You should then have access the newly created bridle parts Let me know if you have any more questions here's the link to the help page https://app-help.vectorworks.net/2022/eng/VW2022_Guide/Hoists/Managing bridle_parts.htm?rhhlterm=bridle bridles parts part&rhsearch=bridle parts
  16. @CFL the only MVR import related issue that I am currently aware of is specifically to do with how GLTf deals with texture mapping. Can you post the file you are having problems with?
  17. Spotlight updated its MVR support to the new 1.2 DINspec with service pack 3, The main difference is that MVR will now use the newer GLB file format for geometry, by default. Its possible that Capture hasn't updated their MVR support to account for this. In sp 3 the MVR export dialogue has a new option to tell it to use the old 3DS file format for geometry, make sure this is checked and see if that fixes the problem
  18. Hi Dylan The easiest way to do this is using the insert drop mode of the insert connection tool. The tool preferences enable you to chose the hoist you wish to use for the drop. A second option is the Braceworks menu Insert Drop command, which will insert multiple drops at the same time, it uses the insert connection tool preferences to control which hoist is inserted.
  19. I'll get a bug report opened What mac OSX version? and what build number of Vectorworks are you using?
  20. The red crosses are the auto-connect attachment points of the truss, not truss crosses (the truss cross issue is being addressed in 2023) and are automatically created based on the truss objects BrxTrussItemRecord (accessed by the Customize Truss Symbol Data command in the right click context menu, not from the data tab of the OIP) Normally they should only be visible in Wire-frame or shaded polygon modes and not in Shaded or Rendered view modes. They will also display if the truss has been converted to a hanging position but this should only happen when the position is selected. This was an issue in 2021 and older versions of the software and as far as I know was fixed for 2022, it works correctly for me (I can only get the crosses to display if I'm in Wire-frame or shaded polygon modes), but I use a win 10 PC not a mac which may be part of the issue. Otherwise from your screen shot it looks like you may be using a customized truss library, since the trusses are black. If it is a custom library do you get the same issue using the default library version of the trusses? When was the custom library created?
  21. I don't have much experience using truss data vis in worksheets, so I can't say for certain why the data vis doesn't display correctly. Can you post the file so I can have a look? In regards to the pipe not taking the data vis, @Mark Aceto is correct, the most likely reason is that the pipe doesn't have the same data record or object type as the data vis is set up for. Personally I tend to convert my pipes into truss objects to get round this issue and then use the criteria object using parameter, Truss, Name for my data vis as this parameter normally a combination of the truss type and length.
  22. Thought I should add a quick update to this post, The above workflow is for 2021 and earlier versions of Spotlight, In 2022 you will need to add truss magnets There are a number of ways this can be done Use the truss magnet tool in the rigging tool set, to access it right click on the truss tool and choose the truss magnet tool in the menu that appears. You will need to insert the magnets in the 3D component of the truss and they should go into the Rigging-Truss-Magnet class. Insert them at each connection point, making sure that you set the connection type (defined by the position of the magnet on the truss) and the allowable roll ( all 4-chord truss should be set to 90°,180°, 270° for example). Automatically using the Update Truss Magnets command from the Tools>Utilities menu. This will add magnets to all the truss symbols in your active file resources. Its good for updating existing custom truss libraries. If this command is used make sure to check the classing and configuration of the allowable roll paramter for the magnets as it may not set these correctly.
  23. This looks like the shaded render mode (openGL if you are using 2021 or earlier) quality is set too low, Look in The view menu Rendering section for Shaded options once you have opened the shaded options dialogue set the Quality drop-down to 'High'. This t will give you much smoother curves in 3D views, it can have a performance impact if you have a lot of curved geometry or a large file though
  24. Is it the house rigging point that is being overloaded or the Dead hang bridle itself? If its the bridle that is failing check the bridle configuration is using the correct steels and shackles Another possibility is the safety factor, make sure that the safety factor is configured for usability in the Braceworks Preferences If none of the above helps DM the file and I'll take a look
  25. Hi Dan sorry for the slow reply on this one, We have a number of fairly similar sized 3 chord truss types in the libraries, including the eurotruss fd and hd 33, prolyte h30d, global f33 and more. How these match up load capacity wise I'm not to sure, without going through the individual manufacturer loading charts. We have been trying to add more Slick truss libraries but we are waiting for them to provide us with the required permissions and data (geometry or structural).
  • Create New...