Jump to content

doug shaffer

Member
  • Posts

    215
  • Joined

  • Last visited

Everything posted by doug shaffer

  1. Donald - I think you meant to say 'attributes' pallette, not constraints pallette. Although it may seem like a minor glitch, the arrowhead bug slows down my work significantly. I hope it is fixed soon. It was one of the first bugs I submitted - within 3 days of receiving VWA9.0.0. thanks, ------------------ d. s h a f f e r a r c h i t e c t
  2. Sean - Thanks for your response. It does look like I missed one step in my description. In my originally described procedure, I should have indicated that I was trying to draw TWO walls, not one, and the procedure I described does not result in two walls. Sorry. Here is a better example: The result I want is a 3 ft. piece of horizontal wall and a 5 ft. piece vertical wall joined with a corner joint. It used to be that I could single click to begin a horizontal wall, tab over to the 'x' field and type 3', press return, THEN SINGLE CLICK (the step I originally left out) while the wall is constrained horizonatlly. The result is a 3ft. horizontal section of wall, and I am allowed then to continue the wall vertically. However, when I tab over to the 'y' field, type in 5', and hit 'return', the wall is offset 5' vertically AND 3' HORIZONTALLY. This is where 8.5.2 and 9.0 are different from 9.0.1. Note that this occurs with any precision input operation you may be performing. Let me know if you need further clarification. thanks again, ------------------ d. s h a f f e r a r c h i t e c t
  3. The leader line tool is there, it's just hiding. I added it using the workspace editor. It is included with the '2D tools'. Good luck. ------------------ d. s h a f f e r a r c h i t e c t
  4. I may have posted this already, but it's a doozie and am wondering if anyone else has seen it. Bug Report: This is an INTERMITTANT problem that occurs on my Mac G4/466 with 256MB RAM. It has occured with files that were originallybegun in 8.5.2, 9.0, and 9.0.1. Occasionally when working in on a VWA9.0.1 file, UNDO stops working properly, and in a way that is potentially very dangerous. Here is an example: I was working on a file and selected a portion of the drawing to do a 2D reshape with marquee. I accidently stopped it at a funny angle. When I tried to do an UNDO, it jumped to a different view (seemingly unrelated to previous views) WITHOUT undoing the 2D reshape. The only way to go back was to 'revert to saved'. However, the file still would not do UNDO's. I quit and re-opened the file to no avail. A computer shutdown, then restart solved the problem. temporarily. Later the problem came back (same file) and I had to shut down again. Some tests I did after doing a 'revert so saved' - I drew a line at random, did an UNDO and was zoomed back as if i had pressed the minus-magnification button. The line remained. It seems that the problem is unrelated to the complexity of the action I am trying to UNDO. I tried all the UNDO options in the 'preferences' to no avail. The problem has occured several times on four separate files. Has anyone else reported this bug? What a pain. d. s h a f f e r a r c h i t e c t
  5. Nemetschek - Please respond to this issue. Thanks - ------------------ d. s h a f f e r a r c h i t e c t
  6. HELL0 - There are some strange things occuring with walls, and one disabling bug when doing precision inputs in VWA9.0.1 for Macintosh. These occur on all machines (G3's and G4's) in our office. 1. This is the main problem which occurs in 9.0.1 and NOT in 9.0 - There are glitches when drawing 'walls', polygons, etc., in plan when using the 'tab' key to move through the data entry fields at the top of the screen. For example: begin a wall, then tab once to move to the 'x' field. Then enter a dimension of 3', for example, and push the return key. The result is that a horizontal wall that is 3 ft. long is drawn and the wall tool is still activated, 'waiting' to be continued. It used to be (in VW8.x and VWA9.0) that I could continue the wall 12" vertically (for example) by tabbing over to the 'y' field and entering a dimension of 12". When this is done in VWA9.0.1, the wall jumps to a spot that is 12" vertically, but ALSO 3 FT. HORIZONTALLY. I assume this is bug, not a new feature, of 9.0.1. 2. When the wall tool is picked, a wall is started, and single clicks are used to change the direction of the wall (but not end the operation), the wall edges seem to be shooting off in odd directions as the mouse is curser is moved around on the screen. Related to this, it seems that the smart cursor cues are working correctly, although what is drawn on the screen is not. For example, when continuing a wall after several single clicks, if I want to make another horizontal portion of wall, the smart curser cue will be 'horz' but the wall will be drawn (before clicking) at an odd angle which is not horizontal. If I then click when the cue says 'horz', indeed the wall is completed correctly, i.e. horizontal. I'm sure this is confusing. more fundamental stuff that needs to be fixed soon... d. s h a f f e r a r c h i t e c t
  7. I totally agree. Please change this tool back to the way it worked in 8.5.2. Thanks, ------------------ d. s h a f f e r a r c h i t e c t
  8. Hello - I too have experienced general 'slowness', especially when using plug-in objects. Using plug-in objects in 8.5.2 did not seem to be so slow. Also, the slowness of the measuring tool is really strange. Surely this is a fixable bug. Thanks,
  9. I don't know why the quick-key was removed, but you can add it using the workspace editor. I did. ------------------ d. s h a f f e r a r c h i t e c t
  10. i have requested this many times. I hope others think about the time saving potential in this concept. ------------------ d. s h a f f e r a r c h i t e c t
  11. Hello - VWA9.0.1, Mac, G4-466, 128MB for VWA Here is a bug in 9.0.1 that was not in 9.0. When using the 'pocket door' option in the 'simple door (v2)' tool, 'trims' are automatically drawn even if the trim check boxes are not checked. In the object info pallette, both 'trim' boxes are checked and CAN NOT be unchecked. When the box is clicked, it momentarily goes blank, then becomes checked again. Also, line weights do not default to the weight of the wall lines. This is a tool that I use regularly and I hope that a fix can be posted on Nemetschecks website AS SOON AS POSSIBLE. ------------------ d. s h a f f e r a r c h i t e c t
  12. Hello - Mac, G4-466, ATI Radeon, 256MB (128MB for VWA), VW9.0.1, RW9.0.1 I just received VWA9.0.1 and RW9.0.1 and installed them this morning. I am still seeing a few of bugs that were reported to bugsubmit@nemteschek.com. 1. 'leader line' arrow heads - I prefer to add the 'leader line' tool to my VWA workspace. When doing so, if I create a leader line using the 'notes' class (one that I made), the arrow head does not default to the class setting. I have the 'use at creation' box checked. To correct the problem, I need to select the class default arrowhead in the attributes pallette (even though the box says that the class default is selected) 2. 'One or more operations was aborted due to lack of memory. Increase partition size.' I get this error message on most (but not all) of my files when rendering with something other than basic 'open GL' rendering. The file size does not matter. For example, on one file that is 4.1MB, the error does not occur. On another (that is 829K, 252 objects) it occurs consistantly. 3. Problems with 'mapped shadows'. Mapped shadows seem to become less accurate as the physical area of a model is increased. I tested this problem by creating a relatively large (1000 ft. diameter) extrusion and placing a small house on it. When doing so, mapped shadows are totally lame. Reducing this disc to 200 ft. diameter makes them look nicer, but still with irregularities. An out-house sitting on a 8 ft. disc renders beautifully. With the RW9 changes, I can not seem to get as nice results as in 8.5.2. - see the McDonald Residence and Yarborough Residence on our website (www.mchenryarch.com) which were rendered in 8.5.2. For the record, the problems with Ray traced shadows have been corrected in 9.0.1 as far as I can see. I hope I don't have to add to this list... thanks,
  13. Hello - Mac, G4-466, ATI Radeon, 256MB (128MB for VWA), VW9.0.1, RW9.0.1 I just received VWA9.0.1 and RW9.0.1 and installed them this morning. I am still seeing a few of bugs that were reported to bugsubmit@nemteschek.com. 1. 'leader line' arrow heads - I prefer to add the 'leader line' tool to my VWA workspace. When doing so, if I create a leader line using the 'notes' class (one that I made), the arrow head does not default to the class setting. I have the 'use at creation' box checked. To correct the problem, I need to select the class default arrowhead in the attributes pallette (even though the box says that the class default is selected) 2. 'One or more operations was aborted due to lack of memory. Increase partition size.' I get this error message on most (but not all) of my files when rendering with something other than basic 'open GL' rendering. The file size does not matter. For example, on one file that is 4.1MB, the error does not occur. On another (that is 829K, 252 objects) it occurs consistantly. 3. Problems with 'mapped shadows'. Mapped shadows seem to become less accurate as the physical area of a model is increased. I tested this problem by creating a relatively large (1000 ft. diameter) extrusion and placing a small house on it. When doing so, mapped shadows are totally lame. Reducing this disc to 200 ft. diameter makes them look nicer, but still with irregularities. An out-house sitting on a 8 ft. disc renders beautifully. With the RW9 changes, I can not seem to get as nice results as in 8.5.2. - see the McDonald Residence and Yarborough Residence on our website (www.mchenryarch.com) which were rendered in 8.5.2. For the record, the problems with Ray traced shadows have been corrected in 9.0.1 as far as I can see. I hope I don't have to add to this list... thanks, ------------------ d. s h a f f e r a r c h i t e c t
  14. I have not found updated drivers for the ATI Radeon card. Are they out there somewhere? I looked on the Apple and ATI websites. ------------------ d. s h a f f e r a r c h i t e c t
  15. Which known bug are you referring to? Just wondering. ------------------ d. s h a f f e r a r c h i t e c t
  16. This is unfortunate. There are many of us that use VW who would like to draw mechanical and electrical plans on top of 'grayed-out' floor plans. Many contributors to the VW user forum requested this capability. This is one of the essential effeciencies that CAD in general has to offer, and it is hard to imagine why this capability would not have been included in VW9. disappointed, ------------------ d. s h a f f e r a r c h i t e c t
  17. doug shaffer

    tutorial

    Howdy Frank - When will Landmark be available? thanks - ------------------ d. s h a f f e r a r c h i t e c t
  18. Hello - Take a look at the topics called: 'offset tool problems', and 'Re: circle offset' from 5/22/2001 for similar problems. ------------------ d. s h a f f e r a r c h i t e c t
  19. I'm using VWA 9.0.0. For your information, I have been able to use 'float 3D objects' successfully. Thanks. ------------------ d. s h a f f e r a r c h i t e c t
  20. Howdy - I have seen this occur also. It happens on files that are originally created in VW9 as well as VW8.5.2. I have also seen a very strange behavior where a circle which is offset has pie shaped slices removed from it for no apparent reason. ------------------ d. s h a f f e r a r c h i t e c t
  21. I have noticed this too. Mac, VW9 ------------------ d. s h a f f e r a r c h i t e c t
  22. Ignore the previous message - I just figured out that this is a VWA thing that is desribed in the VWA Manual. sorry for the inconvenience. ------------------ d. s h a f f e r a r c h i t e c t
  23. Hello - Occasionally, a window pops open at the bottom of my monitor that says: 'A Preference Set has not yet been chosen for this document.' I opened the .pdf version of the VW9 Users Manual and searched the document for 'preference set', but found nothing. What is it? Do I need to choose one? If so, how? thanks ------------------ d. s h a f f e r a r c h i t e c t
  24. Paul - Thanks for the quick response. I did notice that in the first paragraph of your statement you used the term 'intermittant' when describing the problem with the ATI card. However the next paragraph of your statement said this: "With the NVIDIA card, this problem affects VectorWorks versions 8.0.1 through 9.0.0. With the ATI card, it affects versions 8.0.1 through 8.5.2" To me, this implies that Nemetschek thinks that the problem no longer occurs at all with the ATI card and VW9. I just wanted to give you my most recent observations regarding the Radeon card and VW9. Regarding the 'randomness of a buggy driver', perhaps I can understand your logic. However, it still seems strange to me that if 'no changes were made to the code', why does the problem occur only rarely in VW9 where as in VW8.5.2 it occured all of the time? Is it possible that some portion if the VW9 code that is seemingly unrelated to display issues is conflicting with the display code? I'm only trying to help. ------------------ d. s h a f f e r a r c h i t e c t
  25. Hello Paul - Thank you for your thorough explanation of what is happening with this issue. We recently installed VWA9 on a machine in our office that has an ATI Radeon card and have seen the Video Card Woes problem go away. Again, I don't understand anything about programming, but it seems strange to me that if the problem is attributable to the drivers that it would somehow dissappear with a new release of VectorWorks. I am not trying to place blame on Nemetschek, but I am interested in an explanation. Here's another related observation with VW9 installed on our Mac with a ATI Radeon card: Occasionally (once every couple of hours) the selection handles disappear without warning and for no apparent reason. The file we are working on at the moment is quite large - 15MB. We have not nailed down a series of actions that causes the problem. A file close/re-open solves the problem. Strange. Thanks again for the update. ------------------ d. s h a f f e r a r c h i t e c t
×
×
  • Create New...