Jump to content

P Retondo

Member
  • Content Count

    1,704
  • Joined

  • Last visited

Posts posted by P Retondo


  1. Thanks, Nic, I think it might be v2015 vs v2016. If it's a setting, I've looked at them and can't find any answers. I also get the annoying rectangle around the dimension text, which I see you don't have. I've resisted going to 2016 despite owning the licenses because of all the reported instabilities. Jim, if you're monitoring, first priorities for me in future updates and development: reliability, speed. Everything else tends to be bells and whistles if those are not solid.


  2. Christiaan, thanks for sharing your window and door method. It works, but it's not parametric. Have you ever tried playing with Marionette or scripting to construct a parametric symbol? If I ever have a few days, I'm going to give that a try, based on your system.

    NNA would do well to look carefully at this example to see what a modern parametric window/door tool should be capable of doing. Constructing something with Python or VS is all well and good, but way too many VW elements are script-based and, hence, execute way too slowly compared to compiled core program elements.


  3. Will is absolutely right, this could be easily written into VW with something similar to "constrain to working plane." For those unfamiliar with the problem, when snapping to objects in a 3D view, 3D objects can appear to move in the "screen plane" when they are actually moving backwards or forwards as well. When I want to "move by points" in a 3D view, I construct a rectangle snapping to the two points, drag the rectangle to a white space area, and perform the move by snapping to the corners of the rectangle to be sure I'm not inadvertently changing the location of the moved object with respect to that normal axis. I would love to be able to do that simply by pressing a constraint key.


  4. I go even further than Peter - the section viewports are so far from graphically acceptable, and take so long to render, I only use them for the background information, and then only sparingly. For the actual section, I use the good old 2D section legacy tool to get geometry, and draw the section on a design layer old style. That's the only thing that really works, and it takes less time than screwing around with the section VP, and a lot less time than drawing in annotation space, which in past versions of VW at least was maddeningly slow. We tried converting the section VP to lines, then scaling up (x48, e.g.), but 2D section is just faster because of re-render slowness.


  5. MH, you have a great idea. To have maximum flexibility, it would be ideal to be able to choose units on a per viewport and per dimension basis.

    It is possible to do what you want with the following workaround involving a custom dual-dimension style:

    1. Create a dual dimension style for your document

    2. Set the dual dimension units you desire using document preferences (e.g., primary ft&in, secondary in)

    3. When you place a dimension, go to the OIP (Object Info Palette) and change the style to your dual dimension, then set the option for that dimension to "Dual view: Secondary Only" from the dropdown list. That dimension would display in inches instead of ft & inches.


  6. I'll add emphasis to that request re: education support. The single greatest drawback to using VW is the scanty base of trained users as potential employees. It's made me think more than once about switching to ACAD, the cost of training and the lack of choice in the potential employee pool is daunting.


  7. Tom, thanks very much for tracking that down. Many hours were spent dealing with this problem. It's up to VW to fix this very avoidable issue. I remember when rotated plan was being developed, and I pleaded with them to isolate the rotated plan concept to avoid this very kind of problem. To no avail. What is rotated plan? In essence, it's rotating the screen view and orienting orthogonal tools to the rotated coordinate system. If they had just focused on that instead of messing with geometry fundamentals, none of this kind of thing could have occurred.


  8. Had this issue in v2015, reported it as a bug back then, but what exactly causes the shift is still a question for me. Do what Alan says - reset all your origins to the internal origin. Once I did that thoroughly, the issue has not re-occurred. Don't give in to expedience by moving the referenced viewport to correct the problem, it just gets worse.

    Tools-> Origin -> User Origin -> "Set User Origin to Internal Origin".

    Jim, unless this is fixed it makes setting a user origin a dangerous thing to do in any file which is part of a multi-file project. I can only imagine what it would do in the new project-sharing environment. As a general comment, often-repeated and probably just as often resented by VW engineers, I would much rather have NNA spend coding time making all these basic tools rock solid than have some new (probably not really useful) trick feature. Just add some code to the function that moves the origin to prevent it's being moved without notifying the user and verifying the intent. That way, whatever obscure combination of events calls the function, it can never be executed without "authorization."

    • Like 1

  9. All good ideas so far. Navigation is sometimes an issue - like, just now, I went to the site from the link in an email notification, but had to log in. After logging in, there was no way to get back to this thread except through the browser back-button, and that page didn't know I had logged in. Just being able to navigate back when browsing using a dropdown list of "recently accessed threads" would do wonders. (Yes, I do know the browser "refresh" button forces the site to acknowledge I'm logged in.)

    The organization of the discussion groups - it's a long list, and there is a lot of crossover and confusion about which category a thread should live in. I own but don't use Spotlight, but often issues brought up by Spotlight users are relevant to Designer as a whole (for example). I think a database approach might be better, where the website manager enters keywords for each thread so the user could organize and search the site by a list of keywords. That might help with Gilbert's comment, so when a current thread shares a keyword with an older thread, it could be easily referenced.


  10. Jim, real estate appraisers have little apps that take measurements directly from a bluetooth-connected Disto EDM, and even turn 90 at each measurement to draw a crude plan. Seems like it would be both relatively easy and a huge selling point for VW to come up with a more sophisticated version of this capability. As it is, I now export measurements realtime via bluetooth to Excel, then post-collection manually translate measurements and notes to VW geometry. Even with that level of crudity, the system is about twice as productive as the old sketch / measuring tape / hand notes system, and a lot more error-free. I also take measurements with a total station, then export NEZ files to Excel -> survey stakes. Seems like that could be looked into as well, surveyors have small hand-held computers with software that translates total station measurements on the fly into CAD.


  11. Kevin, I don't even remember what version of Minicad we first had. It was the first CAD program I dealt with professionally, in the transition from hand drafting, and we jumped right into 3d immediately to model custom day care furniture.

    BTW, a lot of people don't realize that, as in the original Minicad, screen plane objects are truly 2d - they have no Z coordinate (or maybe that is faked now, who knows what is in the code!). What is especially useful about them is that they make it possible to transfer geometry from one view to another with simple copy and paste, in much the same way as we used to project sections and elevations from plans in the days of hand drafting. I think this hybrid 2d-3d design environment was part of the original unique genius of Minicad / VW, and is much undervalued by some folks who are used to straight 3d programs like Sketchup, Form Z, etc.


  12. Must be a 2016 thing. In all previous versions, a dialog box comes up when creating a symbol with a check box asking if you want to change all layer plane objects to screen plane.

    For those who aren't aware, the original VW (MiniCAD) and in versions of VW up through a few years ago, there was no "screen plane" / "layer plane" dichotomy. In fact, every 2d object was what we now call a "screen plane" object, and anyone who has the experience indicated by some signatures on this thread has long experience with using screen plane objects, even if they didn't know that's what they were! This was historically a big difference between VW and AutoCAD, where all 2d objects were actually 3d - basically, what we call "layer plane" in VW.

    I use virtually nothing but screen plane objects, even though I do a ton of work in 3d. I find it incredibly useful - think of it as a layer of trace on your screen, where you can draw and think in 2d with respect to the view on the screen. I actually think it was a mistake to embark on this "layer plane" notion, instead of enhancing the 3d objects we already had. But this is the VW we have - it would help if certain operations did not inadvertently toggle the preference for screen vs. layer plane. Every time I edit a sheet layer viewport crop, my "screen plane only" option switches to "working plane only," and I have to switch it back (this is 2015). Hopefully this bug is fixed in 2016, I'm just starting to use the new version. For anyone who doesn't know, you can choose "screen plane only", "working plane only," or "screen plane or working plane" in VW preferences / plane mode tab.

    PS: if you want to make sure moving a 3d object in a 3d view does not change location with respect to the screen normal axis, just draw a screen plane rectangle between the points you want, set it to the side, and between the corners of the rectangle. Just one of many useful screen plane object tricks.


  13. Jonathan, try it, and you'll find that it can't be done if you are given the two arcs and a starting tangent point for the fillet arc. That's because you don't know where the second tangent point is. (Take a look at the two drawings for which I supplied links - one for a desired radius but no starting point requirement - the case you've illustrated - and the second for a desired starting point where radius has to be determined.) I'm pretty sure the only way to do the second as things currently stand is to calculate the fillet radius with a formula, but if there is another way I'd love to know it!

    The situation seems ripe for a tool to be developed. There are two cases: 1) the "snowman" case we've been talking about, and for which I've posted the formula, and 2) the "S" case where your fillet curve can be concave or convex depending on the starting point. 2) can also be calculated, but I haven't done the work yet for that.

    (BTW, I haven't been able to figure out how to attach an illustration directly to a post - how do you do that??)


  14. You can construct a fillet of given radius using basic geometry. Tangent arcs have the property that the two arc centers and point of tangency are co-linear. Thus, using the centers of the two arcs you wish to join, construct arcs that are the sum of the radius + fillet radius. Their intersection is the center of your fillet arc.

    0B2Nv6O2xIh9xT3F6XzhiQkoyenM?ths=true

    If you have a given point of tangency and not a given fillet radius, your problem is a bit more complex. Trig is required.


  15. This may not be the case for you, but I use a template where the drawing labels are in a "nonprint" class, which I change to "none" when the labels are needed. Sometimes if that class is turned off I forget the labels are there. Auto-numbering, however, does not forget they are there. Having said that, from the specifics provided it does seem like you are experiencing some kind of file corruption.


  16. The only way I've been able to do this is to create a texture from the image, framed with solid boundaries, then apply it to a NURBS surface and tweak the scale and offsets. It seems like there should be an easier way, but I don't know what it is. Applying an image to a "2D object on the 3D plane" (whatever that actually means) is possible, but that would have to be based on a 2D primitive, such as a rectangle, circle, etc. I would love to know a better way to accomplish what you are talking about.

    BTW, you can convert your cylinder to a group of NURBS surfaces with a simple command, then you can isolate which surface the texture applies to.


  17. Jim, after looking into it I can see that Python, though not directly compilable, is a programming language, not a macro language. This helps me adjust my approach to following the online demos - I need to stop thinking in C++.

    Speaking of which, I asked the question, "how do we know the type of an argument" based on my knowledge of C, where variables are declared with a type, such as "Int". Now I understand that variables in Python are not declared with a type - or at least that appears to be the case from a very cursory look at things. I guess I'll figure out along the way how that works. In C, if you reference the wrong variable type when calling a function, that results in a compiler error that is explicitly called out. Not sure what happens when you plug in a real number in a Python / Marionette function that needs an integer.

 

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.

×