Jump to content

doug shaffer

  • Posts

  • Joined

  • Last visited

Everything posted by doug shaffer

  1. Hi, eas - Did you ever figure out how to batch print from multiple files? We are trying out how to do this now, too. thanks -
  2. Hi - We are starting the Design Development phase of an industrial / office project which is the largest project we've ever produced using VectorWorks. There will be three of us working on the project (plus three consultants using Autocad), and we are looking for information regarding the best means of working on the project as a team. We are familiar with how to use design layer and sheet layer viewports, and understand the concept of using design layer viewports to external files. Does anyone have any tips, or links to processes that have been spelled out? For example, do people use different files for each floor of the building? Are are notes and dimensions added using the 'annotations' part of viewports? Regarding sheets that will be printed, are they all compiled in one main file, or are sheets scattered amongst the various plan, elevation, etc. files? I realize that this is a complicated question, so I appreciate any advise you might have. FYI, we will be working in 2D only on this one. Thanks -
  3. Hello - I thought I had posted this already, but I couldn't find it in the archives. I REALLY like the new option of 'gray other objects' when 'show other objects while in editing modes' is selected. However, I find that when I am editing viewport 'annotations', if I zoom in close, the gray objects disappear. I think this may be a bug. When 'gray other objects' is not selected, the problem does not occur. Can anyone on this list confirm this problem? Also, has anyone written a script that allows you to toggle 'gray other objects' and/or 'show other objects while in groups' on and off using a quick key? Someone out there had written one for previous versions and I used it regularly. thanks -
  4. I received an email from Nemetschek asking if this was still a problem with VW2009-SP3 and I told them that it still is. Can anyone else confirm this? Thanks
  5. Hello everyone - I discovered my problem. Somehow I managed to change the class visibility of the problematic objects to gray. I don't know how I managed to do it, but it was obviously my dumb mistake. Thanks for your replys, and sorry for any unnecessary head scratching I caused. d. s h a f f e r a r c h i t e c t
  6. Hi - VW2009 SP2(build 99197) iMac intel osX 10.5.6 We have been using VW2009 for several weeks now. I started a new file in VW2009 and have been working on it for several weeks now. On several occasions, I have had a problem that is a little hard to describe. Occasionally when I switch to a design layer that contains any number of objects (lines, walls, PIO windows and doors, etc) all or most of the objects are "gray" and NOT selectable. It is as if they are locked somehow, but they can not be unlocked because they are not selectable. For example, on my screen right now is a design layer that has 40 or so walls, some wide flange columns, some doors and windows. Nothing is selectable except for the wide flange columns and two windows. (all other windows are grayed out) I should also note that I CAN snap to all of the grayed objects, and smart cursor cues appear. Also, I can quit the program, restart the computer and problem persists. PLEASE HELP! (and yes, we have a good backup system) Thanks -
  7. I have an observation which slightly modifies what I said previously. These are the criteria to make "Use Part Line Stlyes" work properly. 1. Attributes Palette is set as Wes Gardner described above. 2. "Use At Creation" is UNCHECKED in the Class Settings of the Active Class at the time the door / window is placed. I hope this helps N.N.A. resolve the problem for the next 'service pack'. Thanks -
  8. Thanks for your response - The solution you propose seems to work under the following conditions only: 1. Attributes Palette is set as you described 2. The window / door is placed while in that objects active class. I.E., if you are in a different active class, and you are using 'Standard Naming' and 'Enable Auto-classing', it doesn't work. 3. "Use At Creation" is UNCHECKED in the Class settings of the door or window object. To me these all are work-arounds, but I suppose they are better than changing each object individually after they are placed. Given that this has been a problem for several versions now, can I count on NNA ever addressing it?
  9. Hi - Does NNA have a response to this? I've contacted them through bugsubmit several times, and it has simply never been fixed. I think it started occuring in VW12. It appears that you use VW2009 - does it still occur? Aggravated,
  10. I can confirm this also. Please fix, NNA. Thanks -
  11. FYI Here's a message that I received from Nemetschek regarding this problem: <Hi Doug, So this is a bug, more like my indiscretion. I am changing the detail line styles to the class pen styles, when I should be only changing the cut lines. I will enter a bug for this. Sorry for the inconvenience. And you are correct the only way around this at the moment is to not use pen styles by class for doors and windows at this time.>
  12. dcont - Based on your tip, I think I've figured out a work-around that is time consuming, but would let us continue working with the file. Here's what I do: 1. select door or window 2. double click to open settings 3. push OK button 4. change "pen style" to "none" using attributes palette 5. change "line style" to something other than 0.00 (we use .13mm) to make door jambs appear correctly That's it. We are using Macintosh computers, G5 and Intel - all show same behavior. Thanks again -
  13. Hello again- I am having trouble with plug-in doors and windows in an existing (created before VW12.5) file. When I edit them, all of their components automatically go to whatever the attributes (in the attributes pallette) for the object are. For example, if I change the width of the window, the width changes, but all of the line weights change to one weight. In this case, "Use Part Line Styles" does not override. As a test, using the same file, I tried creating a new wall and placed a new window and new door in them; I got the same result. When creating doors and windows in an entirely new file (created in VW12.5), the tool works as designed, as far as I can tell. (Thank goodness!) Is there a way to make plug-in doors and windows work properly in existing files? The original file was created in version 11.5, but was converted to 12.0.1 shortly after its release (about 8 months ago).
  14. Quigley and others - Nemetschek's current recommendation is against running Vectorworks under Rosetta. I my posting, I made the mistake of demanding for a 'Universal Binary' version of Vectorworks, when the reality is that all we need is a version that Vectorworks endorses running under Rosetta. Regarding the release of updated software to coincide with Apple hardware releases, the first Intel Macs were available last January. After reading responses to this issue, it may be worth the risk to go ahead and buy a new Intel Mac and hope we don't have any problems. This is the only apparent option for us at this point. slightly less frustrated,
  15. Hello - I apologize in advance to those who find it necessary to defend Nemetschek's business policies, or who are tired of listening to complaining about this subject. In an article titled "Technology Update: Rosetta Compatibility" (from the NNA Knowledgebase - February, 2006), Nemetschek said this: <..."These functional problems and speed issues prevent us from recommending that VectorWorks be used on Intel-Macintosh hardware in a professional environment. However, VectorWorks 12 is stable and robust enough under Rosetta emulation to be used in some limited evaluations or less demanding capacities."...> We need to add another workstation (possibly two) to our "professional environment", but Apple no longer makes PowerPC based computers. Our patience is growing thin, Nemetschek. Why has it taken so long to release the 'Universal Binary' version of VectorWorks? We have invested a lot of time and money in Nemetschek over the last eight years, but we can no longer afford to wait. Please give us an anticipated release date for VectorWorks 12.5. (one week? 6 weeks? 20 weeks???) Here is a link to the whole article: http://kbase.nemetschek.net/index.php?ToDo=view&questId=91&catId=23 frustrated,
  16. Hello - I'm really getting anxious for VW12.1, too. My biggest problem is with plug-in windows. In 'TOP-PLAN' view they look terrible. In my opinoin, there variables that affect the appearance - i.e. line weights, etc. - in plan view. When the 'known bugs' with the 'window' PIO are FIXED, hopefully control over their 2D appearance will be better. Do I have to switch back to Version 11.5 to get decent looking windows? Frustrated -
  17. We downloaded and installed the 10.2.8 update and have seen no problems. Two computers are: G4/466/512mb VWArchitect/Landmark industry series + Renderworks G3/300/512mb VWArchitect
  18. Hello - Macintosh G4/466/512 OSX 10.2.6 VWArchitect/Landmark Is there any VectorWorks specific reason I should not update to OSX10.2.8? thanks -
  19. Katie - I did originally send this problem to bugsubmit, and I found responses from Nemetschek in the archives indicating that it had officially been entered as a bug. I will send it again, though.
  20. Hello - Well, the very first thing I tried was the 'window' tool to see if the sill line weights problem was fixed in version 10.5. Nope. Basically, if you insert a window and the sill depth is greater than "0", the line weight of the sill is the same as the wall when 'use wall line weight' is selected. This bug was submitted by me and many others (see these archives, and the VW USERS FORUM). Yes, I can de-select the default 'use line weight' option, and manually enter the line weights for the various window components, but I don't think I should have to go through that trouble every time. The whole concept of the 'use wall line weight' (default) setting should be that parts cut in section are the same as the wall line weight, and parts that are not (sill, etc) are the particular class setting. It worked this way in version 9. frustrated,
  21. ...tick...tick...tick...tick... ...still waiting for a reply....
  22. Thanks for the confirmation, dsolutions. Any comment from Nemetschek on this?
  23. Hello - VWA10.1.2, Macintosh, OSX10.2.6 This is going to be a bit difficult to describe. When using the Window PIO from the Objects tool pallette, the 2D representation of the window has a couple of problems that I can see. 1. When a window PIO is inserted into a wall, the sills are drawn as filled solids so that you do not see elements that may be placed below the window. This is how it should be. However, the window 'sash' is not filled. For example, if you make a window with a 2" thick sash, the 2D window is 'solid' with the exception of 2" wide zone where the sash is indicated. To see this, draw a wall then insert a window using the tool pallette. Next draw a another element, a colored rectangle for example, and 'send to back' so that it is under the window (so the window is stacked on top of rectangle). You will see what I'm talking about. 2. When I use the Window tool from the Objects pallette, the interior and exterior sills have the same line weights as the wall. (if "use wall line weight" is selected) It seems to me that sills should not be represented as if they are cut in section. Shouldn't they have the same weight as the selected class, as do the other parts of the window that are not cut in section? Is this a bug? Is anyone else experiencing this problem? Am I doing something wrong? d. s h a f f e r a r c h i t e c t
  24. Mat - I assume that you are wanting to change the size of the text displayed on the dimension strings. Do this by selecting all the dimension strings that have the wrong sized text then using the 'text' menu to drag to the point size you want to change them to.
  • Create New...