Jump to content

P Retondo

  • Content Count

  • Joined

  • Last visited

Posts posted by P Retondo

  1. Wes, I used to uncheck "show components" in Viewport advanced preferences.  I don't want to eliminate all the components or turn off classes, I just don't want to see components at 1/4".  So that is a big change, and the "low, medium, high" detail settings are not at all the same.  BTW, if I turn off component classes, things like gyp bd and sheathing just disappear, and all we see is the wall framing component.  Sorry, but to me this is just one more example of VW sloppy engineering and lack of consideration for the professionals to whom their software is supposed to deliver for my yearly payments!

    For example, viewport at "medium":



    Same viewport at "low", missing door double line, jambs, and French doors in closed position:



  2. Thanks, Mark - I double checked, and my Unified View settings include displaying screen and plane objects.  Tried "active layer only" both ways, no difference.


    Pat, the more I think about it, the behavior of screen 2d objects in 3d edit space is probably a bug.  Try it.

  3. Pat, thanks for chiming in.  Following your suggestion, if I change my 2d preferences to "Working Plane Only," I can create a 2d object in the 3d edit space that persists as a "Symbol Definition" type (just the fact that this additional 2d object type exists is a red flag!  Kluge!).  If I use my standard "Screen Plane Only" preference, the object immediately disappears and is visible as part of the 2d symbol.  If this difference in the result depends on 2d object preferences, I'd call it a programming oversight.  If a Layer Plane object can be automatically converted to "Symbol Definition" type, so could a Screen Plane object.


    I can't get an extrude to persist in 2d edit space - that's where I can't replicate what you are getting.  It immediately disappears, and shows up in the 3d symbol.  It actually disappears even before I complete the extrude operation.  I don't understand why the "old way" had to be changed - if it ain't broke, don't fix it!

  4. As I use 2020, more disappointments.  Editing 3d portions of hybrid symbols is impossible, you have to create the object outside the symbol edit space, then paste it in.  Can't turn off wall components in Sheet viewports without losing important door and wall graphics.  Based on these alone, I wish I had stayed with 2017.  I just have to wonder whether the engineers consult with actual architects when they make these changes, changes that in my opinion have no plus side.  Hoping to find the silver lining promised by one of my trusted VW compatriots!

  5. It's not the answer you want to hear, but I create a NURBS curve for the entire handrail and extrude-along-path.  The system I use is to draw lines at the appropriate height in each elevation, convert to NURBS, draw arcs from above and convert to NURBS, reposition things so endpoints align (you can also join), then compose into a single NURBS.  After extruding, edit the profile and reposition it - in your case, make sure the center of the circle is at 0,0.  Example of a railing created by this method:



  6. The new system for hiding wall components (low / medium / high detail) is a big step backwards, unless I don't understand something.  With low detail, much of my door and window graphics disappear along with the components!  Bad.  Is there any way I can just turn off wall components like we used to be able to do?

  7. In the past, I have created hybrid symbols by converting the 2d objects to a symbol, then creating the 3d version in the 2d edit space.  Then the different modes automatically separate themselves.  With v2020, I can no longer do that.  As soon as I create a 3d object in the 2d edit space, it disappears.  I can no longer put together a 3d object from parts, add and subtract them, then exit the 2d space.  Nor can I add to a 3d object it its edit space, since every time I create a 2d object for an extrude it disappears.  Very disappointing lack of understanding on the part of VW engineers regarding our typical workflows.  Or am I missing something?


    And now we have the highly complex "component" system for hybrid objects.  Not worth the time to get into that, in my opinion.  Is there any way to opt out of that?

  8. After consulting with tech support and doing a lot of testing, it seems like this is a combination of font, object fill, and GDI+imaging.


    What the image shows is my preferred font (Tekton Pro, which is an .otf font) superimposed on Arial, which is a default font that appears when Tekton won't display properly.    There has been a problem for several years with GDI and Tekton, and I've heard, all .otf fonts.  Turn on GDI, and Tekton is rendered as Arial.  Why both of them appear in this circumstance is a mystery, but there it is.


    The fix is to create the animation with "None" class set to solid fill.  For some reason, the problem doesn't occur with those settings.


    To add to the confusion, the fix does not work in my file, which was converted from vw2017 to vw2020.  So for this file I am changing my default font to a non-.otf font for solar animations.

    • Like 2

  9. The good news so far:  they fixed the problem with 2d object type preferences changing when editing a Sheet Layer viewport crop!  The bad news:  many more crashes, pretty unstable for a SP3.  A bit slower than the version I have been using for a while, 2017.  Not driving me crazy, but I will update this post as I go along.

  10. Anyone have a solution to doubled text in a solar animation time-title?  Looks like this:


    It looks like the text is casting a shadow., but there is no object actually below the left 80% of the text.


    BTW, I attempted to search for community posts on the topic "Heliodyne AND 2020 AND solar animation."  It returned something like 180,000 items.  Someone needs to fix the search engine on this board!

  11. I haven't downloaded versions of VW that I have purchased since 2017.  Can someone tell me from experience whether the window PIO has been improved since 2017?  For example, when we create a casement window in 2017 (and previous versions), the sash is placed at the center of the jamb.  No casement window in the world is built that way.  Just one example out of dozens of shortcomings.  Any joy in 2020?

  12. 1 hour ago, Kevin McAllister said:

    There's definitely room to improve the current snapping system.


    Glad you agree!  You may recall a thread a while back where users tackled the question of how to draw an arc tangent to given points on two circles.  We found a solution and proof to that problem, and though we can construct such an arc using techniques similar to how you typically draw tangent lines, it escapes me why these basic calculations can't be reliably incorporated into VW tools.  BTW, although I find that the problem that started this thread does not exist for me in v2017, Mike has found that it does.  So something a bit arcane is going on.

    • Like 1

  13. On 1/2/2020 at 5:23 PM, Kevin McAllister said:

    I've never found tangent snaps in VW very reliable. I tend to draw a known tangent and rotate it around the circle to where I need it. I also wish there was a way for the second click to be the tangent point on the circle (eg. from a point on another object to the tangent point on a circle).

    Kevin, do you really think this is acceptable?  Tangency geometry is pretty straightforward, you could construct a bulletproof algorithm in less than an hour.  I just think there is some careless engineering going on.

  14. In the version I'm currently using (2017), tangents behave properly with respect to being 90d from the corresponding radius line.  The only odd thing is that when snapping to the end point of a horizontal line, the tangency sometimes flips 180, and I have to use the <alt> key to get it to snap to a point on the other side of the circle.  Maybe something was fixed incorrectly between then & now?


    By the way, the reason I haven't installed my 2020 version is that I keep hearing about problems with v2020, and no fixes to longstanding problems or deficiencies that make it worth the effort to switch.  I'm pretty sure I'm dropping out of Service Select and upgrades this year.  Any advice to the contrary would be appreciated!


    VW v2017 SP5

    Win 7 x64

  15. It's time to let us know what version you are using.


    To select an object after first selecting the tool, hold down the "Alt" key and click on the object.  It is more efficient to just get used to the VW way of selecting objects first, then choose your operation.  To just move the object, change the settings in the "Move by Points" tool the way I previously suggested (see graphic above).  Those settings will stick unless you change them.


    You should not be duplicating the object unless you want to use the "Move" command (see below).  To use the "Move by Points" tool to both move and duplicate with the settings I have suggested, hold down the "Ctrl" key (or Mac equivalent) while making your two clicks, and it will temporarily override your settings from "move without retaining" the original object to "move and duplicate" (retain original object).


    You can get rid of offsets when duplicating by editing VW Preferences (Edit tab) and unclick "Offset duplications".


    "Tools" are in set in boxes, usually on the left.  "Commands" are from dropdown menus on the top bar.  There is a "Move" command that brings up this dialog box:



    PS:  to increase your speed, get used to using keyboard commands.  That is the next stage in your development.  Most veteran ACAD users use keyboard commands, ACAD used to be a command-line program before they started using visual icons to select operations.

    • Like 2

  16. To simplify:  change the settings (in the top bar on the left) to "Move mode," Object retention off, 1 duplicate:


    Then click on two points on the screen and the object will move by the distance and direction (vector) defined by those points.  That's exactly what ACAD move by points does.  Using the data box is not doing a move by points.  Selecting 2 points is a move by points, the first of which can be on the object if you so choose.  Is it possible you are stuck on the Move command, which is different from the Move by Points tool (see my previous post)?

  17. I don't know what version of VW you are working with, but since several years ago VW implemented the move-by-points tool.  It's in the Basic Toolbox, and looks like the highlighted icon:



    It works just like ACAD, in that you can select an object, then select the tool and click on any two points anywhere to define a move.  There are lots of options, so check those out (number of copies, keep original object or delete, distribute across the vector or repeat the vector for each copy).

  18. Well, cheeselog, I'm wondering about your handle.  It's hard to wrap my head around that.


    To answer your questions:  the first effect you are seeing is pre-selection highlighting.  It tells you what object you are about to select if you left-click.  You can turn that off in Vectorworks Preferences dialog box (Interactive tab), and there you can also find a link to the detailed settings for highlighting colors & effects.  When you select an object, the highlighting CAN be different if you have selected something different in the Interactive Appearance Settings dialog.  I have set my preferences to not show pre-selection highlighting, and things are only highlighted if selected.  You should also see little blue squares at key points on an object when it is selected - those are points you can grab to reshape an object.  Also, pay attention to the actual shape of the cursor.  It is an arrow when you are not "within range" to select any object, a white triangle when you are within range (a left-click will select), and a cross symbol when you are within snap radius of a smart-cursor point (like an endpoint, for example).  You can also set your snapping "sensitivity" in Vectorworks Preferences Interactive tab by chosing the appropriate selection box and snap box sizes - it's intuitive, play around with it.


    If you are used to AutoCAD selection, try to wipe that out of your mind.  Marquees will not select an object in VW unless it is totally encompassed within the marquee.  (Unless you hold down the "Alt" key).

  19. Thanks Will for that heads up on the viewport text scaling.  That seems counterproductive.  Why take a feature that was supposed to deal with having a VP at a different scale from the layer, and make it solve a problem that didn't exist with text in the VP annotation space?  Is this what I am hearing?  Depressing.


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