Jump to content

sbecraft

Member
  • Posts

    12
  • Joined

  • Last visited

Everything posted by sbecraft

  1. UPDATE: I figured out what the bug is but not how to solve it. When selecting the source end of a inter-layer connection, spotlight numbering works. When selecting the destination end of the connection, spotlight numbering does not work as stated in the original post. I assume ConncetCad views these connections at each end as different things and not one connection between design layers. Is this a current limitation of this version of ConnectCad or is there a way around this issue? Thank you
  2. I am used to using spotlight numbering for connections within a design layer and I remember being able to use it to number connections between design layers. When I use spotlight numbering for connections in between design layers, it does not properly recall a connection's "Circuit" object where you would select the "Number" field to increment. Instead the connection object reports as a "Object with Record" that lacks the fields required to number the cable. I am on the latest version of VW. Any ideas on where the issue lies? Thank you
  3. I would like to get a report of the total cable length for a given cable type. I'm using the cable element length field to track the length of a given cable instance. Cable Type is pulled from the cable instance name field. When I create a report that summarizes based on the cable type and sums the length I don't get any sum. Even when I use a custom field and try to sum on a summarized field, I don't get a sum. I'm a bit new to reports so I may misunderstand how summarizing a field and summing a field work together. Individual cable instances: Summarized based on cable type and summed cable length column: Type instances is counting how many cable type instances are summarized. Thank you
  4. I guess a better way too put it is, how to change the size of text/sockets relative to the size of the device frame that gets generated.
  5. Does that mean that if a document I imported from VW2021 is at a scale I don't want, I have to move everything to a new document?
  6. For VW2020 and VW2021 I believe the scale of the device text and sockets where related to the size of the snapping grid at the instance of device creation in the document. Now if I place a device, it seems to always have the same small text and socket size. The picture below shows snapping grid size 1mm, 4mm, and 16mm. Is there a new system of managing their scale? This example is from a VW2020->VW2021->VW2022 document so there may be some old setting causing this. If that is the case, do you know what that could be? I performed the same test with a new VW2022 ConnectCad template and had similar results. Only difference is that the text and socket size was larger, but still the same across the 3 snapping grid scales.
  7. When I add rack equipment and name it a known device name, the details of the rack equipment don't update. I have to manually edit all the parameters of the rack device. I only noticed this in VW2021. This worked in VW2020. Further, is there any way to have the rack equipment auto generate from the device list? Thanks
  8. I changed the snap grid size back to 4 since that is what I designed the original sheet in. That solved the issue. Thanks
  9. I upgraded my ConnectCAD workspace from 2020 to 2021 and now any new socket or devicebuilder device is half the scale of my previous devices and sockets from V2020. The scale of the document is 1:1 and was a document made with the ConnectCAD 2020 template. I can copy "old" sockets and its size stays the same (larger). Is there another scale that needs to be adjusted? Thanks
  10. Removing the old ConnectCAD.vww file and restarting fixed the issue. Thanks for the help
  11. Some of the ConnectCAD tools are missing in VW2021. The tools appear as red X's as shown in the first photo. If I try and use the tool I get the error message shown below. I see ConnectCAD plugin data if I go to the folder in both /Programs/Vectorworks and /AppData/Roaming/Vectorworks. Restarting vectorworks or changing workspaces does not fix this.
×
×
  • Create New...