Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

105 Spectacular

About willofmaine

  • Rank
    1000 Club

Personal Information

  • Occupation
    Vectorworks Design, Presentation & Construction Drawings
  • Homepage
  • Location
    United States

Recent Profile Visitors

1,462 profile views
  1. Thanks for your reply! Yep, I did make sure the Guides class was off. I guess deselecting "Draw Site Border" would have worked, but, for whatever reason, doing that seems to make it so that the site model can't have a solid fill in Top/Plan view. While that can sometimes be desirable, why is the site border linked to the model's fill?... There actually was a coincident border object, but, removing it didn't resolve the issue. Ultimately, I just set the site border's color to white. It looks like the Site Model Attributes for the 2D Site Border (at Site Model Settings > Graphic Properties > 2D Site Border) can only initially inherit a class's properties when "Make all attributes by class" is selected, but they don't subsequently remain linked to that class's properties, including its visibility settings in viewports. I didn't check "2D Triangles" in viewports, but, its attributes seem to remain linked to a class as expected. So it kinda seems like a bug... VWIS198
  2. Site Model Settings > Graphic Properties > 2D Site Border. I put the site border in the "Guides" class so that it won't show in my site plan viewport, and I click on "Make all attributes by class." But the site border (which I'm assuming is the line at the perimeter of the site model... ... ...) doesn't go away (though it is the color of the "Guides" class as it should be). When I double check the model's settings, the attributes of the 2D Site Border are correct... except that they're no longer "by Class." But that's maybe a secondary issue. Mostly, how do I make my site border go away in a plan viewport?????
  3. Here in the year 2020, I still wish that surface hatches, at least optionally, were NOT snappable. There are too many invisible snap points as it is; snapping to every particle of a stucco hatch seems entirely unnecessary... ... ...
  4. When creating the wall components of wall styles, and when setting the component's Fill Style to use the Class Style, I really wish that the component's color would automatically also default to "Class Style" when the class it's being assigned to has anything but a solid fill assigned to it (such as a hatch). Otherwise, trying to override the component's fill in a viewport - say to replace a hatch with a solid color - only results in the solid fill being applied, but not the desired color, because the component's color is still its default white color (i.e., while the hatch can be made to go away, the color white can't be changed). The hard-learned workaround is to remember to change the component's Fill Color to "Color by Class" before setting it's Fill Color to "Class Style." The challenge going forward will be remembering this workaround... ... ... Please make Vectorworks more intuitive!!! VWIS131
  5. This seems to persist in VW 2020 SP3, but much more difficult to replicate. The floating data bar now seems wise to the problem and scurries much faster to stay out of the way of the cursor. For all intents & purposes, we'll call it "Resolved!"... ... ...
  6. It seems the "extraneous and disconnected wires in networks" of my original post have been resolved!! But with testing to verify, a couple of new issues: Marionette Object Disappears after Editing Script (VWIS194): https://forum.vectorworks.net/index.php?/topic/70049-marionette-object-disappears-after-editing-script/#comment-344473 Marionette Network Symbol Misaligned and Difficult to Select (VWIS195): https://forum.vectorworks.net/index.php?/topic/70050-marionette-network-symbol-misaligned-and-difficult-to-select/ I've posted these issues in "Troubleshooting" because it seems more likely that they're Vectorworks graphics issues rather than specifically Marionette issues...
  7. After changing the drawing scale, it seems that Marionette network symbols and they're bounding boxes are completely unrelated, and sometimes even misaligned such that it's difficult to select the network symbol for editing. See attached video. VWIS195 03-Network Symbol Misaligned-1080-02.mov
  8. Testing to see if Marionette network nodes now keep their relationships to each other when the drawing scale is changed or different from the creation scale (once upon a time, they did not: https://forum.vectorworks.net/index.php?/topic/52644-marionette-wires-frequently-disconnect/&tab=comments#comment-263834 ). Looks like now they do!! But... After editing the Marionette test object and the network symbols it contained, the Marionette object all but disappeared. It exists, which can only be proven by its presence in the OIP. Otherwise, it's completely invisible, without even the benefit of pre-selection or selection highlighting. See attached video. Subsequently adding another instance of the Marionette object and editing that brings back the first instance. I'm posting this in "Troubleshooting" because it seems more like a graphics issue than a Marionette issue... VWIS194 05-Marionette Object Disappears-04.mov
  9. It's custom built geometry (Sweep > Subtraction > 3D Symbol > AutoHybrid). And when I just opened the file to check, the curves were, yet again, completely faceted... So, maybe I was wrong above about having to restart Vectorworks... Solids seem like a much better thing than 3D polygons and meshes; I wonder why PIO's don't ever seem to use them...
  10. Almost four years later, and I still wish that cameras would be automatically activated when editing them via a viewport. If not for me (most of the time I remember to activate them...) then at least for people new to Vectorworks. Along with saving users some time and frustration, it might help expand any perception that Vectorworks is intuitive...
  11. This problem (from December, 2017) seems to persist with Vectorworks 2020, SP3. However, the (or at least a) solution seems to be simply re-rendering the offending viewport. After that, it's not an issue. The problem seems to occur only the first time the viewport is rendered, and that only after Vectorworks (not just the file) has been closed and restarted. Oddly, whether the "3D Conversion Resolution" (for both the Viewport and for Vectorworks Preferences) is set to Low or Very High, the results are the same with "smooth" curves (i.e., the same slight faceting) in both cases. And, either way, it takes about 1 1/2 minutes (give or take a few seconds) to render the viewport. It's as if the 3D Conversion Resolution settings don't have any effect on the viewport, either in rendering quality or rendering time...
  12. It appears this issue is not resolved with SP3. VWIS179
  13. This issue persists in SP3. I neglected to mention in my original post that "Zoom Line Thickness" needs to be turned on in order to see the different line weights. Also, after having set up the viewport and the 0.70mm reference line, if you switch from "Best Compatibility" to "Best Performance," it's necessary to zoom at least a little before the line weights actually update. It would be nice if Vectorworks had "real-time" graphics, let alone real-time rendering.
  14. This issue persists in SP3. It seems it may happen all the time, except when trying to locate one symbol after another, without interruption to do something else in Vectorworks.
  15. It turns out that it's not Page Scale symbols per se, but, rather, it's Page Scale symbols that are contained in Hybrid Symbols. When editing the viewport and zooming in too far, the ability to snap to geometry of the Page Scale symbol is lost. See attached Vectorworks file. 01-Can't Snap to Page-Scale Symbol.vwx


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...