Jump to content

P Retondo

  • Content Count

  • Joined

  • Last visited

Everything posted by P Retondo

  1. 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?
  2. 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.
  3. 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.
  4. 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
  5. Use the "Wall End Cap" tool:
  6. Let me add, multi-track sliding doors with lapping stiles. This standard door type has been available for more than 30 years. As far as I know, not possible with VW2017 (I have later versions, but never use them because there is no incentive to do so).
  7. This is what happens when software engineers try to do the job of the designer and drafter. Let us do that, provide tools but not tools that are laden with assumptions and stumbling blocks.
  8. Juan, please be prepared for a lot of feedback. The issue with glitches of this type is not a lack of tech support, it is a lack of attention to software engineering to correct longstanding (I'm talking about 5 years plus) issues and bugs that folks have been complaining about to no avail forever. Be advised that willofmaine is one smart guy!
  9. 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.
  10. 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)?
  11. 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).
  12. 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).
  13. 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.
  14. The annual subscription (service select) was supposed to have shifted some of the engineering effort from flashbang new features to fixing all the problems longtime users have experienced. I and others have been paying for years for unusable product. My current work is in 2017, despite owning multiple 2018 and 19 licenses. So, NNA, how about delivering a 2020 version that will cause users to come here with rave reviews for stability, bug fixes and speed? Or is the problem upper management not getting it? When VW was run by R Diehl at least we knew an adept engineer was at the top.
  15. I have never figured out a solution except to convert to lines and delete the overlapping lines.
  16. Just to be clear about what I have said, I think this thread and Jim's comments are an extremely constructive response - not at all an attempt at deflection or obfuscation, rhetorical or otherwise. If you have ever worked on a software project (I have), you will know that testing is probably the most important part of the process. In that regard, developing some benchmark tools, which run the software through a series of speed tests, would be extremely important to be able to know whether the code as written is helping or hindering the specific goal of optimizing the speed of operations. Making the result of benchmark testing available to users, compared across versions, is what both Jim and I would like to see. Not as a way of solving every user's particular problems, but as a way of knowing in general whether a new version of the program is improving performance, or not. Just as getting a faster processor may not solve someone's issue, having a version that benchmarks better may not solve every issue, but it will at the least tell us whether a performance problem is due to a basic software design issue.
  17. For what it is worth, I'm a strong advocate of NOT being constrained by a software engineer's vision of what I should be designing. Tools that guide the process, or make certain results more efficient to achieve have the potential to seriously crimp creative freedom. BTW, yes, a serious distraction from the topic at hand, which is benchmarking! On that topic: the tests that occur to me as being key are 1) OpenGL 3d navigation, 2) Final Renderworks, 3) operations in sheet layer viewports (which have been subject to slow performance in the past), 4) site model updates, 5) undo certain operations (such as convert polygons to lines), 6) applying linetypes (much slower now than it used to be), 7) populating the resource palette, 8) booting.
  18. Jim, thanks for the thoughtful response. Obviously, specific dysfunctionality of certain files and workflows are not going to be a good subject for benchmarking. But that doesn't mean benchmarking is useless. On the contrary, having some set of reasonable tests for various aspects of VW (rendering, certain 2d operations, certain sheet layer tasks) would be just enormously helpful, so that we can compare speeds - let's say, going back to VW15 - and get an idea of what we are in for if we upgrade. The other issue you mention is that this would have to be done on different machines, let's say three or four generic representatives of the kinds of machines your users tend to have. It's not an end-all-be-all, but head and shoulders above the information desert we currently face. I tend to think that almost any simplifying decision about files, testing categories, and machine types made by you and your team would be enthusiastically welcomed.
  19. Melanie, if you are reading this, the topic is not closed. I sympathize with your problem, and don't have much to offer since I am sticking with v2017, despite owning three v2018 licenses and two v2019 licenses. Jim, VW needs to deal head on with these speed and efficiency perceptions / reality (?) by instituting performance testing and releasing the data. When I buy a processor I look at all the available data, and it is both voluminous and convincing. CAD programs need to do the same thing - if for no other reason than to let their engineers know whether they are doing a good job. When I make the time-consuming commitment to convert my files and resources to a new version, I want to know if my performance is going to be at least equal to the previous version. That's just a simple business decision, and I don't base those on sales department press releases. Processing is ever more heavy, and Melanie I would be interested to know about your video card and it's RAM cache. 16 GB RAM on your computer is not as big as I would target for a new computer - I'd be looking at 32 or 64, minimum.
  20. I've always wondered the same thing. It doesn't do anything I can detect.
  21. Those of us who have worked with VW for a long time have developed systems and workflows that depend on screen plane objects. You may work a different way, but bear in mind that others may not. For my part, I have no use at all for layer plane objects. As you point out, the power of screen plane objects is that they can be copied into a different view and used as geometry to inform design - transferring geometry from plan to section, for example. Think of it like having a layer of trace over your 3d view. If all your plan geometry is layer plane, you can't use it this way.
  22. Yes, I might even start using 2019 if this is fixed!
  23. After much experimentation, what has worked for me for many years is to set the stylus range on my large tablet to a smaller rectangle, about 5-6 inches diagonal. This is comfortable and very workable.
  24. It would be great if we could designate a unit type to each dimension object individually. I run into the problem where some of our site drawings have to be in decimal feet, and the rest of the drawings in feet/inches. As it stands now, changing the units preference changes everything globally, so I have to set up a separate file just for those sheets and viewports that need to be in decimal feet.


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