Jump to content

P Retondo

Member
  • Content Count

    1,801
  • Joined

  • Last visited

Everything posted by P Retondo

  1. 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.
  2. 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.
  3. Jeff, not quite sure I understand your question. (0,0,0) will be the same in both files.
  4. 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.
  5. 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.
  6. 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.
  7. mm, check out this discussion for a work-around: http://techboard.nemetschek.net/ubbthreads/ubbthreads.php?ubb=showflat&Number=80336&page=1#Post80336
  8. Jonathan, didn't know you could edit attributes for multiple classes at once. Brilliant! Thanks, this makes it a piece of cake.
  9. Peter, your desire to control the "standard" gray is a good idea. Short of being able to do that, since it is not now possible, you can resort to the following procedure. It's tedious, but can be replicated once done: create an overlapping viewport. In that viewport, with the desired layers visible, override all the visible class pen colors with the gray you desire. It's tedious because you have to edit classes individually. If you have someone who can create Vector Scripts, I would think this chore could be automated.
  10. Bruce, try converting your curved walls to NURBS surfaces first. I don't know how this will be treated by the IGS translator, but it's worth a try.
  11. Don, you probably feel the way I felt that last two or three times I had someone on this board point me to that same solution!
  12. Don, double check your class view settings. When you are looking at the model layer, you may have certain classes turned "invisible" which will supress their display.
  13. Convert polylines to arcs and lines, etc., using the "Decompose" command. Polygons, by contrast, are by definition composed only of line segments and will only yield line segments, unless you redraft in the manner you describe. If you convert a polyline to a polygon, you've lost all the curvature information. I think your suggestion about making the selection handles for objects fit the "smallest rectangle," which in many cases would be rotated, is a very interesting one.
  14. Islandmon, thanks for the insight. I stepped through my movie, and I could clearly identify the key frames. Unfortunately, the frame shown above is one of them! Maybe size is one of the factors affecting my situation. I zoomed out to reduce the overall size of the view, because I find that it creates the animations faster with smaller file size. I would have been willing to accept the on-screen resolution I was seeing from the rendered view, but it seems my expectations were a little high. I'll try to keep the factors you point out in mind as I do some more experimentation.
  15. Don, not quite sure what you are saying. The correct way to construct a model is to establish a model layer, then in that layer create Layer Links of all the appropriate design layers containing 3d objects. The layers linked can be native to the file, or can be WGR layers. Once you have assembled the model in this way, including any lighting desired, position a view that is to your liking and create a Viewport on a sheet layer. The viewport is then looking at your single model layer containing all the Layer Links. From the viewport you can adjust the exact perspective, but I find it easier to adjust the perspective in the model layer itself, using the various viewing tools.
  16. Nicholas and Jonathan, thanks, I'll try all those suggestions!
  17. Don, what he means is that Layer Links are not supported by a WGR, so any layer referenced into the "master" file will not contain any layer links. Since "model" layers in the referenced file are constructed using Layer Links, those layers will basically be empty in the master file. You have to go back to basics by referencing your actual Design Layers, or the layers that the objects were constructed in, and then gathering them into a new Model Layer in your "master" document by creating Layer Links. PS: I'm not sure, but I think that Islandmon is using "master" and "subordinate" in the reverse sense of your original post; I'm using the terms as I think you are - i.e., the file that contains the references is the "master" and the files in which the "pieces" are created are the "referenced" files. I actually think something like "container file" and "contributor files" might be more intuitive.
  18. You can see textures in Section Viewports, but they are applied in orientations that can be bizarrely different from what you see in an elevation.
  19. My Renderworks QT animations are not giving me the image quality I had hoped for. I'm using the "Video" compression type at "best" quality. The range of colors, pixel size, and aliasing don't come close to what I see on screen (72 dpi, presumably) with a static Renderworks display. Does anyone know whether any of the other QT options can offer better quality? The following image shows a frame captured from the video (which is considerably sharper than what the QT player is showing on screen at the same size!!), compared to a jpeg created directly from the VW rendering. The comparison does show the color banding and lack of shadow gradation in the video as opposed to the jpeg image. BTW, the file size of the VW jpeg times the number of movie frames is approximately equal to the video file size. The fact that the video player displays much greater aliasing and lack of edge resolution than it's own still frame capture suggests that the quality of the video display itself is a factor. Does anyone have any advice about that issue?
  20. Christiaan, I'd agree that this is a bug. Any such string that starts with the zero digit should be handled as a text string instead of as a number.
  21. AutoCAD content can definitely mess with things. I have a symbol that won't display its handles, which came from an AutoCAD drawing made for a plumbing manufacturer (why are all these AutoCAD drawings so poorly constructed?).
  22. I think I put this on the wishlist in the past, but I'd like to renew the desire to have the animation path captured from a realtime walkthrough. Then we could do a quick tour of a project in OpenGL, and have a RenderWorks animation created from the saved "movements."
  23. When you start the animation, your initial view should be rendered in the background behind the animation dialog box. I'm not 100% clear that you are telling us this is so. If it isn't, and the view is a wireframe instead, you will get wireframe results. BTW, it would be better if the animation module were able to deliver the rendering type as specified, regardless of how the model is rendered in the current view.
  24. JHE, a couple of things. Do you know about copying/retrieving a file using the Workgroup Reference method? Second, you never said whether the layer you are working in is a Design layer or a Sheet layer.

 

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