Jump to content

jcogdell

Vectorworks, Inc Employee
  • Posts

    425
  • Joined

  • Last visited

Everything posted by jcogdell

  1. @JMiller that is the designed behavior, a flexible/pliable truss cross is designed to represent fixing the pipe with a steel rope or some other form of non rigid (movable) attachment method (which in the case of an out-rig pipe would be dangerous), where as the fixed definition is to model a rigid or hard connection like when using doughty clamps or burgers. I not 100% sure whether this is bug, as I can kind of see why it might get triggered. I'll contact the developer and ask about it. Not all warning/error messages will prevent a truss system from calculating, typically as long as the issue will not physically prevent the calculation then Braceworks will calculate the system. The issue highlighted may for example just refer to a potential documentation problem like having several hoists with the same ID.
  2. Check that you don't have enable vertical offset toggled on in the insert connection tool mode bar (its the green tick icon to the right of the tool preferences)
  3. another option is to use the insert load tool from the rigging tool set, once the load object has been inserted go to the OIP and tick the Show symbol box then hit the select symbol button to convert the default geometry into a symbol of your choice
  4. Hi Dave if you are using 2021 or 2022 the distributor tool from the new cable tools will allow you to attach distro boxes to trusses and have them included in weight calculations. in 2021 the distributor tool is located in the preview tools palette, which you may need to turn on in 2022 the distributor tool is now in the lighting tool set or you can in the resource manager navigate to Vectorworks Libraries Defaults>Cable Tools and look in one of the distributor folders select the distro you want by double clicking on it and insert it on the truss as normal
  5. I can't reproduce this in 2022 or 2021, could you send me the file so I can figure out what is going on? (send it by DM if the show is confidential)
  6. Hi Martijn can you share the file with me? What build did this appear in? (normally this message should only appear in development builds) Gruße Jesse
  7. Hi Leppi I've had a look at your file this seems to be because of the hanging angle of the bumper, if the bumper has a hanging angle Braceworks assumes that it needs a second motor. This looks like a bug, from what I can tell it only appears when multiple hoists are used. I'll get the bug report in. If you don't want this included in the Load overview you can use the load filter to turn if off. I haven't found a way to turn it off for the create report command though. Gruße Jesse
  8. As far as I can tell the behavior for the Fixture ID attribute of the label legend is the same in 2020, 2021 and 2022, in that it references the instrument type parameter of the lighting device. You will need to select channel or unit number in the edit label legend dialogue to display these parameters in a label legend.
  9. open the resource manager, right click on the symbol and select attach record from the context menu. You may need to import a truss symbol into your file to make sure that the truss record is available to attach to your custom symbol
  10. Can you send me the file with the problem so I can take a look at it?
  11. I'm working on a set of detailed skill videos for the new cable tools, as soon as they are finished I will let you know
  12. I had a quick look at your file and as far as I can see the issue is the H30V C017 corner has the wrong dimensions in the geometry pane of its Truss properties, by default it is display L1 as 710mm and it should be 713mm. I'll get a bug report into the content team to have the symbol corrected in the default libraries In the mean time to fix this in your current file right click on one of the H30V C017 truss corners and select 'Customise truss symbol data' from the context menu this will open the truss properties dialogue in the geometry pane change the contents of the L1 field to 713 hit ok to exit this will correct the symbols definition. You will need to rebuild the truss system to get everything correctly lined up (if you look closely you can see the the cross corner in the center is not correctly lined up with most of the straight truss sections) Also make sure to save the symbol into your user or workgroup folder so you don't have to fix it again for future projects.
  13. At the moment it looks like we don't have this in the library, If you are a Service select member you can make a fixture request through our customer portal in the support page Otherwise you can contact the UltiRender team (our Finnish Distributor) and ask them to make the request for you
  14. I will make an enhancement request, this is happening because the house rigging point tool converts the symbol into a parametric object which then blocks the record being visible in the data pane. If you ungroup the hanging point object after insertion the data record will become visible, however this will break the house rigging point object and convert it back into a symbol From my understanding this is the default behavior in Vectorworks whenever a symbol is converted to a parametric object by a tool and the few exceptions to this rule (like lighting devices and trusses) have been specially engineered to allow specific records to still be visible in the data pane
  15. Yes this is fixed, I just checked it to make sure (2021sp4) and as far as I can tell it is behaving correctly
  16. In this generation of the cable tools Distributor objects are primarily designed to document/display how the system is connected, so there is no way to document the individual MCB's (breaker) and RCD's (differential breaker). The work flow for creating a distributor object is create or select a symbol for the distributor object in the resource manager right click on the desired symbol and use the attach record command to attach the 'CableDistributorRecord' by ticking it in the attach column while still in the attach record dialogue select it (highlights in blue) and hit the edit values button to open the record and fill in the data. For the Input type and output type fields you will need to use the connector universal name from the Cable Connectors xml file (found in your application folder>Libraries>Defaults>Cable Tools) exit the dialogue and save the new distributor into your user or work-group folder.
  17. Hi Ben There are 2 related problems that you are dealing with here When using Daisy chain mode you have to make sure to set up the auto-numbering to use the same cable run ID for each cable in the chain, or only the first cable in the chain will be given a cable run ID as it is the only cable directly connected to the breakout. If the cable doesn't have a cable run ID there is no data to push to the lighting device At the moment the lighting device circuit name and circuit number fields only get data pushed into them if the cable object is connected directly to a breakout. I will put in an enhancement request to have this behavior improved, ideally the lighting device should document the connected cable no matter what it is connected to at the other end. At this point in time the only option in Spotlight is to create a custom report documenting the lights circuit name, number and wattage.
  18. From looking at the ACT notes about the plugin it was fixed fin Vectorworks 2019.
  19. Hi Gabriel It is no longer necessary to use the import option to access speakers in the default Spotlight libraries. Instead select the symbol option in the source drop-down menu and then use the select symbol dialogue below to search for the speaker type you want to use
  20. Hi Nehemia Wie haben Sie die Projektionsfläche in Spotlight erstellt? Haben Sie das 'Video screen Tool' verwendet oder haben sie selbst erstelt? Freundliche Gruße Jesse P.S Bitte posten Sie in diesem Forum nur auf Englisch, da die Mehrheit der Vectorworks-Mitarbeiter kein Deutsch spricht. Wenn Sie Unterstützung in Deutsch benötigen, wenden Sie sich bitte direkt an Computerworks.
  21. The basic problem is that there isn't any Braceworks cross section data available for any Tyler trusses, as they are not willing to share the needed structural analysis data for their products with us. This in turn causes auto-connect to restrict how corners will connect with trusses in 3D (it will only allow the corner to connect in the horizontal plane). Currently this is a hard coded restriction when there isn't any cross section data available, we are changing this as part of the 'Refactoring of Truss Engine' task that's part of the development roadmap but that doesn't really help at this moment. I've contacted a college on the content team to see if he can find a solution for you. If you have access to the structural data for this type of Tyler truss you could create your own custom Cross section for it, which in theory would fix the problem.
  22. What type of truss and hinge are you using? From your description of only being able to bend the hinge or connect the custom corner in the horizontal plane (X/Y axis) it sounds like the truss you are using has no Braceworks cross section profile and is using the default rigid setting. Which then restricts corners and hinges to connecting in the horizontal plane Another possible issue is that bookend style hinges are restricted to only being usable in the horizontal plane (outside of a couple of exceptions this is per manufacturers recommended use guidelines, from my understanding). Effectively this mean that for this configuration you would need to use a center point type hinge.
  23. @MattG The default definition of the hoist fields are Hook Weight equivalent displays the total load acting on whatever the hoist is hung from, including the hoists own body weight and the total weight of its attached chain (max chain length x weight per meter or foot). Hoist Weight equivalent displays the the load acting on the Hoist Hook Force and Hoist Force display the same data but as a force (Kilonewton, pound-force, etc...) rather than a unit of weight. Since you are not using Braceworks you don't have to use these fields the same way. The only limitation is that the fields are formatted in the hoist properties according to the type of data they are designed to display, so fields documenting a force will use kN or lbf and weight fields kilograms or lbs (or whatever your document units are) This will not cause any problems, you could for example do a test hang of your rigging system, using load cells to get the exact loads for every hoist in the system and then add this to the hoist properties. The only thing to be aware of is that if your file is then run through Braceworks the values in the fields will be replaced by the results of the Braceworks calculation. The new hoist object record has 2 versions of each weight related field in its object record, plain and formatted. The plain version displays the weight in the internal format that Vectorworks uses (Grams) and the formatted version will display the weight using your document unit settings. The fields use the same naming as the Hoist properties. @stevenmorgan94 The enhancement request is in for this As long as you are not going to be using Braceworks you can do this, see my above answer
  24. You can set the measurement label (and the ID) classing in the hoist tool preferences before insertion using the classes button or after insertion in the hoist object properties the same way
  25. Not sure if this helps but you should be able to change the exported report's page size when printing from adobe reader in the print dialogue. I'm not sure how well it will scale when adjusting the page size if it is a big change (A4 to A3 for example) but from the preview it looks like it will work OK for going from letter size to A4
×
×
  • Create New...