Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Joe-SA

  1. I was told that the built in Drawing List feature did not work with Custom Title Blocks. You can type your own search criteria into the database header row to get the title block info to load into the worksheet. Then manually link each column header to a field. I also added a boolean field to the Record Format and titled it 'On Drawing List'. The title blocks display whether or not 'true' or 'false' are in this field. I also added a class setting in order to sort different sets of sheet the way I like them instead of alphabetical. (civil, arch, elec, etc) See an image here. https://dl.dropboxusercontent.com/u/21682894/3.%20GeneralUse/VWForum%20Images/WorksheetForCustomTB.png Hope this helps. Joe Hoffner Sears Architects Grand Rapids, Michigan
  2. Custom Title Blocks that work with the Issue Manager are very tough to achieve but well worth it. You also want them to work with auto-numbering. My main source of info was the VW Help files. This explains how to set record fields with P and S prefixes to the info comes from the overall files Project and Sheet Data. Very useful. Unfortunately, however, custom title blocks do not work with the built-in tools for Drawings Lists. But if you know your way around Worksheets its easy to create a Worksheet that does the job. I actually added an 'on drawing' boolean field to the record format which allows me to set which titleblocks I want to appear in the my Worksheet drawing list. Good Luck. Joe
  3. I would disagree with this statement. When composing a construction document floor plan and the many revisions that take place throughout the process you would not be able to see your dimensions as you are editing your walls in plan. Along with editing things like center lines, section lines, door tags, notations, etc. to avoid overlapping data. You would have to make the plan revisions and then jump over to the viewport for continued editing....remembering all the areas that require your attention. Dimensions often inform the design decisions being made on the fly in design layers. I use a PLAN layer paired with a NOTES layer. All REAL objects go on PLAN while all SHEET objects associated with that plan goes on NOTES. In this way the plan can be referenced as background elsewhere in the set without bringing the notes and dimensions with it. (electrical, structural, renderings, etc) Just like there is some benefit to overlaying one plan over another there can be benefit to doing this with notes and dimensions as well. This is possible in design layers but not easily done in sheet layers. Yes, there is the pitfall of drafting beyond your sheet layer titleblock but I see that as easily corrected and minor compared to the benefits of notes and dimensions on design layers. Often times when issuing preliminary plans or small scale vignettes of a plan we will use annotations for various notes, dimensions, room names, etc. In this way the larger and evolving construction document plan is not effected by these intermediate drawings. They stand on their own. In the end, however, only the drawing title with its auto-numbering typically ends up in the final floor plan viewport. my 2 cents Joe
  4. We use the Issue Manager and my script extensively for dates and descriptions but we do not currently use the built-in Revision Data. Being nearly 100% residential we rarely see the need to track revision across a number of different sets sent out to the contractor. When we do we simply place a revision tag next to a new issue date that corresponds to our revision bubbles. We list a number if issue dates on each title block. Joe
  5. I don't think I know enough to answer this question. The Issue Manager creates the Issue Data record format and sends dates and description out to many sheets. My script merely edits the content of that record format that is attached to each title block. I'm not seeing an equivalent method to send revision data to multiple title blocks at the same time. Revision data appears to only be sheet by sheet. I don't know where this information is stored because no record format is created when you input the data through a titleblock. Oddly, the Issue Data record format is also not created when you simply add the issue date by accessing through the title block instead of through the Issue Manager. However, my script still works to change the information. Find out where the Revision Data is stored and a similar script can likely be written. I attempted to re-write my script to change info in a record format called 'Revision Data' instead of 'Issue Data' hoping it might exist but just be hiddne...but that didn't work. I didn't take the time to flush out bugs in the script, however, so it might still be possible with a couple of additional edits. Joe
  6. Here are two scripts that have been posted, one by me and one by Pat Stanford, that overcome some of the inherent problems with the Issue Manager. I think the script I wrote is what you are looking for. See these two links. Pat's script blanks out all previously input data. Best if run as a vectorscript from a script palette. Very useful when starting a new project from an old project. http://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Number=126725#Post126725 My script allows you to input the letter or number assigned to a given sheet set and revise the date and title to something different on all title blocks at the same time. Otherwise you need to edit them one sheet at a time. Good to correct typos and change an issue date at the last minute. I run the script from a menu command but it can be run from a palette as well. http://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Main=33110&Number=163089#Post163089 Joe
  7. You can also use classes to define textures or create a texture bed site modifier to drape a texture over a small portion of the overall model. However, I'm noticing that once I add a texture bed to a model it doesn't want to delete from the model even after the texture bed modifier has been deleted? Thoughts? I have a textured area I can seem to get rid of. Right now I'm thinking I might need to regenerate the model from the source data and re-apply my pad modifiers. Joe
  8. Try it with two 90 degree winders at the corners. You might even put in a single riser straight flight between them if just the two winders don't work. Joe
  9. Is this a single roof object or a collection of roof objects? I've noticed a number of issues with the Roof Object in VW2013...one of them being that Roof Objects configured as a single plane will not allow holes of any kind to be cut into them. I have no choice but to use a Roof Face in this instance. Joe
  10. Is it only in OpenGL and not in Renderworks that you can turn on the hidden line work at the same time as you generate the textured image and shadows and therefor get both of them in the same viewport without the need for multiple stacked viewports or exporting out of VW? We've used this in 3d perspective views. Makes for an interesting image when you sketch the linework on top of the textures. Haven't done much with final elevations, however. Joe
  11. We've been having the lack of memory issue ever since we started generating building section and elevation viewports from our model. We've also been experiencing some lag in the screen display regeneration. I think this is a combined problem with Vectorworks memory management and your hardware. After extensive discussions with our IT consultants our current theory is that its the amount of dedicated RAM on the graphics card. Even though my iMAC has a 3.06GHz processor and 12GB of RAM and 500GB harddrive....it only has 256MB of dedicated RAM on the graphics card and unlike macmini's the iMAC graphics card doesn't have the ability to share the system RAM so 8GB vs 12GB of RAM makes no difference. New smaller iMACs only have a base graphics card and 512MB of RAM and can't be upgraded. We didn't think that was enough. The 27" iMACs can get an upgraded graphics card and you can increase the dedicated RAM. We just ordered a couple of these that have the upgraded cards increased to 2GB of RAM. This will be 8x the graphics card processing power of my current machine. To say the least, we are hoping these upgrades solve the problem. Joe
  12. Create the Planer Surface with the Extract Tool in the Model Menu. Then apply your 2d hatch to that. Use the Attribute Mapping Tool to modify the origin. Unless its been fixed there is a bug in the Attribute Mapping Tool. If you turn it on and immediately begin to 'nudge' your hatch to a new origin it won't 'stick'. But if you manually move the origin with your cursor to a new location first and then use your 'nudge' it will stick. Hope this helps. Joe
  13. In your Render Modes settings you can up the quality. I had to do this in both the Open GL settings and the Custom Renderworks settings. For renderworks there is a specific 'Curved Geometry' quality setting. I had extruded a crown assembly along an eyebrow roof eave. In order to get a reasonable curve I had to up the quality to the point where it took 20-30 minutes to generate the rendering. Not very effective. In addition, my hidden line elevations wouldn't generate smooth. Here I had no option where I could increase the quality. I had no choice but to mask over it with 2 polygons. This is one area where some improvement is needed. (one of many, that is) Joe
  14. And while your waiting for the plan revision to finish calculating your always wondering if you are going to crash. In general, crashes are way up in VW2013 from VW2012 and a large percentage of them deal with wall revisions or wall component revisions and manipulating wall joins. Sometimes seemingly simple tasks with walls toss me out of the program. Joe
  15. There have been some complaints about the interface but we typically do the 3D hatch. Once you get the interface down it goes pretty quickly. Adjusting origin might be the biggest hassle. We choose this method even with renderworks at our disposal. Might have to give Peter's method a shot, however, because it does take a while to get to exterior elevations that are presentation to client quality when you are relying on the model to generate exterior trim, crown mouldings, etc. Joe
  16. One of my biggest complaints when comparing Roof Faces and Roof Objects. The Axis Z is an elevation that results from taking the lower outside corner of a roof face (looking in section) and extending it along the roof pitch up the slope for the length of the overhang to the point where you drew the inflection point of the slope in plan when you created the roof. Usually the face of the wall/sheathing. Depending on whether you have a double miter, vertical, or horizontal eave this point could be on the top or bottom or somewhere in the middle of the depth of the roof face. I never tried to predict it. Just adjusted the height after creation. With the Roof Object tool having bearing height and bearing inset parametric input you get much more predictable results. You might be interested in this recent thread. Joe http://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Number=181872&Searchpage=3&Main=35191&Words=shed+roof&Search=true#Post181872
  17. I've made symbols of information to be referenced into a worksheet in the first file (FileB). Then not just imported the symbol but imported as a reference into the second file (FileA). Then placed that symbol into the drawing in FileA. Now a worksheet located in File A sees and pulls in all the data that is in the referenced symbol that is still located in FileB as long as its criteria is searching inside symbols. The referenced symbol can be edited from File A and the changes can then be sent back to File B. Or the symbol can be edited in File B and the reference then updated in File A. With the fairly recently added ability to edit symbols 'in place' while seeing it in context with the surrounding objects it may no longer be very cumbersome to work with many objects scattered about a plan that are placed into a single symbol in order to facilitate the above. I haven't done this with architectural data but I have done this in order to get sheet data referenced from many different files into a single file in order to generate a single Drawing Title worksheet. Joe
  18. Just discovered a bug in the Roof Object tool. When making a Roof Object into a single plane shed roof it will no longer allow you to cut holes in it per VW2013. This worked fine in VW2012. If you take a gable roof object with a hole cut in it and then turn one eave into a gable to make a single plane shed the hole disappears. The polygon is still embedded in the roof, however. It just doesn't cut anymore. The latest SP2 update doesn't fix it. Looks like there is no longer a choice here between Roof Faces and Roof Objects. Good thing they fixed the rendering issues with Faces at least. The other issues with Roof Faces mentioned in previous posts still apply, however. Joe
  19. I've been editing my wall styles and adjusting the heights of individual wall components. I make a duplicate of my standard exterior wall style and tag for use on the second floor and then edit it so only the sheathing and siding components extend down the depth of the floor framing. I make another duplication of the base wall style and tag it for the first floor and extend the outer components down to the top of the foundation walls. Now in my building section all of the profiles of the building components come in just like it would get built. You can even blow the sections up to detail level and not have to add much to it at all. Something else you can do on the second floor is to set the wall style used for the second floor exterior walls to have the framing component and interior drywall component to NOT follow the wall peaks. Now when you extend the wall up to the roof at a gable then the stud wall stays at the plate height and also won't show up in your detail section. This way your gable wall doesn't overlap where you want a truss to go...whether you choose to model the truss or not. Saves a lot of time masking and redrafting at the detail stage. Joe
  20. I've found that if you have curves in your profile and want them to show in hidden line rendering without the facets of the curve you need to convert the polygon profile to a NURBS curve. This works well when modeling gutters and mouldings. I also take the VW columns plugin and make it a symbol and then add circular EAP's to create the base and head trim. This gives me nicely profiled columns in 3d that also need no extra linework in elevation. Joe
  21. Updating this debate with VW2013 tools...along with ideas for much needed improvements. It appears the Roof Face and the Roof Object tools have been moved a little closer together. How texture is applied to Roof Faces have been improved to match how it is applied with Roof Objects. Also, symbols for skylights, etc, can now be inserted into Roof Faces the same as Roof Objects. Key differences that remain are the inconsistent bearing height of roof faces with changes in Roof Face eave condition. Also unwanted changes in fascia height with changes in Roof Face pitch. Why such an incremental improvement to Roof Faces and not a wholesale change? Do away with the mysterious AXIS Z setting of Roof Faces and match the Bearing Height and Bearing Inset of the Roof Object tool. Bring the methods of cutting holes and shaping edges closer together by making the Roof Face method match the Roof Object method. (Right now I'm teaching employees how to cut holes in Roof Faces and Floors, Roof Objects, and Slab Objects....3 different methods for 3 very similar operations. Is this not kind of crazy?) This improvement to Roof Faces would also give overhangs a parametric control like Roof Objects instead of relying on a polygon reshape. It seems to me that rather then taking the Roof Face tool and slowly over many upgrades making it more like Roof Objects we should just add a Single Plane Roof Object tool that functions exactly like a single plane roof object I can make on my own but only after many modifications to the hips that are created automatically every time a make a new Roof Object. Give these new 'single plane roof objects' the ability to extend and join to other roof objects or other 3d geometry to match what the Roof Faces can do now. Wouldn't this be the best of both tools and converge two very different interfaces into one? On a side note, I've been experimenting on turning on the 'attics' of the Roof Objects and using them to add ceiling joists that align with the rafters created with the Framing tool. If we have the ability to do this along with the ability to toggle on gable end walls (which I have never put to practical application) then why can't we add a control for 'truss knee height' in addition to 'bearing height' with automatic toggles for turning on solid shapes representing the perimeter chords of a truss? This feature would also create a vertical solid at the high end of a shed roof where the vertical chord of mono truss would run. In this way simple building sections get a solid hatch at the ceiling plane without the creation of a separate ceiling slab. They also get solid hatch at the vertical ends of the trusses when required without additional modeling or 2d patches. Similar to the current 'attic' feature the Framer then uses these shapes to automatically generate at least the perimeter of each truss using the Framing Member PIO (simto the current method) or create a new Truss PIO that the Framer could use to fill the area defined by these solids created by the Roof Object tool. It doesn't seem like the current technology is too far away from these features. Here's hoping for VW2014. Oh, and all that with Roof Components, as well. This would probably lead to the hole cutting and edge reshaping method of Roofs to want to match that of current Slab Objects as the ultimate goal of the roof tool development. How many upgrades will be needed before we get there? Joe
  22. Can you create a wall component the depth of your panels and then create a wall recess for the seams? This is assuming the design is a series of flat panels with a Fry Reglet-like reveal. Is the surface area of the wall still available with this method? I've used a similar approach in more traditional recessed and wood trim wall panel details. This method would give you pretty good up close detail in 3D. If the up close detail isn't required and your panel grid can be made with a repetitive 2d hatch then the extract surface method might be easier. Joe
  23. I was able to DLVP them from one file to another...that is Design Layer to Design Layer...but that is where it stopped. I found no method to get them from the Design Layer in the Satellite file into the Sheet Layer. I used the DLVP for reference and manually traced over top of them with my own custom 2d mark which, in turn, I was able to bring into the SLVP. Joe
  24. We did this same customization a couple of years ago. There is some pretty good information in the HELP menus. Atari was correct...certain prefix in the record field names tell VW to get the information from the Layer data among other things. You will also need to set up a Sheet Border object that then references your custom title block symbol into it. This gives you the ability to use the Issue Manager to send data to each of your title blocks. You will no longer be able to edit your symbol to input data. The data will need to come from Issue Manager if you want to put dates or client data into all your title blocks. We repeat this process with each file, however, if you were to place a 'referenced' symbol of your title block into each of your project files it can be pulled into a Sheet Border Ojbect for each sheet. You may need to keep your project data static in the symbol instead of linked to the project data pane of the Issue manager but the auto-numbering you are trying achieve should still be possible. As a side note, I created a Sheet Border Object that did not have a border and did not have the 'center on sheet' toggle checked and used it to create a large title sheet object that contained the project title and address. It pulled in a custom symbol created for this task. This object now updates right along with the title blocks. You may want to incorporate this script I wrote which will modify your dates and notes globally after you have already used the Issue Manager to set a bunch of title blocks. http://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Number=163089#Post163089 Pat Stanford's script to Clear All Issue Data is also very useful. http://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Number=126725#Post126725 Joe
  25. I've used this method on numerous residential projects and although I have also had similar issues. When you consider the alternative for black and white construction document drawings is 2d hatching in annotations, however, I didn't find this method so horrible a process as to never use it again. I created a preset set of classes with most of the exterior material we typically use. I place all my planer objects that are on one layer in a single group for easy manipulation with the Show Groups toggle off. If later revision is more then a simple reshape of existing perimeter or openings I just re-extract it. I have noticed a bug in the Attribute Mapping tool where if you nudge immediately after selecting your object the new location won't 'stick' but if you drag the origin to a new location and then 'nudge' it will stick. For the planer object 'bleed through' bug we've done 2d hatch patches just on those elevations to fix it or we have actually classed our planer objects to another tier per elevation allowing us to turn off the backside elevation while keeping the front side on. Whenever this process does break down, 2d hatch in annotations used in conjunction with it seems to get us to what we need. I'm not defending this process and saying it is 'good', that all the suggested improvements are not valid, or saying the process isn't tedious. All true. Still - its a method I will likely use until such time as it gets replaced with a better method. Joe
  • Create New...