Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Travis

  1. Thanks, Pat, for weighing in. No, I'm running current hard- and software. Just been a minute since I updated my profile. We've never been able to track the core problem(s) down. Luckily, I'd shared my workspace with a colleague who'd done only minor modications. I had her send me a copy which works as expected. Solved my problem and I'm back in business. Now for the weird part: when I sent her the 'broken' workspace from my system, it works fine on hers. When she sends it back, it's still broken on mine. (yes, we renamed the file each time so we could keep track of it) Maybe somethings are better left a mystery?
  2. Tried all three suggestions and still no joy in 'my' workspace. If I switch to another workspace such as the default Architect, all the pallets work as expected but I'm (nearly) lost otherwise because things/menus/etc aren't where I'm accustomed. I originally customized from one of the default workspaces, but it was probably back in v8 or something. I've modified it to suit my workflow gradually since and hoping to not have to start over. Of course 😉
  3. Suddenly, in my preferred workspace, the OIP has not only disappeared but the menu selection has also gone gray. Perhaps I've accidentally typed some key combination? Help!
  4. I'm running VW20. I duplicate the Framing Take-Off worksheet in the RM, rename it, then bring an image of the duplicated copy right onto the Design Layer (for now). See that it's still counting a 2x10 from the Framing Layer AND all the decking from this layer. I open the Database Criteria and see that it's set to the DeckSurface layer but still counting framing from the Structure layer. (other than the one 2x10, the Structure layer is empty) I click More Choices and further restrict the criteria to Framing Members. Then click OK which closes the Criteria window. I then select Edit-Recalculate Active Worksheet and... nothing changes. I reopen the Database Criteria window to discover the parameters have reverted back to where I started. I'm obviously missing something!
  5. I have a very simple take-off worksheet that counts the number of Framing Member items on a specific design layer. I duplicate the worksheet, rename it, then go into the database criteria to change the Layer to a new design layer. However, the change doesn't seem to stick: the new worksheet still counts the items from the original design layer. If I want to save changes in a spreadsheet cell, I click the green checkmark. Is there something similar I'm missing that triggers a 'save' in the database criteria window?
  6. Did anyone perhaps find a solution to Jeff's 'bug'? I've just had the same thing happen to me. Once it happens in a file, I find it sticks and haven't found a way to drag it to unstuck! I open another file, even during the same session, and fillets/chamfers work. But not on the stuck file. It seems likely there's a setting (did I mistakenly press the wrong combination of keys?) that can be triggered to lock all extrudes. Any help would be wonderful!
  7. Peter, I very much want to do exactly what you describe: have two textures with the wood grain at 90° to each other. I can duplicate a RW texture, but don't see how to rotate the orientation. Help?
  8. I hadn't explored the menu quite deeply enough. I had to turn on the dual plane option so the menu gave me both choices. Thanks for your reply.
  9. How do I change the default Plane for new 2D elements drawn in 3D views? On the Object Info pallet the Plane menu allows (generally) for both 3D and Screen. Surely there's a way to toggle the default so one doesn't have to make the change on the pallet for every new element. I suspect this is fairly simple, but it's eluding me today!
  10. I can confirm that VW2015 runs fine on OS High Sierra (10.12.6). I don't have a copy of VW2014 to test. My copy, however, is not available.
  11. Thanks, both. Yes, VW is quitting normally/successfully. I tried dragging the preferences file out onto the desktop, launched VW (same 2/3 window), resized the window to take up 95% of the screen; quit; relaunched: same 2/3-sized window. (things that make you scratch your head and say choice words) I'll try tech support. Oddly, when I launched VW18 the first time it opened a full-screen window. I thought, 'Great. Problem solved.' Then, I converted a couple files forward from VW17 and the 2/3-glitch came with. To stay. :\
  12. About half way through this year, my default drawing window—regardless what file I open, even creating a new document—is about 2/3 wide across my screen rather than full size. So, I grab the bottom right corner and drag it across and go to work. It's driving me crazy, mostly because it hasn't always been like this. I'm sure I've 'stored' some kind of default somewhere, but I'll be switched if I can figure out where. Perhaps in my custom workspace? If so, I can't seem to figure how to set it back. Any help much appreciated!
  13. Peter sometimes has all the good ideas.
  14. Hmm. Of course NNA is in business to generate revenue for its ongoing success. But with three service packs released for v2008, I don't see how you can say they've ignored bugs. That's not to say they address all known bugs, but who does (or could)? No software house I know of maintains more than (perhaps) one release prior to the current one. Additionally, it seems reasonable to this non-programmer that the best way to address some perceived "bugs" is to evolve through, or even pass, them. For example, there have been "bugs" for years in the some of the more arcane geometry of both 2D and 3D elements. I have been particularly frustrated by the inability to "snap" to 3D midpoints when working in wireframe. Is this a "bug" because I can snap in another program but not in VW? For both of these issues, it seems the best answer might have been switching to the Parasolid kernal. Does this mean NNA doesn't care about them in the prior version? Of course not. Rather, I see it as caring a great deal: they not only solved my gripes but did so by giving me more than I could have known was possible. As to your other issue re the value of each upgrade, it seems to me you'll have to arrive at a conclusion based on your circumstances. I simply wouldn't be willing to buy a new car just because they changed the shape of the fenders and moved the headlights a bit. Truthfully, the workstation productivity increases in each of the last four VW versions have easily paid for the upgrade cost in the first two or three weeks. If you're billing $100 per hour and can be more productive by one hour per week, the re-coup rate is just over a month. We usually (and will this time) make the upgrade switch in Dec/Jan during our slower season: we can watch these boards for tips from early adopters, we usually start with at least the first or second service pack already in place, and we have more time to adapt all the "bring forward" items (workspaces, templates, symbol libraries, other work-flow-related stuff) when we're not quite so buried trying to keep clients happy. With NNA's recent (last two years?) change to a reliable, annual upgrade cycle, we're able to budget both time and money to review and then adopt (if appropriate) their offering. Makes a lot of sense, even for our small (4 seats) shop. Do what works best for your business
  15. OK, my friend, it's finally confirmed: you have too much time on your hands! Nice dose of humor. I'm not sure I want to supply all our clients with ready-made skeletons. Most of them already have several in the closet! Good day!
  16. I can see it on screen, but printing (even to PDF) yields No Joy. Was able to print it from another computer in our office. Maybe I'm missing something from the install. Will do a clean install over the weekend and hope. Thanks,
  17. I've imported another architect's sheet (in PDF format) onto it's own design layer and then viewported it onto a sheet layer for output with other viewports overlaid. For some reason, the PDF layer doesn't print. Is anyone else having this problem? And maybe learned a trick I can't seem to discover yet? Thanks in advance,
  18. Super, When using walls, be sure to just move one wall AND make certain the Wall Join option is turned on at the top of your drawing window. If a square were drawn with the Wall tool and I wanted a rectangle, I would just grab the center handle of a single wall and drag it. The two adjoining walls will "stretch" right along with the wall being moved. If you find a corner that's come apart, just use the Wall Join tool to "heal" the corner. (Make sure it's set to the correct option: "L" or "T" joint.) Good luck,
  19. 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,
  20. 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,
  21. 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,
  22. 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,
  23. 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,
  • Create New...