Jump to content

TomWhiteLight

Vectorworks, Inc Employee
  • Posts

    868
  • Joined

Everything posted by TomWhiteLight

  1. Hi @Stefan B. I only work with entertainment customers so that does restrict the background of my users. In terms of my recommendation this is how I was taught this feature internally at Vectorworks. Some of the common issues I have resolved over the past couple of years include... Sync issues caused by poor broadband upload speed (below 25mb), External reference syncing issues caused by multiple origins, Lightwright Data XML sync issues. failed master sync due to multiple working files (this happens alot and is usually user error). I had one ConnectCAD customer who was receiving the Metadata is too large error. This was resolved by updating the file to 2024.
  2. Hi James. This is how we teach the project sharing workflow at Vectorworks, I don't think it exposes fragility in anyway, its faster and also you have the added benefit that when you open a new master file you can see that the file is syncing. There are many ways to use Vectorworks but nothing beats actually asking us what the best workflow is.
  3. Hey Stefan, Nikolay is the best person for this, I would also recommend opening a case with premium tech support. The forum is useful but Vectorworks staff respond as and when they have time, however there is a good chance a Beta tester or other user might also help out which is great. Remember as a Vectorworks Customer you qualify for tech support. Of all of my customers that are using project sharing there are only a handful (in fact currently only 1) with issues. So we need to get to the bottom of whats causing your problem. Is this in 2023? We changed the project sharing engine in 2024, I think we resolved all large syncing issues with this change. Let tech support know which version you are using and if this is still happening in VW 2024 "Refresh the working file (my gosh why is this not done during the 1min and 30sec of opening the file???)" OK this is a workflow issue, you should not be using the same working file on a day to day basis, creating a new working file while opening the master will avoid this from happening. I recommend the following.... 1. Arrive at work and open the master file 2. It creates a new working file which I spend the day working in, saving and committing when required. 3. End of day backup file, File Save a copy as (Save as .VWX) Then DELETE THE WORKING FILE (Please ensure that there are no other .VXW files from this project on your machine at the end of the day). 4. Next morning open a new master file and repeat the process.
  4. You can also use this on WiFi without the need for a physical loopback. Best thing to do is to ‘ping’ (flash) Address 1 Thru 512 from the ETC Nomad and then check the DMX viewer.
  5. I think it looks like the ‘use layout’ symbol that the label legend manager utilises was missing. It should however have still let you continue. If it happens again, I would contact tech support.
  6. Hi Clint. Have you downloaded the file further up the thread? coloured lens and more. Open that one and take a look.
  7. Hello, I have been out of office, just catching up. I think this is an enhancement request. I considered being able to set up a data map in the data manager to auto populate the position name from the HP field to the Truss object. Knowing that you probably wanted to break down which truss lengths you can utilise the location field of the Equip Universal Record and break down truss record by location in the inventory dialogue. Either way this is currently a manual process, I will make a feature request to map this data from the HP position name.
  8. Also, can you update the light info record from the defaults folder to rule out a legacy LIR. It would be worth doing a refresh instruments command prior to running the numbering dialogue. Then save and try again.
  9. Hmmm, I tend to create a camera, class it, choose my favourite settings (16:9 etc, 2d/3d and Name). Then I make it a symbol with convert to plugin object checked. Then insert it as needed. Then I don’t need to assign classes retrospectively.
  10. Are those lights attached to a hanging position? I cannot replicate this issue in 2024, can you post a file?
  11. Just had a look at this, I believe it looks at the current document. When I added new truss items into the design layer they then appeared as an option to replace with. When Symbol was in RM it couldn't see it. When Symbol was inserted as a truss object it was then visible.
  12. https://www.edgelightrgb.com/product-page/vwx-backline-symbols-v2020-buy-now
  13. I would try deleting the XML and setting up a new exchange
  14. What happens when you run a refresh instruments command? (In Vectorworks)
  15. @Dave Donley The only drawback here is the lens is glowing even when the light is set to 'Off'. That would be important to rectify.
  16. The data vis applies a glow texture with colour set to object attribute,
  17. Apologies, Forgot to explain that I had a data vis running on this!
  18. The tilt value will not be considered for the schematic. It is display a front view as a 2d component. Your best option is to use a viewport in a front view instead.
  19. I wonder if the Data Manager could be used to auto populate this data. This is tricky as the hanging position is like a sort of container with the truss objects inside, I am not sure that the truss objects ‘know’ that they are part of this position. I will see if my colleagues have any suggestions. Presumably you want to be able to breakdown how many truss items of a particular length and make/model are used to create each position.
  20. Yes of course, any data fields from records or PIO's can be used to create a data visualisation.
  21. Thanks for pointing this out Stefan, duly noted. I tend to use the 'Select System Objects' command followed by 'Calculate Selection' I will let my colleagues weigh in with other solutions.
  22. That looks correct. It depends what view you specify when you create the Schematic. This webinar should help. https://university.vectorworks.net/mod/scorm/player.php?a=449&currentorg=articulate_rise&scoid=898
  23. Also I don't believe this is true "Currently if you create a hanging position from trusses it is no longer possible to reference them in a worksheet." If you check 'Use plug in objects' It will still count all the truss objects.
  24. I don't think its dying, All of Jesse's points are correct and depict a workflow using rigging objects such as truss, pipe, etc. The Hanging Position command still has many uses, as mentioned above... Floor packages and particularly any custom geometry that you want to attach lights too. Its another tool/command in your arsenal to allow greater flexibility, Whether its applicable to your particular workflow is up to you. You give us an example of the kind of position you want to use it for?
×
×
  • Create New...