Jump to content

Xurion

Member
  • Posts

    16
  • Joined

  • Last visited

Reputation

3 Neutral

Personal Information

  • Occupation
    Senior Light Specialist
  • Location
    Netherlands

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Sam, let me put that differently. It was not my intention to offend anyone with that, I don't mean that label legends aren't useful.. I can see it's a useful way to way to show all the fixture information you need in some worksflows. When we started working with Vectorworks 3/4years ago Data Tags became more useful to us in more and more situations. Ontopic: Nevertheless, the labels legends are the only way to display information about the other cells. I can live with that, but I think it is very important to be able to include it in worksheets.
  2. Good to know, thanks for your reply 👍
  3. As of now there's only one way to show the data of the second, thirth or fourth cell of a fixture, and thats by using the legacy fixture legends of Vectorworks Spotlight. We've stopped using these legends a while ago and started using Data Tags for this purpose, which seemed way more flexible at the time since and still works way faster than manually editing the placement of 3D Fixture Legends. Now I've started to make some multicell fixtures but theres no way to show the data of the second, thirth, forth and so forth cell.. There's no way to define a dynamic text block to grab the data from these cells, and the same goes for worksheets (patchsheets) and .CSV or .XLS exports from Vectorworks. Which makes the multicell feature kind of useless for our usecase. For example, I've got a multicell 4-light blinder. The left and the right side have different circuit numbers and different DMX adresses. If i wanted to make a detailed dimmer patch worksheet for this, I can only show the first cell. Are there any workarounds for using multicell fixtures? The only way to make complete patch sheets now is to duplicate the multicell fixture on a hidding design layer (and I have to make sure this hidden layer isn't included in any count worksheets).
  4. Adding a output seems to re-enable daisy chaining, however I can not assing L1, N & PE to the consumer object. Wich seems a bit odd because I have to define a connector type for the consumer object. I don't think I'm going edit all of our Lighting Device symbols for now and wait for a proper solution in the future Service Pack releases...
  5. Maybe It's possible.. But I haven't discovered that yet. Not everything about the Cable Tool is documented well..
  6. Hi Bogdan, Your cable .vwx files need to be in the installation folder->Libraries->Default->Cable Tools. We made a .bat file to automate this and make updating these files easy. The .bat file looks something like this: xcopy "..\Libraries\Defaults\Audio Tools\*" "c:\Program Files\Vectorworks 2021\Libraries\Defaults\Audio Tools" /i /e /Y xcopy "..\Libraries\Defaults\Cable Tools\*" "c:\Program Files\Vectorworks 2021\Libraries\Defaults\Cable Tools" /i /e /Y xcopy "..\Libraries\Defaults\Stock Bridle Materials\*" "c:\Program Files\Vectorworks 2021\Libraries\Defaults\Stock Bridle Materials" /i /e /Y xcopy "..\Libraries\Defaults\Hoist Tools\*" "c:\Program Files\Vectorworks 2021\Libraries\Defaults\Hoist Tools" /i /e /Y
  7. Works great. Thanks Jesse! Off topic, but quick question: Wattage of Lighting Devices arent used for the power information. Am I supposed to draw Input, Output and Consumer objects in all of our Lighting Device Symbols? Drawing only a Consumer object will disable daisy chaining...
  8. Hi everyone, I'm currently in de process of updating our libraries to get everything working with v2022. While working on our Distributor Objects I came across the following issue. I've got no control over the order in wich the outputs are shown in the IOP. Every output is named and numbered in the "Name" field of the Electrical Output object, so alphabetical/numeric order would be fine. But nonetheless the outputs are shown in a seemingly random order. Has anyone figured this out? My whole experience with migrating from v2021 to v2022 has been troublesome. I have to figure out how everything is meant to work by myself. After 3 days of battling with Truss Magnets (our custom truss library is quite large).. It would be great if in the future there would also be an explanation before the release on how to change symbols to work properly in the new version, in addition to the release notes. I am aware that the cable tools in v2021 were still in beta. But I'm getting off topic..
  9. I think i found the reason why @Antonio Landberger got it working and I couldn't. Everytime I try to import the marionette symbol I imported the referenced symbols first. When I don't do this, everything works fine. If you want to reproduce the bug I'm experiencing. First import Scaff large silver part + Scaff small silver part + Scaff small black part. Import the marionette symbol afterwards. Thanks Antonio and Jesse for diving into this issue!
  10. That's strange.. I tested it in our template file and a blank file and got the same results.
  11. I got the same result on 2 different machines with the latest Vector works servicepacks. Dropping it on the design layer of the same file works fine. But importing it on another document and dropping in into a design layer of that document with the same scaling causes all nodes to disconnect.
  12. Here's a file with only the red symbols. Scaff only.vwx
  13. Hi Antonio, thanks for your reply! I've recreated my marionette network in a blank document on a design layer with the scale 1:50. I made it into a plug-in object symbol. Opened another blank document with a design layer of the same scaling and I got the same result as I described in my previous posts. The marionette network I made and tested in the first file, does not seem to work in the second file. When I try to edit the marionette network in the file I imported the symbol into all connection lines apear as normal. When I move one node, all nodes get disconnected. So I've tried everything from scratch with the same scaling and got the same issue.
  14. I've made a screen capture of the issue I'm experiencing: https://youtu.be/W1ceB8eU8CI
  15. Hi M.Graf, Thanks for your quick reply! Setting both documents to the same scale does not seem to solve the problem. I checked both documents settings units and design layer scaling.
×
×
  • Create New...