Jump to content

P Retondo

  • Content Count

  • Joined

  • Last visited

Everything posted by P Retondo

  1. Christiaan, I agree for the most part, but I wouldn't call it a "McMansion" phenomenon. It's more like simple standardization. I think the basic solution in that regard is to go beyond US manufacturers and get more kinds of window types into the library, and to integrate those with the PIOs. I've used windows from Sweden and Italy, as well as a fair representation of US manufacturers, and I don't think it would be far-fetched to bring more types into the fold. Plus, the PIOs could make it much easier to customize things. Regarding the stairs PIO, to my mind it's not a matter of two stories versus many - it's anything beyond a single story. The stairs PIO needs to be able to handle displaying information on more than one floor using a single object. I'm hoping we'll be able to put ideas out in the context of a focused wish-list thread pretty soon. We could probably write a small book outlining how we think intelligent parametric objects would work. Fortunately for us, it seems the engineers at NNA basically agree that the current tools are a work in progress, and are making efforts to institute some fundamental improvements.
  2. Christiaan, I note your recent accusations regarding the "McMansion market," and without suggesting I have evidence against that and without for a second disagreeing with the need to revamp the window and door PIOs, I wonder what the basis of this McMansion thing is? It's a fact that there are McMansion architects and drafting services out there, and that at least some of them use VW - nothing wrong there (I'd rather have them support VW than some other software), though I'm not particularly impressed by the architecture that results nor interested in the fast-food equivalent of design. But where is the evidence that VW is tailoring the program to that market? Frankly, I don't think there are that many "seats" in that sector. And what part does BIM play in that market? Very little to none, I would say. BIM is a creature of institutional clients.
  3. Carl, I've submitted a bug report about this. This is particularly a problem when the door threshold is lower than the wall, which occurs typically in a garage man-door, and other situations. This problem is also responsible for those false thresholds that show up in interior renderings. Robert A. has recommended raising floors by a fraction of an inch to obscure those, but one hopes that is a temporary workaround as it plays havoc with accuracy in sections. There is a workaround where one needs to drop the door below the wall. Edit the wall using 3d reshape tool to bring a portion of it down to the bottom of the door. See attached image for before-and-after results.
  4. Christiaan, I get your point about Wikis. On the ohter hand, I'd say that it would be a big step to get some focused discussion going, as Katie says she can do with the resources available to her. If it at some point it looks as though the Wiki format is needed to sharpen the focus, maybe NNA would be willing to work on that. What I envision as key (and acknowledging the oligarchy we're dealing with, i.e., Katie and her colleagues run the company!), is that NNA at some point would post what their engineers consider to be the design direction for the next generation Window & Door PIOs. Call it a kind of open engineering experiment in software design where end users could participate BEFORE everything gets locked into millions of lines of code.
  5. Jeffrey, this is excellent news and your approach is thoughtful and understandable. The bug submittal route is a very useful tool, but I think that an open dialog could be incredibly helpful as well. Christiaan, by a Wiki do you mean an online document that can be edited by anyone? So that your ideas could be modified or deleted by someone else, and no trace would be left of them? I'd rather see a series of threads, and, if NNA has the resources, a software design guide that incorporates what are perceived as the best ideas and directions, that would evolve and provoke additional thoughts and comments. For starters, I'd suggest that Windows & Doors, Worksheets, and Section Viewports would be interesting topics.
  6. Resistance is futile! Has any thought been given to the idea of nomenclature tables? In this concept each part of VW would have variables assigned to the key words that show up in dialog boxes, etc. These variables would each map to a member of a nomenclature table, and a variety of tables could be made available for various markets and standards: Germany, IFC, Australia, etc., including a user-built custom table. Thus, for the US market "Department" would be part of the US institutional nomenclature, where "Bureau" or whatever is appropriate would be the equivalent term for the UK nomenclature table. It's the verbal equivalent of a color (colour) palette. Yes, we are growing towards a more interactive/interoperative environment, but with the power of intelligent programming we can still have flexibility and customization. I know that some have complained lately about incorrect terminology in the Window PIOs. I'd be willing to bet that many of the terms are standard in one market and inappropriate in others. The nomenclature table concept gives the user the power to work around what are perceived to be inappropriate terms, while still allowing VW to promulgate its best compilation of terms appropriate to multiple markets and standards. It also makes it possible to ship VW with different options selected for different markets, making it easier for users to get up and running without fussing with arcane settings, while at the same time allowing the opportunity for fussy customization when the user is ready to pay attention to such issues.
  7. Christiaan, "Department" is one of those north american MacMansion concepts. I like your idea, particularly as it might be extended to a variety of other PIOs, like the oft-maligned "Stlye-1" . . . class names.
  8. Katie, I know everyone at NNA is super busy, and you're probably at the limit - but to implement your idea, I wonder if it would be possible to dedicate a couple of forums (fora?) on this board to specific issues, so that you could accumulate the wisdom of a variety of users and so that we could all benefit from the dialog and refinement that would generate?
  9. 256 MB RAM is going to cause you big problems. Most of that is taken up just running the system and storing the program and your document. 800 MHz is going to be frustrating as well, unless you're doing strictly 2d work with no images.
  10. The problem is that those loci (even if they are locked!) are going to disappear if changes are made in the contributor WGR file. Then VW completely rewrites the WGR layers. To get your loci to stick, you will need to create a layer link to the WRG layer in another layer resident in the container file, put the loci there, and use that layer containing the link in the VP.
  11. Bring the 4 files into a single container file via WGR, make layer links of the referenced layers that need to be rotated, and after unlocking the links move and rotate them appropriately. The referenced layers will update, and the layer links will update and maintain their rotation. Be sure to have unique layer, class and resource (including symbol) names in the four separate building files. Some of your common resources, such as textures and stock symbols, can have common names, as long as you maintain discipline so that when VW asks to update one of those you aren't writing over something you don't want changed.
  12. If you want to create a hole in a roof object, first create a rectangle or polygon that outlines the hole you want. Copy it. Then "edit" the roof object with the "Edit Group" by keying , paste your polygon in, and "Exit Group." Use a similar process to edit a roof face.
  13. My dual core uses ~100% processor for final RenderWorks. I have hyperthreading enabled.
  14. AZ, RenderWorks should be using approx. 100% processor. Other rendering modes will only use 25% (we'd like to see NNA fix that). When you look at a RW rendering in process on the screen, you should see the multiple threads at work as the rendering takes place in 3 to 4 horizontal bands at once. Your dual core is emulating 4 cores, that's why with other processes that can't hyperthread you're getting 25% performance.
  15. Nicholas, we agree - if VW can meet the needs of product designers, all the better for architects!
  16. Nicholas, as an architect I use and appreciate the window/door/wall objects. But I agree with you wholeheartedly, and many architects would also agree, that robust NURBS modeling would increase the attraction to VectorWorks. ArchiCAD doesn't have NURBS at all, nor AutoCAD ADT. And what Rhino specifically lacks is the separate 2d space that is always present in VW, no matter what the 3d view, and that allows us to construct extrudes, 3d polys and NURBS curves with precision in any orientation. Maybe Calatrava is going to use a more expensive and sophisticated program than VectorWorks, but if I were NNA my goal would be to provide a program that could meet the sculptural needs of architecture. VW already has a leg up, it's good to build on strengths, and freeform expression is the wave of the immediate future.
  17. Nicholas, Rhino is a great program - but the last time I used it I had trouble accurately creating the kind of objects I wanted because of the lack of a 2d/3d interface. I wish we could get VW 2.5D (i.e., extruded objects) combined with Rhino's NURBS power.
  18. I note that you are on version 12.5. I'm not positive, but I believe that 12.5.1 contains a fix regarding this issue, if I understand correctly what you are referring to.
  19. Good suggestions. I had a 350MB file that became 35MB after turning off "cache Viewports." The only problem is having to regenerate those viewports. I hope that at some point VW implements an incremental document save so that with adequate RAM we can deal with the larger file size.
  20. Mike, you're being too generous. AutoCAD has a couple of features, such as move and copy by vector, that VW lacks, but one simple fact puts VW way ahead in terms of productivity: it is not necessary to hit after every command. Add the 3d/2d interface that VW has mastered from very early on, and I find that my productivity in VW surpasses ACAD, which I used for 3 years, by a significant margin. Fortunately, I learned MiniCAD first and didn't have to deal with reconfiguring mental pathways. I find that most ACAD users have trouble at the conceptual level when learning VW.
  21. Jeff, not quite sure I understand your question. (0,0,0) will be the same in both files.
  22. Christiaan, I believe those lines extending into the sill are zero-thickness jambs. Like you, I think that a major overhaul of the window and door PIOs would be a tremendous boost to VW's utility and sales. I hope that NNA agree and follow through with a thorough job of polling architects in the trenches and in different regions to come up with something spectacular.
  23. Nicholas and Thom, I agree that we need a better way to control the generation of contours. Control points come to mind as a concept. It would be good, also, to come up with a more refined and interactive method for creating proposed contours.
  24. Peter, this is real simple and doesn't require you to change your class structure. Set up a Viewport on top of and registered with your "main" viewport. In that VP, activate only the LAYER you want to be your background info, i.e., your base plan. Then, in that VP only, edit ALL the visible classes to change the pen color to gray. If you have only one class, that's okay, just make that one class gray. And yes, your classes must be checked "Use at Creation" for the over-ride in VPs to work. But whether or not you are using symbols, this method will still make everything gray provided that you edit all the classes indicated as visible in the Viewport. Your individual object line thicknesses should hold (I haven't tested, but when you change an object's lineweight, you change it from "Use class" to a specific value, so editing class attributes should leave that alone). Then send your VP to the back, and your background will show all objects gray. The easiest way to create a registered Viewport is to duplicate the existing foreground VP, then edit the layers so that only the background "base plan" layer and all the appropriate classes are visible. With Jonathan's advice about simultaneous class edits, this should be almost as fast as the method you'd rather have.
  25. mm, check out this discussion for a work-around: http://techboard.nemetschek.net/ubbthreads/ubbthreads.php?ubb=showflat&Number=80336&page=1#Post80336


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