Jump to content

P Retondo

  • Posts

  • Joined

  • Last visited

Everything posted by P Retondo

  1. Create your layer links in a single Design Layer, not in a viewport. You actually can't create a layer link anywhere else. This is your model layer. Add lighting (in a separate layer is okay) using View -> Lighting -> Set Layer lighting and sun. Create a ground plane (usually in a "ground" layer and again linked into the model layer). Pick a point of view in one of several ways (use the numeric keypad to get standard isometric viewpoints). Pick a rendering mode. Done. If you want this in a viewport on a sheet layer, View -> Create Viewport. You skipped a few steps. I don't know where you are getting your training, but I would suggest taking a look at the manual.
  2. Chris, there are 2 ways in VW to create a hatch. To create an associative hatch use the attributes palette and apply a hatch fill.
  3. Christiaan, that is the update build number, different from the build that was shipped initially.
  4. Ray, it sounds like Pete still has an issue. What do you mean by "particular workflow?"
  5. Try running just VW, and you will see that your graphs will differ and that one will be working much harder than the other. That's because VW doesn't use more than one processor at a time (except, as I noted, for RenderWorks rendering). Since computing power is now moving to multiple processors, we won't be able to boost our performance with CPU upgrades until VW is optimized to use multiple processors. I don't know if it's possible to get your P4 to run without the dual processor emulation. You might ask the company that sold you the computer, but I've never looked into it - I doubt it, but it's probably worth a phone call. Right now, only 50% of your P4 can be applied to a VW task.
  6. Thom, your P4 is probably emulating 2 processors. You can confirm that by looking at Windows Task Manager / Performance, and see if there are two separate graphs for the CPU. So most VW operations, except for RenderWorks, will use only 1 of those "processors" = 50% CPU capacity. Can you compare your experience with 2008 to VW 12.5? What are your video card specs? Forum users have noted a lot of problems with certain setups affecting the speed of 2008.
  7. Petri, just to clarify, are you saying that you don't use window or door PIOs?
  8. Bruce, I think you should be the one to write a wish list item asking that these settings be saved in a file that would not be affected by a VW crash!
  9. Christiaan, while I agree in the main with your comments, I think it's time we put the McMansion notion off to the side. I think it's a bit of a red herring, and doesn't serve our interest in getting NNA to focus on the real problems - fixing the flaws, such as those you point out, and expanding the power of the PIOs. The window sill has been a frustrating one, and one that I can't understand. It has nothing to do with conventional window detailing in any market, McMansion or otherwise. It just doesn't represent a sill properly for any window ever manufactured. Similarly with the stairs tool, most "McMansion" designs in my neck of the woods would never settle for the limited stair designs that tool can generate. With all respect to those who use VW purely as a 2d drafting program, that is not the future. If NNA focused solely on that, there would not be a VectorWorks in the future. In fact, if NNA doesn't come up to speed on some of these 3d tools, they are going to lose market share to software companies that can. I think the engineers at NNA are working on these things, per Jeff O.'s comments in a different thread on this board, and many of us are hoping they will get it right in the next release. In the meantime, while I acknowledge the flaws that Christiaan points out, in my practice 3d PIOs are still usable for many if not most situations. I would hope that the users who read these comments take Christiaan's remarks and his well-earned and credible opinions in balance with the experience of others.
  10. I just turned off my NVIDIA nview desktop manager, and it made a big improvement in the top bar flickering I had noticed with VW 12.5.2. Unfortunately, it hasn't made the same dramatic improvement for VW 2008, although it seems to have speeded things up somewhat.
  11. Petri, love that WHAT. But I was thinking of that pull-down menu as an advanced, or at least intermediate, utility. Just out of curiosity, what would a SQL-based mode be like? I don't have any experience with SQL, but isn't it like most other languages when it comes to logical statements?
  12. Checkbox or the equivalent is a great idea. Seems to me also that there should be a more technically accurate term available from a pulldown list before each criterion condition: AND, OR, AND NOT. A AND B selects objects that satisfy both A and B. A OR B selects objects that satisfy either A or B. A AND NOT B selects objects that , well, you know. One of the problems I think VW is trying to solve is that the casual use of "and" in ordinary conversation can mean "OR" as used in programming. By automatically supplying the "OR" when a user selects "More Choices," the user will be educated and the technically knowledgeable can easily edit the "OR" to an "AND" if desired. By supplying "AND" with the selection "Fewer Choices," we could then edit that to "AND NOT", another possible interpretation of "Fewer Choices."
  13. Islandmon, thanks, much appreciated sympathy. I'll send you a handful of hair as a token of appreciation! To uninstall VW, check this board for recommendations by Katie. You basically delete the VW folder and the associated Nemetschek application data in user settings, and you can also manually delete registry items (usual disclaimers about not tinkering with the registry unless you are familiar).
  14. Tom, to be fair, I didn't experience the problem when I first installed 12.5.2. Something has happened in the meantime, and it may well have been something in a Windows or driver update that conflicts or interacts badly with VW. Not to say that NNA is off the hook, but I myself know how hard it is to deal with a moving target.
  15. Katie, when I open a new file in vw2008 and draw a wall, after my second click the blue bar at the top of the application window flashes about 15 or 20 times. When I draw a second wall, same thing. When I draw a thrird wall, just a few flashes. The same thing happens often (talking about 12.5.2 as well here) when: entering a viewport, clicking on a window or door, editing a callout. I think there are two issues here. One is the actual flashing, which might be triggered by an unnecessary call to redraw the screen. The second is that (my hunch) VW is doing some dynamic loading of resources, and even if you could eliminate the "flicker," you'd still have a program slowdown associated with the dynamic loading. I'd ask the engineers two things: 1) are loading these resources always necessary? 2) why is VW resorting to dynamic loading (assume to preserve RAM and to make the initial startup faster), and is this the best strategy to solve these problems? Windows XP boots a lot faster than Win 2000 did, and the reason (I think) is that it gets to functionality faster because it loads some modules when it gets the chance, rather than forcing everything to load into dynamic memory before anything can be done. So, one strategy for VW would be to get to the point where a file can be opened or a new file created really quickly (that's where most users start their session). Then load more stuff as the user is looking for their file - etc. I'm not clear that saving the RAM has to be a big priority. I have to admit I'm not familiar with the numbers, but it seems that if you have to load resources to draw a wall or deal with a window PIO, you have to load them sooner or later anyway. My hardware: Intel CoreDuo 3.2 GHz, 2GB RAM, NVIDIA Quadro FX 3450/4000 SDI w/ driver, Dell flatscreen monitor (2007WFP) w/ driver
  16. Matt, thanks for going to the trouble to create a graphic illustrating the specifics of the idea. To limit the operation of the override to "none" class is an interesting idea, although as DWorks points out, it's not the only way to go. But having the Viewport override settings supercede might void the usefulness of the whole idea, since Viewports on Sheet Layers are the current method of choice for many (but certainly not all) users when it comes to output - which is where the graphics count most. For me, this inheritance feature would have to be a user-controlled option, not a default or automatic thing. I don't know that this is impossible. AutoCAD programmers were able to do it, but given the structure of NNA's code it might be difficult.
  17. Matt, I had similar problems a while back with 12.5.2, and had thought I had a corrupt file. I ended up removing VW and reinstalling, and the problem immediately disappeared and everything has been stable since. The signature of my problem was that when VW stalled Task Manager indicated that one processor was occupied with a VW task.
  18. Matt, if I understand you correctly, that would create a conflict. Of course, there is no current option to have an object "inherit" a symbol's class attributes, so I'm assuming you mean that the object's attributes are set to "use class," and you want the meaning of that to be "use the symbol's class," not the other class NNA assigned to the object. If you ask an object's attributes to be overridden by both the symbol object's class and by the class override in a Viewport (N.B., these classes are different, otherwise we wouldn't be talking about the inheritance concept), there would be no way for the program to sort out which one has priority. Or, at the very least, there would be a conflict with the desire of those users who don't want the ACAD behavior to prevail, and have set up their systems to work with the way VW currently behaves. Think about this: a line in a symbol has class "A," and is set to dash style "by class." Class A has a solid linestyle (no dash). Under your inheritance proposal, if the symbol is assigned class "B" with a short dotted line, the line would become dotted. But suppose that in your viewport you have defined a class override whereby class A is set to a long dotted line. Which dash style will the line receive? It has to be determined to be one or the other. If it automatically receives the short dash, that frustrates the desire of users to have the viewport preference apply. On the other hand, if you mean to suggest that there be a new attribute option, for a symbol member object to "inherit" its attributes from the class of the symbol container, then that might be a workable alternative to give the user a choice. It would add a button in a different location, I hasten to add, and it wouldn't give us the nuanced control to assign some attributes, but not others, the inheritance behavior. Having another setting for every attribute for every object would be too much.
  19. Bill's right about how ACAD blocks work, and there's just no exact equivalent in VectorWorks. There are workarounds, but I think it's worth mulling over a wishlist item to NNA about coming up with something that will give more meaning and power to the class assignment given to container objects. With ACAD blocks, the attributes of some (not necessarily all) objects within a block can be overridden by assigning the block instance to a "layer" (= VW class) in the same way VW objects take on class attributes only if they have been created with the "by class" options selected. It strikes me that if there were a checkbox option on a symbol, whereby the user could choose to override member object attributes according to the class assignment of the symbol container object, that would do the job without creating a conflict with the normal way that classes can be modified in a Viewport. This would only operate on those objects and those attributes with "by class" selected. You could call this idea "optional inheritance."
  20. Bill, you can override the class attributes of your objects in a Viewport, so you don't need to create two symbols. If you want to display the same symbol in two different ways in one drawing, you'll need 2 viewports to do that. Look at the OIP with a viewport selected. Go to the "classes" button and when the list comes up, you can edit the class attributes, and those edits will apply in that viewport only. So you can change your linestyle to dotted for that viewport, for example. Window and Door PIO's as used straight from the window and door tools can be classed and will pick up class settings and viewport overrides in the manner you are asking for. Those aren't really symbols, per se, they're a different kind of object. So if you are looking for the easiest way to have a window or door be dotted in one plan and solid in another, assign them to a Demo class like the wall, and use viewport overrides to have that class display differently in different drawings.
  21. Peter, what is "windows XP compatibility mode?" Okay, researched that myself. I have been running without checking that option for almost a year, without experiencing problems. From what I understand, if you are in compatibility mode you may be unable to run 64 bit programs, and since some of those are part of the system, you might run into some problems. In fact, I wouldn't be surprised if this is the reason you can't run with 4 GB RAM. It's worth a try anyway, and I have an ulterior motive in getting you to try in that I'm uncertain whether to upgrade my RAM! I don't know why you are opting to use compatibility mode, but on my system the 32 bit emulator works just fine without resorting to compatibility mode. BTW, with 64 bit you could install 128 GB RAM! (assuming everything works and your buss could handle it!)
  22. Pete & Ray, someone on another thread was complaining about VW crashes or stalls, and, perhaps it's just coincidence, but he had the NVIDIA 7600 video card. If you have an extra 20 minutes, you might try swapping that for an older card to see if it is part of the problem.
  23. Well, the logic of this is that your contained objects might have different classes and attributes, so you don't want the container object to override the differences.
  24. Mike, do you think that this is mainly for folks who still do their printable output on Design Layers instead of Sheet Layers? I use Sheet Layers now for all output. The only use I think I have for Viewports on a design layer would be when I want to have more than one version of a detail on my Sheet Layer in a case where the detail is composed of 2d objects drawn over a Viewport.
  25. billtheia, you don't necessarily have to convert your symbols to groups. The same process will work in both converted and unconverted symbols. Enter the symbol or group to edit the objects. Change all the objects so that they take attributes by class. BE AWARE that it is the class of these objects, not the class of the group or symbol, that will affect how they look. So if you want to have a class that controls them, set one up and ASSIGN IT TO THE OBJECTS. Assigning that class to the symbol instance will not do anything. Assigning that class to a group will also do nothing, unless you are prompted by VW about whether you want the class assigned to the group's objects and respond affirmatively. So, I would suggest that you use some special class other than "None" to control how these objects look. The biggest use of this level of control is to customize class attributes in Viewports.
  • Create New...