Kevin Krautle

I am just testing out VW 2022 new cable path tool and other features today and the posted sample file is not doing ConnectCad justice. https://university.vectorworks.net/mod/page/view.php?id=2656 Can we have someone post a few better examples files? At first glance: Cable lengths not being calculated and drop points clearly not used properly. No cable route summaries ie drop point summaries Generally not a great design to showcase ConnectCad as you don't see the entire production design. Cameras going to encoders is fine, but does not showcase how to wire a small FOH or BOH control room using the most common switcher in use today which is the Blackmagic ATEM. Missing elements like audio No power distribution or callouts. Maybe post the theater file you have in the other documentation?

@Nikolay Zhelyazkov I DM'ed you a copy of both the bad file i had and after I fixed it. Sorry for the delay, busy times.

This is something that we have all been thinking about as power users. For now I am just using a device block to hold the cables and label the block as spare with connectors as XXX with the signal type that matches the cable. Basically an AV plate without it being a plate. From what I understand right now in 2022 you cannot do a logical schematic first, then drop everything down on the Physical 3D schematic later or go back and forth.

I have seen this as well going from 2020 to 2021, I have not seen this directly but had to fix some of our files that hold our symbol library. @ConnectCad Team ping me if you want one of my bad files. The good news is I have figured out what happened and have a procedure to fix the problem in a file having issue. In this example this is what my symbol was looking like before fixing: The problem is that a number of System Symbol objects got corrupted (which looks to be only the ones actually in use in the file at the time of conversion) In my specific case it was (but it can be more depending on which ones are in use in the file that got hosed): What happened is for some reason these symbols have been scaled down exponentially: To Fix: Open both the Vectorworks file that is having the issue and known good file that is still working. For each bad Socket Symbol that is not working in the bad file: Right click each bad System Symbol in Resource Manger and edit the 2D component. You can see which symbols are bad by drilling into a bad looking device and checking which style you are using. In my case it was the ones I was using in this example is: skt_con_IN skt_con_OUT skt_txt_L skt_txt_R Exit the symbol without doing anything - This will update the symbol in the file so that is then can be replaced into a know good working state. Note if you have 100's if not 1000's of symbols in your file, Vectorworks will single CPU thread crunch away 😞 for a while (100's has taken 3-5 minutes to crunch on my maxed out 16" MBP) depending on how many symbols have using this nested symbol in the file. Navigate to your known good file Resource Folder (while your bad file is the active file), and drag in the the Known Good Symbol to Import and REPLACE the existing symbol in the file. Note this does not work if you do not do step 1-2 first. Believe me I have tried just importing and overwriting the folder but Vectorworks will not override all of them at once for some reason (I suspect corruption as doing it one at time also didn't work). I found for each symbol that does not prompt for overwriting or not actually overwrite, I would have to do step 1-2. Click Replace when prompted: Repeat for each bad System Symbol After each replacement you will see all your symbols start to get back to normal, one replacement at a time. Below is an example after I fixed the skt_txt_L symbol, but before fixing the rest. After replacing the bad skt symbols everything has now returned to normal, and we live to draw another day: Thanks -Kevin

I have been thinking about virtual wiring and is wondering if anyone has done anything interesting to document the Dante/AES67 Grid? I have not played around with it yet but am thinking up a few ideas.

I am adding on to this request, As I like creating viewports to get a drawing into printable pages as well.

Good idea, just find it fascinating that vectorworks does not have that built in. A decent search system with some filtering.

I guess my feature request would be a CMD-F search box 🙂

Forgive me, I am working with 1000's of devices in a single document. Is there a way to search for a device by name/tag or other parameters then locate it on the design view? I know I can dump a device report, but how to find the actual device it on many sheets of drawings is the fun part.

Good point either way. Maybe it's a Preference checkbox? 🙂

This is probably related the post linked below.. Right now there is a very annoying bug that if i change a name of a device, the next time i go to update rack elevation for the sheet. It does not update the device name, but instead creates a duplicate device. On this same note, It probably should also be if a symbol is deleted it would change the rack elevation to red on the rack view sheet so we can identify devices that no longer have any use but are still in the rack.

I am also dealing with re-arranging dozens of sheets. Vectorworks team, can we add another column that will only populate for sheet layers that matches the # column in the Sheet Layers image? As I always want to export my PDF's by sheet layer arrangement I already have.

sent via DM

We just ran into a very bad bug that needs to be fixed ASAP! @Conrad Preen Right now if you number cables, it restarts numbering in every design layer instead of incrementing as per project file. Yes we can work around but its burning dozens of hours, and I mean dozens. Please see a screenshot of the issue as it exists you will see its in two different design layers but has the same restarted numbering.

This is confirmed fixed in 2021 SP1 THX -Kevin