Jump to content

Kevin Krautle

  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About Kevin Krautle

  • Rank

Personal Information

  • Location
    United States

Recent Profile Visitors

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

  1. Good idea, just find it fascinating that vectorworks does not have that built in. A decent search system with some filtering.
  2. I guess my feature request would be a CMD-F search box 🙂
  3. Kevin Krautle


    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.
  4. 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.
  5. 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.
  6. 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.
  7. @Vectorworks team We have identified a bug in VW2021 which has been reproduced in both our migrated file, and a file created from scratch. The issue is that for our device symbols, we customize our dev_label_generic with additional text fields that are linked to the user1, user2, user3 dev_rec record type to show the additional info that we have for them. This is not working right now. The good news is that the data is still there, so I am not worried about it for now, but it needs to be fixed. Please see attached screenshots of the issue and a blank file created and reproduced with it. Linktext.vwx
  8. CC Team, With VW2021 you have added additional symbol types like dev_label_center. I would love to have a setting in CC settings to select which is the default for newly created symbols. This is a no rush thing, but would be nice as we use currently dev_label_generic as our default custom symbol and it will save clicks. -Kevin
  9. I use the term 'MTRS' for mini TRS (3.5mm), and 'MMTRS' for micro (2.5 mm) . Which I add using the ConnectorTypes.txt custom setup that conrad linked to above.
  10. On the data visualization note, You don't necessarily have to use a data tag to see an image of the device in your symbols. However it is a nice way for a different use case. The cool thing about CC Symbols is that you can add images to them after they are created, and then save them as symbols to reuse. To add an image, just doubleclick on your already created device on the drawing (just like when you want to edit connectors) and add your image. Just be aware of the location of the symbol template (in this example I use a custom dev_label_generic). Exit out of the symbol, and then you can save as symbol to add to your resource library to use again.
  11. CC Team, I noticed during my migration that if you have a custom SignalTypes.txt with blank lines in it, it causes a endless loop and pegs a cpu core at 100%. Its triggered when using device builder for example.I have to force quit VW to resolve. Attached my file for reference 2020 is the one that did not work, and the final adjusted file for 2021. I also did this with ConnectorTypes.txt but that one did not cause any issues (but it cleaned it up anyway). SignalTypes(2021).txt SignalTypes(2020).txt


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...