Jump to content

doug shaffer

Member
  • Posts

    230
  • Joined

  • Last visited

Posts posted by doug shaffer

  1. Another "new" issue: new sidelite control allows for depth of mull...great. But the Jamb Part Line Style seems to control the "sill" wt. a lot like the Window PIO in 12.0.0 before it was fixed in 12.0.1. (By sill I actually mean the line viewed in plan at the edge of the mullion "frame"--not the Wall Line or Threshold).

    I can confirm this also. Please fix, NNA.

    Thanks -

  2. 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.>

  3. 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 -

  4. 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).

  5. Doug,

    I happen to think you are being unreasonable to expect NNA or indeed any other software manufacturer of any size to be able launch UB versions to coincide with Apple hardware releases.....

    .....So I'm not defending NNA but be reasonable. Fact is that on one of these new machines VW and most other software will run very well indeed even under Rosetta. And when the UB versions do roll out you will have state of the art.

    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,

  6. 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,

  7. 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 -

  8. 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,

  9. 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

  10. 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.

  11. Hello -

    Below are a couple of postings that were recently made at the Vectorworks User forum site. Can someone from Nemetschek address this issue?

    thanks -

    David -

    We are using VWA+L 9.5.3b1, OSX10.2 with a HP Laserjet 4V printer and have the

    same problem. Is it likely that this is a VW problem or an OS problem? If it is a VW

    problem, I hope it can be worked out prior to the final release of 9.5.3.

    thanks -

    d. s h a f f e r

    a r c h i t e c t

    On Mon, 23 Sep 2002 11:06:25 -0700, david poiron <david@POIRON.COM> wrote:

    >Here is a new one:

    >

    >When printing to our HP LaserJet 5100, text that straddles the page boundary

    >prints compressed (and backwards?) together, as if it were trying to fit all

    >the text on the page.

    >

    >We are using Mac OS X 10.2.1. VW 9.5.3b2

    >

    >Anyone experience this?

    >

    >Dave.

    >

    >(btw, VectorWorks 10 looks pretty cool! Does it fix my problem?

    >

  12. Hello -

    Below are a couple of postings that were recently made at the Vectorworks User forum site. Can someone from Nemetschek address this issue?

    thanks -

    David -

    We are using VWA+L 9.5.3b1, OSX10.2 with a HP Laserjet 4V printer and have the

    same problem. Is it likely that this is a VW problem or an OS problem? If it is a VW

    problem, I hope it can be worked out prior to the final release of 9.5.3.

    thanks -

    d. s h a f f e r

    a r c h i t e c t

    On Mon, 23 Sep 2002 11:06:25 -0700, david poiron <david@POIRON.COM> wrote:

    >Here is a new one:

    >

    >When printing to our HP LaserJet 5100, text that straddles the page boundary

    >prints compressed (and backwards?) together, as if it were trying to fit all

    >the text on the page.

    >

    >We are using Mac OS X 10.2.1. VW 9.5.3b2

    >

    >Anyone experience this?

    >

    >Dave.

    >

    >(btw, VectorWorks 10 looks pretty cool! Does it fix my problem? [Wink]

    >

  13. Hello -

    THANK YOU, NEMETSCHEK!

    I just visited the Vectorworks User Forum site and found the following posting from Paul C. Pharr.

    Hi everyone,

    We posted 9.5.3b2 this afternoon to resolve some additional problems withMacOS 10.2 compatibility.

    http://www.nemetschek.net/downloads/vectorworks/9.5.3b2_page.html

    This addresses most known problems with the exception of dongle drivercompatibility. We expect to have a solution for that issue soon.

    Thanks,

    Paul C. PharrCAD Software ManagerNemetschek North America

  14. Hello again -

    THANK YOU, NEMETSCHEK!

    I just visited the Vectorworks User Forum site and found the following posting from Paul C. Pharr.

    Hi everyone,

    We posted 9.5.3b2 this afternoon to resolve some additional problems withMacOS 10.2 compatibility.

    http://www.nemetschek.net/downloads/vectorworks/9.5.3b2_page.html

    This addresses most known problems with the exception of dongle drivercompatibility. We expect to have a solution for that issue soon.

    Thanks,

    Paul C. PharrCAD Software ManagerNemetschek North America

  15. Hello -

    A friend of mine turned me to some late breaking news regarding the soon to be released OSX10.2.1. Perhaps this information will point toward a diagnosis of the problem. If the links below do not work properly, go to macsurfer.com and scroll down to the OSX section.

    http://www.eweek.com/article2/0,3959,538582,00.asp

    http://www.pcpro.co.uk/front_index.php?ip=1&domain=macuser&page=%2Fnews%2Fnews_story.php%3Fid%3D32374

    http://www.macslash.org/comments.pl?sid=02/09/16/2021247&threshold=-1&commentsort=0&mode=thread&cid=39

  16. Katie, Matthew and Paul -

    Just for clarification, I will restate the problems that we are seeing:

    The problems occur on both machines in our office. They are:

    G3/300/256mb VWA 9.5.3b1G4/466/512mb VWA+L 9.5.3b1

    Occasionally when working on a file, the program (VW) will crash ('unexpectidly quit') while doing a cut and paste/copy and paste operation. This problem is INTERMITTANT. When this occurs and an attempt is made to open the file again, the program quits after several seconds without fail. A re-boot is then required to 'fix' the problem.

    Our experience is that the cut/copy paste problem occurs whether using keyboard shortcuts or the menu commands. The problem has also occured when using the 'option' key to copy an object and drag the copy to a new position.

    I should add that there are other crashes that occasionally occur (far less frequently, and not related to cut/copy and paste) that then require a re-boot of the system also. For example, a few minutes ago, my co-worker Mark was creating some new layers then saved the file and closed it without quitting VW. However, while the file was closing, the application 'unexpectidly quit'. Again, when this occured an attempt was made to open the file, and once again the program quit after several seconds. A re-boot was required to move forward.

    My opinion is that the problem is not FILE specific for two reasons:

    1. The problem occurs with files that were newly created (while using OSX10.2 and VW9.5.3b1) and with files that were created prior to installing the updates. It has occured on all five projects that we have been working on only since installing the updates.

    2. A re-boot 'fixes' the problem temporarily. If the file was corrupted in some way, how would simply re-booting the machine fix the FILE? After a re-boot the file is NO DIFFERENT than it was before the re-boot. I have sent a sample file to bugsubmit, but it seems that this might be missing the point.

    Finally, trashing the preference file did nothing to alleviate the problem. It seems to be occuring just as frequently and the machines still require a re-boot.

    Thanks, and good luck.

  17. Katie and TiTaNiuM sAMuRai-

    Thank you for the information regarding the preference file and where to find it. Are you (Nemetschek and TiTaNiuM sAMuRai) saying that trashing the Vectorworks preference file will fix the cut-and-paste/crashing bug? There has not yet been a response from Paul Pharr to my last question in this thread which might shed further light on the issue.

    I hope this is the answer to our problems.

    Thanks again -

  18. Paul -

    Can you be more specific about what you mean by 'misinformation'? Are you referring to the serial number issue raised by Katie?

    I understand that the software engineers at Nemetschek know far more than I regarding exactly how Vectorworks and an OS work together. Having said that, since my shift to Jaguar I am only observing problems with Vectorworks. I am not trying to suggest that Nemetschek is simply trying to shift the blame, but perhaps this observation (symptom) will inform a diagnosis sooner.

    Thanks for your efforts to clear this up.

×
×
  • Create New...