Jump to content

willofmaine

Member
  • Content Count

    1,082
  • Joined

  • Last visited

Everything posted by willofmaine

  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
  16. These issues persists with SP3, except that temporarily changing the window's ID Tag class to None and back again actually seems to cause the issue described in the last paragraph above, rather than resolve it.
  17. This problem persists with SP3 and, as before, it happens in "Best Compatibility," but not in "Best Performance." Also, when zooming way in, text just turns solid gray. Navigation Graphics don't seem to affect this either way. See attached SP3 video. 09-Text Solid Zoomed In-1080-08.mov
  18. Thanks for this but, unfortunately, it doesn't seem to help with this issue in Custom Renderworks... Thanks anyway!
  19. So last night I decided to overhaul my televisions, the screens of which use a texture consisting of an image and a glow shader. My first rendering with custom renderworks, all was good; I knew what I wanted to tweak. So I tweaked. But when I re-rendered, all textures were, what, blank?... huh?!?... Flash forward (through another good chunk of time lost to Vectorworks...) and I've concluded that making a change in the file, such as changing the visibility of a class, or changing a solid, thwarts the ability of Vectorworks to render properly. I found that changing the Quality settings of the Custom Renderworks Options would resolve the issue... at least until something else in the file was changed. At which point it would be necessary to yet again edit the Custom Renderworks Options. A super tedious and somewhat unproductive approach to rendering, to say the least... I replicated this issue in a brand new, blank file (attached, File 04, along with a video, File 08). Changing Navigation Graphics makes no difference. Also, because all of that wasn't frustrating enough, occasionally, the rendering would include inexplicable, extra geometry (video, File 10). VWIS193 08-Blank Texture with Custom RW-1080-06.mov 10-Nonexistent Geometry Rendered-1080-09.mov 04-Blank Texture with Custom RW-00.vwx
  20. Looks like SP3 is recently available, with all kinds of new features and capabilities... Hopefully SP3 also has countless, extensive fixes as well... I've got until September or so 'til I have to decide whether or not to jump in the nearest lifeboat.
  21. I wish that individual viewports could remember their Light, Layer and Class override settings, regardless of such objects' settings on design layers, and regardless of whether or not the objects' design layer settings may at one point or another temporarily coincide with the viewports' override settings (which currently results in the overrides being abandoned). As @markdd suggests, maybe a "Lock Overrides" button. For more on that and what's behind this wish, go here: https://forum.vectorworks.net/index.php?/topic/69769-vectorworks-override-fundamentals/&tab=comments#comment-343437 VWIS191
  22. Yeah, I'm still wishing for this. Almost four years later. And also wishing for the ability to name heliodons. Still.
  23. Ah... okay. That's very helpful in understanding some of what I'm struggling with. I turn all of my lights off for "All" (scenes) so that when I'm setting up, say, my tenth viewport, I don't then need to go back to each and every one of my previous nine viewports and turn off any new lights I may have added for the tenth viewport. So, right out of the gate, all of my lights turned on in viewports are done so as overrides, in which case all of their properties are controlled by their viewports (some quick experimentation seems to confirm this, just as you're saying...). So thank you for helping to clarify the implementation of overrides, though why they're implemented this way remains a mystery to me... At the very least, it seems a "Lock Overrides" option, or similar, would be especially helpful! Thanks!

 

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