Jump to content

P Retondo

  • Posts

  • Joined

  • Last visited

Everything posted by P Retondo

  1. 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.
  2. 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."
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. Here is Will's construction to find the arc fillet in the "S" curve case.
  8. Here's a proof, no question the construction is much more intuitive than the equally-correct trig solution. The illustration is slightly different in that an arc was struck instead of copying the second circle, for clarity. Great work, Will.
  9. Will, looks brilliant, do you have a proof? Don't doubt, just interested.
  10. Jonathan, I emailed those files to you so you can see what we are talking about. The fillet tool gives a fillet of known radius, the problem is to fillet from a known point on a curve. Also tried attaching a file to this post.
  11. 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??)
  12. Here's a mathematical solution for the construction of a fillet arc given 2 arcs and an initial point of tangency. If you email me I can send you an excel spreadsheet that contains the formula https://drive.google.com/drive/folders/0B2Nv6O2xIh9xT3F6XzhiQkoyenM?ths=true If anyone cares I can supply a proof.
  13. 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. If you have a given point of tangency and not a given fillet radius, your problem is a bit more complex. Trig is required.
  14. 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.
  15. 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.
  16. 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.
  17. Makes sense. Guess I should look into Python a bit more. I'm pretty excited about Marionette, seems like a great way to become familiar with the language and to block out a procedure.
  18. Thanks for the clarification, Jim. It's too bad Python doesn't follow one of the established models. And, out of curiosity, what is the relationship between Python and Vector Script, and why two macro languages?
  19. I've just taken a quick glance of some Python code shown at the webinar on Monday, and following the presentation with a knowledge of C++ I can see the clear parallels. As a shortcut for me, could someone spell out whether Python uses C++ syntax and structure, or some other language?
  20. rDesign, this is a bug that occurs whenever you edit a crop in a viewport. You have to toggle the preference back to "Screen plane only" whenever you edit a crop. Already reported as a bug, and there may be other operations that cause this. Alan, I've been doing 3d in VW for 25 years, and I NEVER use layer plane objects. Never saw the need for them, given that we can create 3d polys that are much more versatile, except for not being able to show 2d graphical qualities. I can't foresee ever needing that. Screen objects are much more useful, given that they are aligned to the screen regardless of your point of view, and as I've pointed out before, screen plane 2d objects are part of the original unique genius of VW when it was MiniCAD.
  21. Christiaan, have you tried setting the recess cut line to a height within the recess (should be in the OIP)? Normally, you have to adjust that height to get the recess to show as a cut in the wall.
  22. Bruce, I'm not sure I understand your question, so this may not be the answer you're looking for - all doors swings can be put into the 4 potential configurations using the "Flip" button in the OIP.
  23. Will, your post is a little confusing. You say you already have hybrid (i.e., 2d/3d)auto symbols, but then you want to add 2d to them? To convert a hybrid to 2d only, just save a duplicate of the symbol and delete the 3d content.
  24. Mike, awesome! Just to be clear, MH, Mike means when you have double-clicked on the symbol and it shows up rotated in its edit space, you use a command to activate the Top/Plan view, and the symbol will rotate to it's normal orientation. Mike, it looks from the behavior of the screen as though VW is actually accomplishing this through the "rotate view" algorithm. The beauty is that you can still see other objects in normal edit space to work on the symbol in context.
  • Create New...