Jump to content

P Retondo

  • Content Count

  • Joined

  • Last visited

Everything posted by P Retondo

  1. Michelle, I think you will find that most new "Wintel" computers are shipped with WinXP. I've used both XP and 2000, they are basically the same and work very well with VW (I assume you are using VW 8.5 or later). Your performance problem probably had more to do with your respective computers' hardware than with their operating systems. I would recommend getting the fastest processer and largest amount of RAM you can afford if performance is an issue. I also recommend getting a Pentium processor. The Celeron has had some problems with it's backside cache, and I've heard some people report problems with the AMD. I've always stuck with Pentium and have had no problems.
  2. Giovanni, Thanks for confirming that you have had this problem! Is it possible that the problem has to do with units accuracy? I say that because one thing I did the same day this problem came up was to add layers at 1"=40', when previously all layers had been at 1/4". I also notice that the information palette for the rise and run of roof elements has strange behavior. Instead of showing 3" / 12", some of the corrupted roofs show .003" / .01". When I attempt to edit .003" to .0025", the program reverts the entry to .003". When I change both fields to 3" and 12" respectively, those numbers are accepted. The 6:12 roofs show .005" / .01", which might have been rounded to .01" / .01" if unit accuracy had been downgraded by adding the layer at 1"=40'. Since VW 9.5 uses 64 bit numbers, this accuracy problem would not be as much of an issue. Can anyone at NNA or among users comment on how likely this explanation is, and are there any tips on how to avoid the problem in 8.5?
  3. Added info on corruption: it is possible to restore the failed subtractions merely by "entering" them (ctrl+[) and exiting (ctrl+]). This apparently regenerates the geometry. On the roof problems, some of the roofs were corrupted, some were not. Roofs were corrupted differently depending on certain circumstances. 6:12 roofs became 12:12. Roofs that had been ungrouped to edit their planes were changed variously. Some 3:12 ungrouped roofs became flat; some that had been gathered into groups changed from .0025" rise per .01" run to .03" rise per .1" run. Any information on these baffling corruptions would be greatly appreciated. [ 08-14-2002: Message edited by: P Retondo ]
  4. Working with VW 8.5.2 and a 3D model of a building. This morning my file opened up with multiple corrupted objects. All 6:12 roofs are 12:12, all 3:12 roofs are flat, and most but not all solid subtractions are failed. System: WinXP, P4 2.2G, 512MB RAM I can fix these objects, but if this is a continuing problem, VW is dead for me and for this office because we are using the program specifically for its ability to create 3D models in a hurry. I have to use ver 8.5 because my new version 9.5 has a bug in the walkthrough tool which freezes the program. Does anyone have experience with these problems? Thanks! [ 08-14-2002: Message edited by: P Retondo ]
  5. Matthew, Thanks for your further assistance. I am indeed getting the message "A required resource was missing" as the program freezes. To reproduce the problem: open a new document, extrude a rectangle, set any sun position, set a perspective view, render using OpenGL, start to navigate using the walkthrough tool. After about 30 seconds the speed of motion begins to slow noticeably. After another 30 seconds, multiple redraws of the sun icon begin to appear, then a confused screen appears, and then multiple recurrences of the "A required resource" message, then the appearance of the complete message "A required resourse was missing." At this point, if you wait, you may regain a semblance of normal program function (except that the walkthrough tool will cause a freeze immediately). However, VW then operates slowly and erratically and affects the performance of any other program until VW is shut down. It is not necessary to restart the computer in order for it to function normally. The full specs on my video card are: 64MB DDR NVIDIA GEForce4 MX 420 (TV out)BIOS version: .dll's are all Thanks - any solution to this problem would be appreciated. I could install an old version of VW 8.5 I own, if you think that might work. However, the firm's principal might then want to return the new copy of 9.5.2 for a refund!
  6. Matthew, Thanks for checking in on this. Needless to say, this is both disappointing and embarassing, since the office I'm now working in just bought a copy of VW at my request - they use ACAD for production - and my first whizbang demo of its great 3D capabilities crashed and burned. However, you did not answer my question. Please believe me when I say that the walkthrough tool on my old configuration was ABSOLUTELY STABLE. Does WinXP have a different OpenGL standard? Does my particular video card handle OpenGL differently? In other words, it appears to me that since VW is not currently forthcoming with a fix to this bug and can't say when it will be available, perhaps your engineers or other users could help me isolate a hardware/OS fix to work around the problem.
  7. I just installed VW 9.5.2 on a new computer, and I'm experiencing the walkthrough crash described by chopper4 on May 8 in this discussion area. The new computer has WinXP and a GEForce 4 MX video card. In my previous experience using Win2000 and both a GE2 and GE3 Titanium video card (old system: P4 2.0G, 775MB RAM, 128MB GE3 Titanium), the walkthrough tool worked perfectly. This problem has been described by Matthew G. as a VW bug, which it may be, but 1) has there been any progress resolving this problem, and 2) what is the explanation for the fact that very similar systems either have or don't have the problem? Is this a problem with WinXP, with the GE4 card, with the MX card? Does anyone have feedback on their configurations which could shed light on which component of my current system is involved in this problem? P4 2.26G512 MB RAM32MB GEForce 4 MX
  8. Do the attribute values revert when you select the tool, or right after you use it? If the latter, you probably have an object selected somewhere when you changed the attributes (check your info palette to see). Only if nothing is selected do changes to the attribute palette affect the status of defaults. Or, it could be a problem I know nothing about . . . BTW, it helps the tech support folks if you supply your system specs (VW version, OS, processor). [ 06-17-2002: Message edited by: P Retondo ]
  9. In my installation, both 2D and 3D rotate tools work correctly in all views. However, the 3D rotate tool is very slow compared to its operation in VW 8.5.2. VW 9.5.2Win2000P4 2Ghz785 MB RAM
  10. Thanks, Ion! That's a great method. I've seen the grid angle option on its menu many times, and never stopped to think what it might do besides display the blue lines at an angle. NNA: Still not a UCS. Things which don't work in the coordinate system created by rotating the grid: the move command, stretching (resize cursor), editing via info palette. These tools still operate with respect to the "page" coordinate system. Also, the only rotated constraints activated by the "shift" key are the two primary directions of the rotated grid. Other constraints, as set in preferences, still operate with respect to the page. Surely with all the code that has gone into these rotated coordinate capabilities, it can only be a short leap to a fully capable rotated coordinate system. [ 06-13-2002: Message edited by: P Retondo ]
  11. Katie, Yes, you can draw 2D objects that appear to be aligned with a working plane's coordinates, but . . . if you go back to standard top view, you will see that those objects aren't really rotated with respect to standard coordinates. In fact, the 2D coordinate system seems to be totally unaffected by changes in the 3D working plane alignment. Only if objects are converted to 3D will they remain rotated with respect to standard coordinates when you shift back to standard coordinates. We want to preserve the 2D-3D interface essentially as it now works, but have the ability to rotate the view and operation of tools for 2D operations. CipesDesign: I used to use your technique, but now use layer links to do the same thing more painlessly. Do your orthogonal work on one layer, and link that layer (make sure you check the 2D objects box)to the one that contains your site background info. Unlock and rotate/position the layer link. Then any updates you do will be automatically transferred via layer link. [ 06-12-2002: Message edited by: P Retondo ]
  12. You can generate elevations by giving your walls an appropriate Z+/- value, and constructing your roof in 3D. Then, when viewing this 3D model from the side, convert a copy the objects to lines and paste the result into a new layer. There is a ton of clean-up to do (i.e., removing extraneous lines), which others in the past have asked NNA to automate, but it is dimensionally accurate. If some things were automated, this could work like automatic updating. But as it is, if you change something in your plan, you have to go through all or part of the procedure all over again. Try this: draw a wall with 8' height, insert a window or door, change your view to look at it from the side or front, select it and "convert copy to lines." Move the resulting group of lines to one side to see what you have. The details of how you create the window or door affect how it will look in elevation. You can stretch parts of a drawing by grouping the objects. Then you can use the stretch cursor on the group. I often use this technique with VW 8.5 to distribute a group of lines equally over a given space. VW 9 has a tool for that function. You can also select the objects and scale en masse.
  13. John, What you suggest is what I in fact do. The problem is that in order to avoid error, the VW user should a copy of ACAD and know how to do a few things with it, to place the xref at the correct location. And with VW 8, I believe there is a potential for difficulty if the xref is updated following a change in the location of the VW file origin. On VW 8, at least, links can't be exported to a .dwg or .dxf file. Again, I think it would be possible to write a function allowing that if NNA chose to do so.
  14. defjef, ACAD does not have classes, only layers - advantage VW! There is a box in the export dwg dialog that asks whether to convert classes to dxf layers. If you check that box, the ACAD file will have a set of layers corresponding to your set of classes. If you don't, the ACAD file will have a set of layers corresponding to your layers. There is no way to sort some objects by class and others by layer, its all one way or all the other. In both cases, unless you request otherwise, only visible objects will be translated. As a rule, I make sure that invisible objects are not exported because you can often get results you didn't expect if you don't go that way. The translations are not ideal, but they're a lot better than they used to be! I find that VW 9 is at lot better at these exports when it comes to issues of line weight, font size, dealing with layers of different scales, etc. NNA: It would be possible to have the translator assign ACAD layers that combine VW layer and class, so you would end up with a set of layers like 1st_Fl_Plan_None and 2nd_Fl_Plan_None. Some users might find this a good tool. [ 06-01-2002: Message edited by: P Retondo ]
  15. Yes, "y" toggles screen hints on and off. I use VW 8.5.2 and Win2000 as well. I haven't had your problem, which does sound like an abnormality of some kind. The snapping pattern you describe (no centers) is consistent with having the "Intersection" constraint option turned on ("Intersection" toggled by "w"), but with "Object" constraint turned off. You will observe the lack of snapping to centers if you have not selected the "Object" constraint option (toggled by "q"). Constraint settings are reset when you reboot vW, so if you have accidently toggled something on or off it is often corrected by quitting and restarting the program. [ 05-31-2002: Message edited by: P Retondo ]
  16. It is possible to do what you want only in the world of 3D objects, by setting a working plane at any rotated angle you desire. VW then applies a system similar to ACAD's UCS (user coordinate system). Unfortunately, this capability does not carry across to the VW 2D world. A few months ago I suggested applying all the code related to 3D working planes to 2D objects to allow this capability - how about it, NNA? Multiple inheritance?
  17. Make all your relevant plan layers visible (creating one heck of a mess on your screen!), then export to ACAD. Your layers will be translated to ACAD layers, which the ACAD user can turn off and on and manage in ways which are functionally equivalent to VW layer management.
  18. defjef, Is snapping working when your screen hints disappear? You can tell by looking at the cursor - if you get close to a point or vertex and it changes from the hollow arrow to a black arrow or cross with a dot to the lower right, that indicates you are snapping, with or without the accompanying screen hint. If you are NOT snapping, this is probably because the appropriate contraints are not selected. "q" and "w" toggle the two constraints that enable snapping. If you ARE snapping and not getting screen hints - I have always found that I had inadvertantly hit "y" and toggled screen hints off. That, however, is inconsistent with your observation that "SmartCursor Cues" remains selected in your preferences box. Checking that box and hitting "y" perform the same action. So if you are getting snapping but no screen hints and hitting "y" does not solve the problem, something unusual is going on.
  19. Thanks, Matthew. I'll try your suggestion as soon as I have some time to be adventurous!
  20. A possible workaround if you are using this shape to create a 3D extrusion anyway: convert the circle to a polygon. The clip will then be performed. You can control the number of segments in the polygon conversion by setting your 2D conversion resolution in preferences. When you extrude, the circle would have been converted to a polygon anyway, unless you are using NURBS.
  21. Matthew, Update: I was able to restore functionality. I had to uninstall the new driver, then on restart Win2000 installed its generic driver. In the process, I elected to replace a bunch of files that the Install Wizard said were more recent. With this installation, VW crashed on being launched. I went to my backup, and replaced all the .dll's listed in the driver details window with yesterday's files. That fixed the problem, at least for now. Now that I am paying more attention, it does appear that Win2k installed its generic driver initially. There were a bunch of files already installed which were later versions, and during my original installation at the Install Wizard prompt I kept them. That appears to have been a lucky decision, because when I reinstalled the driver just now and elected to replace those files, the resulting configuration caused VW to crash. That's why I thought to go to yesterday's backup, and restore the listed .dll's. The driver provided on my MSI installation disk is not compatible with Win2000. So my current choices are to keep the generic driver, or install the upgrade that causes VW to crash as described in my earlier message. I will check with MSI tech support in a couple of days to get some guidance, but they will likely point the finger at VectorWorks - if you have any info, such as nuances of OpenGL that may be an issue, please let me know.
  22. Matthew, Not to find fault, but just to pass along hopefully useful info. I upgraded my nVidia driver, using the VGA adapter manufacturer's website (version 27.5 I believe). This resulted in immediate crashes of VW 8.5.2 whenever any kind of movement in a rendered model is attempted (walkthrough or flyover). VW 9.5.1 crashes even sooner, as soon as an attempt to render using OpenGL is made. I will now attempt to undo this installation, and get back to my old driver! [ 05-16-2002: Message edited by: P Retondo ]
  23. As suggested by some on this board, I upgraded my video card (from a 32MB GeForce2 to a 128MB GeForce3)in an attempt to accelerate realtime walkthroughs on a complex building using Open GL rendering. For those who are interested, this resulted in minimal, if any, improvement. Seems as though processer speed is the key. P4 2.0G785MB RAMWin2000VW 8.5.2 and 9.5.1nVIDIA G3Ti200
  24. Joe, As a long-time user of VW 3D dating back to MiniCAD 4.0, I would guess that your biggest problem is with snapping. Some really strange things can happen when you move an object in 3D space and think you are snapping to one thing, when the program is actually snapping to some object in the background. Very difficult to control. A program like ACAD or Rhino, which has multiple windows from different perspectives, is a lot easier to follow when working in 3D because it helps triangulate your position. Here's a technique I use frequently when moving objects around. I try to restrict my moves to the 2 dimensions of the working plane. When snapping, I place a 2D object, such as a 2D locus, in the foreground. When a 3D object snaps to a 2D object, it cannot change its position along the axis normal to the working plane (normally, the screen). This will give you a lot more control. It also helps to create temporary groups, and enter them so that you limit the number of objects you are dealing with. VectorWorks has its plusses and minuses, but I think its 2D-3D interface is better than most. Best of luck! [ 05-15-2002: Message edited by: P Retondo ]
  25. Thank you all for your expert advice!


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...