Jump to content

Travis

Member
  • Posts

    808
  • Joined

  • Last visited

Everything posted by Travis

  1. Ride, Set the double-line tool to one of your specified widths (say 80mm) and to create polygon (NOT lines). Draw a door frame. You now have a polygon with both inside and outside lines. When you double-click the polygon, you'll get the 2D Reshape tool. Click outside the polygon and draw a marquee/box around one end of the door frame. All of the vertices inside the marquee will now move together. Either drag (visually) or enter the distance to change the "length" of the door frame. All this without altering the 80mm offset between inside and outside lines. A similar approach can be taken with your face frames: you'll just have to do some Add Surface steps to get a single polygon. One key paradigm to conquering VW is to think in terms of objects rather than lines. Good luck,
  2. Gilly, et al, Depending on what you're trying to do, you can change the letter spacing by converting TrueType to polys. Then group the wording, enter the group and adjust spacing, etc, as needed. It's just very inefficient, especially compared to AI. But, it you're trying to lay out a sign panel or something that has relatively few letters, it works well. Good luck,
  3. It seems that one doesn't actually have a video card option. The card you mention is only available with the fastest processor on the largest screen available for the iMac. I'd be inclined to make the choice based on those other two features, and let the video take care of itself. We always buy the fastest processor and at least 2gb (better yet, 4gb) of memory that the budget will allow. In the case of the iMac, spending the extra $300 (however many pounds Sterling that is) for the faster processor will almost certainly be returned many times over in improved productivity. Good luck,
  4. We have a whole set of Detail- classes that are used only for details. (e.g. Detail-Conc-ReBar; Detail-Conc-Section; etc.) This way, whenever details are WGR'd in, there's no conflict with other classes. Also, Hatches can be customized for detail-sized use. Just be sure to use unique Hatch names, as well. Since the broken-link WGR layers are already on their own design layer, we would generally finish the annotations there. This, however, is the only time we annotate on DLs. And there are at least two benefits: 1) If a detail is modified enough to warrant adding back into the library file, all of the relevant info is in one place; and 2) on larger projects, when multiple individuals are working together, one draftsman can be compiling the details ? on DLs ? which can then be WGR'd into the master "print set" file. Finally, the DL-based details are VP'd onto sheets. Scale and cropping is adjusted, if required (we're kind of partial to neat rows and columns of more-or-less uniformly-sized details on a sheet). Good luck,
  5. We keep a library of details filed by type: meaning there is one file for footing/foundation details, another for exterior, yet another for doors and windows, etc. Each detail is drawn on its own design layer at about the scale we would expect to use it. Then, as a drawing set is developed, these detail layers are Work Group Referenced (WGR) "in". The link is then broken so the detail can be customized to fit the situation AND so future changes to the library aren't referenced back to "old" drawings. Generally, as details are developed for new situations, they are added to the appropriate library file. HTH,
  6. tguy, I thought my leading statement "need to show a building section" would have implied a "section created for purposes of display". My apologies if that was unclear. If all one needs is a quick measurement, it can be got directly from the model layer by switching to an elevation view. If the model is complex and a measurement is needed somewhere in the "middle", one could certainly use the old Cut Section tool. But don't forget to count the "delete" step, if it's only a temporary item. boxjoint, In the VW application folder go to Plug-Ins>VW_Arch>Data and open Lumber Sizes.txt. Under Units\Actual\Nominal, change the actual to 1.01", 2.01", etc. (Since we frequently use 3x material, we've even added a full line that reads 3.01"/3") Then scroll down and update Length increments (Imperial) to 24.01" It seems the nominal calculation in the PIO is set to round at the numbers in the "Actual" column. We want 2" to NOT round up, since we frequently work in full-dimension timber. And, since milled lumber typically comes slightly longer than specified dimension, we would rather not have a 12'-length rounded up to 14'. By "upping" the rounding point to .01" beyond, we now get the expected Nominal dimension. Which we then flow to a materials list. I realize the above looks only to Imperial measurements, but the logic works just as well for Metric. If something's not clear, please repost. Good luck,
  7. brudgers, Rather than retyping everything, you might be able to remap the corrupted font to a working font. Could save hours!! Good luck,
  8. ccw, We use the VW framing tools every day, so I'm hoping I might help. First of all, what are you trying to accomplish? If you need to show a building section, with the rafter length dimensioned, you can use tguy's approach. But creating a Section Viewport will get you there quicker and it will be "dynamic" (if the model changes for any reason, so will the Section). Then, in Viewport Annotations, apply whatever dimensions you need. If you want a framing materials or cut list, you'll need to get fairly familiar with VW's reporting capabilities. But be assured, you can present an accurate list on your plans. I'd encourage you to search these discussion boards for excellent pointers; use the Create Reports menu item; and post here with more questions. If you want to insert a Call-out note, say on a roof framing plan, with the rafter's actual length (not the span length, or even the nominal length) originally mentioned, you'll either have to "do the math" or go to an elevation view to get an accurate measurement. However, I can't think of a time when we would have used this approach. As you've already noticed, while the OIP (Object Info Pallet) gives you some useful feedback, it doesn't show the actual cut length. But the nominal length (rounded up to the next 2'-increment, on the Imperial system) may be what you'd want anyway; especially if you're trying to create a materials list. If you'd like to correct the Nominal Size problem that Ray observes, please repost and I can walk you through that process. Ray: It's a simple data table problem that has never been resolved in any shipping version of VW, yet. I've given up complaining: we just replace the data table with each new issue. Good luck,
  9. Bruce, You can, however, cut & paste from one file to the other. I realize this is somewhat tedious, but it may be faster than re-drawing/re-writing whatever you're needing to bring forward. Good luck,
  10. Do you have Quartz imaging turned on? (Preferences>Display tab) This may render the font more accurately. TrueType and OpenType fonts include the PostScript info, and a whole lot more. We don't use any solely PostScript fonts (either Type I or III), but rather all TrueType. I do know that VW is more sensitive to font-type and possible corruption than, say MS Word. In fact, I could (but won't) send you a "free" font someone once downloaded that crashed VW every single time it was used. The net result of my ramble is this: unless absolutely necessary (and be prepared for unpredictable results), always use genuine TrueType or OpenType fonts. At the risk of being redundant: if the font didn't come with your OS, or you didn't buy it, don't count on the results. Good luck,
  11. Raida, Please provide info about the platform on which you're running VW: OS & version; hardware specs; printer Since VW utilizes only fonts loaded into your system, there are several points along the way where your problem could be based. Good luck,
  12. Islandmon. . .you're so very punny. But it's a little early for Halloween, don't you think?!
  13. Craig obviously has had a different experience, but I used MacDraft for a couple of years before evolving into MiniCad/VW. It was eventually very limiting, but it seemed to me to do a pretty good job of letting me draw on the screen like I would on a drafting table. It was precise and very straightforward from screen to paper. It's been more than ten years since I used it, but their website makes it seem very familiar. So it must still work with a similar paradigm. I do like g2g's idea tho, unless license cost dictates another choice. Good luck,
  14. CS1, You may very well have your grid set to invisible and/or to some fairly small increments. Especially if the grid is small, any movement to align the object will be almost imperceptible. HTH
  15. Transparency can also be assigned by Class. Check your class setting to see if you have transparency set to something other than 100%. Good luck,
  16. Brooke, It's a little unclear exactly what a "masking entity" is. If what you're referring to is a viewport crop, you "engage" them by entering the VP Crop mode. . .NOT the Annotations mode. When in the Crop mode, you'll only be able to select/edit the cropping shape. HTH
  17. Brooke, Check your "global" class settings (Navigation pallet). It sounds like you've got the class(es) turned on for the VP, but you don't have some critical class(es) active overall. HTH
  18. TrueType font technology is adapted by both MacOS and Windows. While Univers is a fairly common font, it doesn't ship as part of the Mac's system fonts. I'm unsure whether Windows will allow you to "export" a font from it's system files, but you can in Mac: you'd place a copy of the font in a separate folder or on the desktop and then copy to the other computer via network or some kind of storage device. Failing this, try Adobe's or ITC's website and buy a copy of the font. Good luck,
  19. Visard, Your concern has been discussed a number of times, especially in the last year. Please see this thread for a place to start. There are a number of ways to get what you want, but (as Robert points out) it's useful to note VW's paradigm: hatches are 2D and textures are 3D. It's not terribly difficult to create a texture from a hatch. If the above (and whatever searches you do) leaves you with more questions, don't hesitate to post again. Good luck,
  20. VW is rather fussy about fonts, at least in part because VW incorporates technology from several sources (the OS, Adobe, etc.) to create the final product. If they're not genuine TrueType fonts, they don't seem to play well with others. Our standard is this: if we didn't PAY for the font (and then usually only from Adobe, ITC, or Lino) or it wasn't included with the OS, we don't use it. Downloading fonts, especially "free" ones, is absolute vorboten. Beyond that, a little more info about the system(s) you're running might be helpful. Good luck,
  21. You're correct, the Repetitive Unit tool creates 2D elements only. Most, though not all, of the tools on the (default) Detailing tab are "2D only" with the likely intent they will be used in Viewport (VP) Annotations. I generally draw decks using Floors set to the decking material's thickness and then apply a hatch to represent the deck's orientation. If I need to show a section through the deck, I'll use the Repetitive Unit in the VP to add detail. Occasionally, I've tried truly modeling a wood deck by extruding an individual plank, making it a symbol, and then duplicating it as req'd. It hasn't seemed worthwhile. . .especially when the client wants to change the shape of the deck! Good luck,
  22. David, Have a look at this thread and maybe do a search for more threads, especially re Linux. It gets discussed at least a couple times each year. Good luck,
  23. Brendan, See this thread, especially Mike's final post. And keep asking questions here. We'll all try to help where we can. Good luck, PS: For future questions, it would be well for you to include your OS & version, hardware, and VW version. You can create a signature line that includes all this.
  24. Christiaan, it seems your second query is also answered by Jeffrey's post. The accessible RAM is controlled by the OS more than by the app itself. I can verify that on our 4+gb machines, it appears that never more than 2.5?2.8 is allocated to a single application. We don't, however, use Artlantis. Do they somehow bypass the OS limitations? HTH,
  25. I think Pat means versions prior to 12.5.3 . . . Version 12.5.3 will run under Leopard (we currently have that setup) as will VW2008. Good luck,
×
×
  • Create New...