Jump to content

P Retondo

  • Posts

  • Joined

  • Last visited

Everything posted by P Retondo

  1. One of the few big advantages of AutoCAD over Vector Works is their Paperspace capability. This allows us to compose a sheet from various elements of a project, displayed in any location on the sheet and at any scale desired. See complaint by CARMELLHILL2 in the main discussion forum about plotting multiple floors on one sheet. Like most of us, he probably arranges his layers so that all floors are registered with each other. "Pulling apart" these overlaid layers is not possible in VW, no matter how you set up a sheet. It seems to me that you could fairly easily provide us with this feature. The layer is printed on the page according to the way (0,0) is related to the page. Just allow us the ability to break that link, and to customize the relationship of a layer's origin to the page, for each layer. This should be a graphic tool, like dragging a thumbnail of the layer's (or multiple layers') content around a representation of the sheet. Then, allow the "scale" of each layer to be set differently in different sheet setups - you have printer scaling, this might be an extension of the same algorithm. Both of these features should be extensions of the existing sheet setup dialog box - a "Drawing Setup" within Sheet Setup. Do this, and you will have something better than AutoCAD's convoluted Paperspace. [This message has been edited by P Retondo (edited 07-28-2001).]
  2. Doing a particular (complex) solid subtraction in a file originally created in VW 8.5.2 took about 8 seconds in VW 8, and over 30 seconds in VW 9.0. I'd say that is significantly slower. Tech support told me they thought it was the change from 32 bit to 64 bit accuracy. I said I could do without 64 bit accuracy if that's the price we have to pay. But I've also noticed that the translation from VW 8 to VW 9 is very quirky, and perhaps objects native to VW 9 don't have this problem. Has anyone else tried similar comparisons?
  3. I agree with Donald. Suppose you have a series of parallel lines you want to extend to some reference line, and these lines are so close together you can't select them properly unless you zoom in - then you lose sight of your target reference line, and can't use the tool!
  4. I use Set 3D View quite a bit, and since I'm in the process of switching to VW 9, I was motivated to try it immediately. The command works fine for me (on a PC) in both perspective and orthogonal modes. VW 9.0.1 Win 2000 PII 333
  5. Donald, I have not experienced the problem you describe. For example, my rounded rectangle tool is nested under the ordinary rectangle tool. Whichever one has been selected and is displayed on the palette is activated by the keyboard command <4>. When viewing all of the nested tools by clicking on the little triangle, each is tagged with a "(4)". Perhaps your system is different from mine: VW 9.0.1 (worked the same with 9.0) Win 2000 PII 333 [This message has been edited by P Retondo (edited 07-28-2001).]
  6. Dear Andrew, Thanks for your thoughtful input on this issue. I don't have a dual processer, but if I did I would want it for the rendering operations and for converting 3D objects to lines (same process). If NNA could write those functions for a dual processor, I think you would make those folks who have them happy.
  7. Dan, Alan, If you are talking about the fill patterns assigned through the attributes palette, those have always been 72 dpi, regardless of scale or printer resolution. I've often wished for a more powerful and sophisticated fill capability.
  8. Import data file for property line description - great idea! [This message has been edited by P Retondo (edited 07-16-2001).]
  9. Thanks, Caleb, for the tip on using <Esc> key. This does exactly what I was looking for. I note that this bit of information does not seem to appear in the User's Guide. One of the more frustrating things about dealing with VW is that the program behaves in ways and contains features that are not adequately explained in the manual. In participating in this forum, I have noted that many people complain about the program because they just don't have the information they need to use it. NNA should get a specialist to work with all the tech support folks and engineers to come up with a complete manual. By the way, I find that using <Esc> after entering new information in the object info box does not cancel the change. Additionally, it has a great advantage over clicking in the drawing space. Clicking in the drawing space is interpreted by the program both as a shift of focus and an initiation of the command currently active (e.g., draw a rectangle, edit it, click in the drawing space - you will have to finish drawing a rectangle you don't want before doing anything else!) I agree with Raymond Mullin that <Enter> would be a more natural and logical choice as a keyboard command to perform this function. One expects that using <Esc> would cancel all edits, which in fact it does not do. -Pete Retondo [This message has been edited by P Retondo (edited 07-09-2001).]
  10. If you have snap to objects on, when the cursor is snapped to a 3D point the coordinates appear at the top of your screen. Or, you could put a 3D locus at the desired vertex and read off the coordinates in the info palette. With the second method, you can choose whether to see coordinates in X,Y,Z or I,J,K system. [This message has been edited by P Retondo (edited 07-02-2001).]
  11. When creating a text string, the "enter" key (on the numerical keypad) takes you out of that command so that keyboard commands are no longer interpreted as part of your text string. The same thing should apply to editing values in the info palette. I can't tell you how many times I have pressed "enter" after editing a number in the info palette, then pressed "x" to get the selection tool - only to find that I have just tried to assign "42.67x" as the length of something!
  12. Sorry to jump in with a possibly stupid suggestion, but have you tried defining another working plane aligned with your i,j,k vectors and performing a rotation using that coordinate system?
  13. This may not be the best possible technique, but you can close each polyline using the checkbox in the info dialog box, add vertices if necessary to make the two intersect, then use the add surface tool to combine them into one surface. Turn off visibility of sides you don't want using the 2D reshape tool. (I assume that you meant to say you're using 8.5.2) [This message has been edited by P Retondo (edited 06-23-2001).]
  14. Printing perspective views used to be simple with my HP 722 in Windows 98 and VW 8.5.2 (or was it VW 7?). The perspective was automatically scaled to fit the sheet, and only the view showing on the screen printed out. Just get your perspective set up, then print. Now, with VW 9.0, an HP 1220C and Windows 2000, I have to set up a single sheet page size, scale it and move the page to center the view. As though this weren't enough trouble, it will print a larger view, to the extent of the sheet, instead of what shows in the window. I solve this by masking the rest of the page with a window around the perspective view that shows on the screen, a pain. This problem is occurring with a document originally created in VW 8.5.2 and translated to VW 9.0. By the way, if you choose the wrong order of doing the steps above, you can get into trouble. You must set the scale in the page setup dialog box BEFORE switching to the perspective view, otherwise the effect of setting scaling changes the view on the screen radically. [This message has been edited by P Retondo (edited 06-18-2001).]
  15. Shaun, et al., I have a HP 1220C. After following Caleb S.'s recommendations, have had successful printouts of various documents at various scaling sizes. I'd say - works great! I use a Dell PII333, with 192MB RAM. One difference that could account for different experiences - I use Windows 2000. One problem. Printing perspective views used to be simple with my HP 722 in Windows 98 and VW 8.5.2. The perspective was automatically scaled to fit the sheet, and only the view showing on the screen printed out. Now, I have to set up a single sheet page size, scale it and move the page to center the view. As though this weren't enough trouble,it will print a larger view, to the extent of the sheet, instead of what shows in the window. I solve this by masking the rest of the page with a window around the perspective view that shows on the screen, a pain. This problem is occurring with a document originally created in VW 8.5.2
  16. Andrew, Thanks for your response. You point out a challenging aspect of making this aspect of 3D work better, but consider this. If you rotate an object out of it's original axis, then enter the edit window, that window must place the originating object(s) in some point in space. Why not place them at a point that corresponds to the same relative location in the Working Plane currently active? Then, for example, when you are looking at a rotated extrusion from a working plane defined normal to the extrusion face, and enter to edit, you will be looking at a 2D object that relates to the Working Plane in the most useful possible way. Sure, this will take a couple of days to code and test. But it makes the program REALLY work well. -Pete
  17. Create an extrude from a 2D shape, then move the extrude. When you want to edit the 2D shape, you will find that it did not "move" with the 3D object. This makes it difficult to use the full potential of your 2D-3D interface! If you want to edit your original shape using the spatial context of the 3D object's current position by drawing objects then pasting them in place in the edit window, you're out of luck. This technique is the fastest and most reliable way to work with 3D objects. The same problem plagues the use of boolean solid operations. It would be a powerful improvement to the program if all objects associated with a 3D entity moved with it, and always occupied the same position with respect to the origin. In other words, if you extrude a square into a cube, then move it 2 inches along the x axis, you should be able to enter the edit window for that cube and find that the square from which it was extruded has also moved 2 inches along the x axis.
  18. Caleb, Yep, it works, but you need to know to do the following: enter scaling in page setup, select the output page size desired. Go into Set Print Area dialog box, and click on a single sheet. Check to make sure your printable area numbers make sense. While I have your attention, since it seems you work for NNA, have your programmers figured out a possible way to speed up the operation of 9.0? I have documented a solid subtraction that takes less than 10 seconds in 8.5, and more than 30 seconds in 9.0 - due apparently to greater accuracy (unneeded, in my case).
  19. Caleb, thanks, I'll try this and let you know if it works!
  20. "I realize you're not using VectorWorks 9 right now, but print scaling is is one of VW 9's features." - Caleb Strockbine Caleb, I had VW 9 up and running, and it could not scale printer output. Scaling is discussed in the manual, but only in the context of a printer driver that provides a scaling utility. My printer, an HP 1220, doesn't do that as well as some other printers in that regard, so yours may work fine. It appears to me, though, that VW 9 does not contain its own scaling utility, such as AutoCAD contains. If you are able to access a scaling dialog box that belongs to VW, not to the printer (look in the window header to see if the printer is named there or not), please let me know and I will give it another try.
  21. Haven't tried the new VW 9 extrude along path tool, so I was interested in this comment. I have used AutoCAD's, and the kind of problem you are experiencing happens in AutoCAD when the cross-section being extruded "doubles back" on itself geometrically when passing through a curve that is too tight. When you experience the error, try extruding the same shape along a much gentler curvature or angle. If it works in that case, then most likely your problem is that the path contains "kinks" that the extrusion algorithm can't resolve.
  22. Is there anyway you can add a feature allowing the program to scale printer output to allow, for example, a 24x36 sheet to be printed on an ordinary printer? I have an HP 1220C, which handles 13x19 sheets, max. When using zoom at 50% and the largest possible sheet size (e.g., 13x19), my output consists of 4 pieces of the drawing printed on 4 sheets at 50%!! Apparently I can't print at 50% because, in their wisdom, VW programmers have chosen to automatically tile the output when a sheet smaller than the "page size" is selected within print setup. HP provides the zoom feature, but not a 24x36 sheet size option. I don't recall having this problem working on a Mac platform with a HP 4ML printer, so my particular issue seems to arise using Windows (2000) and/or my particular printer. Surely there is a way to guarantee the ability to scale output regardless of printer or platform by scaling the printfile (like, gulp!, AutoCAD does - I can do the above referenced printing task easily in AutoCAD).
  23. I use an HP1220C with VectorWorks 8.5 (tried 9.0, shelved it). Both print okay, but the lack of a scaling utility in VW is a sore point. HP's "Smart Zoom" utility doesn't work with VW because VW automatically tiles a document according to the paper size selected in the printer driver. So, for example, if you want to print out a 24x36 document at half size, you're out of luck. The 1220C driver doesn't offer a 24x36 paper size, so VW tiles the document into at least 4 sheets. When you try to print out at 50%, you get four 50% size sections of the drawing. The work around is to change layer scales - a real pain, but doable. The printer itself is fast, quiet, and gives great output. It can also take a 13x19 sheet. VW programmers take note! You need to provide printer output scaling!
  24. Dear scubohntr, I share your frustration with VectorWorks documentation. It is far too sketchy. Here is a pobable solution, though, to your problem: you are working an a map at a "large" scale, where the symbol you are trying to use is at a "small" scale, like 1/4" = 1'. Put the symbol on a layer with a small scale, and it will show up in properly sized. This is a problem one wouldn't encounter in AutoCAD, which uses a completely different system for these things. VW responds to scaling a symbol, as opposed to an ordinary object, as an illegal command and just does nothing in response. If you convert the symbol to a group, however, it can then be scaled using the scaling tool.
  25. After two days of trying VW 9, encountered many bugs - you will no doubt work through them. Sluggish performance is not a bug - it's a basic design issue. 3D solid operations, doors and windows, simply changing the width of a wall object, all take unacceptably long periods of time. If you have a strategy to get back at least to the user performance of v 8.5, let me know. Otherwise, can't use VectorWorks in the future.
  • Create New...