Jump to content

ThreeDot

Member
  • Posts

    167
  • Joined

  • Last visited

Everything posted by ThreeDot

  1. Although it seems no cares much about this, here is an example showing similar dashed lines in AutoCAD. See how much nicer they scale and center themselves between endpoints. To me, it seems like CAD 101.
  2. In addition to a better dash editor, dashed lines should scale better between their endpoints. Simple dashes scale okay, with equal dash lengths at each end. However, more complex dashes don't even try to even themselves out.
  3. Completely agree propstuff's comments. He mentions color for presentation, but a better color picker would be super for regular drawings as well. I have trouble quickly selecting the correct color because the swatches are too small and there is no way to identify them other than counting columns and rows. - Colors should also be identifiable by color ID, RGB, or other directly in the color picker. Easier to identify. - Color picker swatches are too small to be usable. - Agree with propstuff, put color books in a resource folder. Allow them to be imported and exported as a resource. ThreeDot
  4. Yes, consider this another strong vote from me. Updates with the dashed lines are long overdue. I agree with all previous posts. ThreeDot
  5. I'm running a Dual 2 GHz PowerPC G5 with 2.5 GB RAM and the original GeForce FX 5200 graphics card. Performance for me is okay, but large files tend to bog down and overall speed is not as snappy as AutoCAD on similar size drawings and hardware. Looking at an actual drawing has certain advantages (smooth resolution, overall perspective, etc.) over viewing the same drawing on-screen (smaller format, pixilation, anti-alias blurring, etc.). I think visual aids are absolutely required when drawing on-screen. It's extremely useful to have objects, classes, or layers color coded so the dimensions can easily be distinguished from lines, or Class 1 distinguished for Class 2, etc. I don't think VectorWorks WYSIWIG approach works very well as currently implemented. If I want my output to be black and greyscale, then I cannot have ANY color represented on the screen. On the flip side, if I have color on-screen and want to print black only, I cannot also have greyscale on-screen. This seems like a serious deficiency. I think, at minimum, VectorWorks should provide finer grain user control for printed output. Perhaps an additional column in the Class dialog that would allow a user to choose print output per class "NonPlot", "Color", "Black", or "Grey". Conversion should happen automatically on print, unlike the current "Black and White" setting which requires an extra trip to the preference dialog. ThreeDot
  6. Katie, One must have a method to understand line weights on screen, in anticipation for how they print. There are two popular methods. 1. Allow color to represent line thickness. A user sets up a table mapping on-screen color to printed color/thickness. The software will then correctly make the conversion when printed. VectorWorks does not (really) support this method, so... 2. Emulate the output line weights and colors directly on the screen (WYSIWYG). It's a very direct and sensible approach. I find it amusing that one the most basic aspect of any CAD software (virtual emulation of drawing), here carries a "slow" warning. So, if method 1 (poor supported) and method 2 (Slow) are not practical. How do you recommend I visualize printed line weights? ThreeDot
  7. You're right, I don't really like that solution. Apparently Nemetschek doesn't think too highly of it either...
  8. I am also looking for an answer to this question. In my case, I use class colors to indicate line weights. Just before printing, I switch to "Black and White Only". The problem is that I use greyscale shading with some light lines. These are converted to pure black when printing, losing the 'grey'. Does anyone have a solution to this? Thank you, ThreeDot
  9. Automatically, like InDesign or Quark, no. If you're sending a non-standard font be sure that you are not violating your font license. Most font are purchased with restrictive non-distribution agreements. Matt
  10. I had similar trouble/complaints about title block fonts. Refer to my post: "custom title block fonts" Matt
  11. As noted by panthony, VW has spent a considerable amount of time (no doubt) working toward a bifurcated model-sheet workflow. However, they just don't seem to get it... Regress to MiniCAD running in parallel development to early versions of AutoCAD. Complaints from many AEC professionals transitioning from drafting tables was that AutoCAD was too abstract, there was too great a learning curve, unfamiliar territory. Entry MiniCAD. An electronic drafting table with a workflow familiar to drafters. The page was primary. Then surprise, drafters adopted and co-opted technology, became familiar with a new way of working. An abstracted way of thinking about drawing, their buildings, issuing documents. AutoCAD, with its split MS/PS, becomes comfortable. But it's a hassle managing two distinct and separate sets of data (drawing and annotation). Meanwhile, development continues on VectorWorks, which sees drafters becoming more CAD abstract-saavy, and acquiesces toward the AutoCAD methodology to implement MS/PS-esque Design and Sheet Layers. As VectorWorks spends a great amount of effort, mucking the water, grafing on more layer types, viewports, annotations, and places to set scale, AutoCAD managers, users, and standards are returning to a more simplified MS/PS workflow. One that promotes drawing AND annotating in MS while simply printing from PS. Drawings and annotations are now logically re-connected. And we're left with VectorWorks pushing a half-baked MS/PS variant, and we have no choice but to follow their lead. Examples: A. Design Layers and Sheet Layers are both scaled. VW officially recommends that you scale your drawings in both places to help maintain consistent font scaling. Why? B. VW recommends that dimensions be placed as viewport annotation...thereby eliminating associative dimensioning. Why? C. How many places can I add dimensions now? In Design Layers, in Annotation, or directly on the Sheet Layer. What is the point of this? There should be a single direct way to dimension a drawing instead of spending time working out the pros/cons of what to annotate. I don't want VectorWorks to be an AutoCAD clone, and I'm happy to move past MiniCAD. I just want Nemetschek to find an simple 2D drafting and 3D modeling methodology and develop it with some rigor and common sense toward the end user. It all seems a little flaky and reactionary as is. Enough for now...
  12. I'm customizing one of the provided VW12 title blocks for my own use. A couple of questions: 1. Can I use more than one font? Say Helvetica Neue 45 Light, 55 Regular, and 65 Medium. The inserted TB defaults to a single font when inserted on a sheet. 2. Can the TB font and style be locked in the sheet to prevent changes? I don't like the the TB text can be selected and changed so easily. Thanks
  13. I use... A0.x Cover, General Notes, Symbol Key, etc. A1.x Plans A2.x Reflected Ceiling Plans A3.x Exterior Elevations A4.x Building Sections A5.x Details A6.x Interior Elevations A7.x Kitchens, Bathrooms, etc. A8.x Cabinetry and Millwork Details AE1.x Power, Communications, AV AE2.x Switching Plans D1.x Demo Plans D2.x Demo RCP D3.x Demo Elevations and so on.
  14. I agree that AIA standards are a must, however I only partially appreciate the hyphen nesting function. As an Architect, my classes are always A-this or A-that. So, when I open my class menu I have an inevitable and unnecessary extra click to access the "A-" nest. So, I don't like the "A-" nest, but I do like the "Wall-" or "Flor-" nests. I really wish this feature could be toggled or customized in preferences.
  15. Please help, I'm just getting started with VS and am having trouble. While I have visions of script grandure, the basic premise of what I want is: a script that will select all objects of criteria FP color on all layers in a drawing and SetLW. PROCEDURE LWSync; VAR h:HANDLE BEGIN h:=SelectObj(PF=2); WHILE h<>NIL DO BEGIN; SetLW(h,12); END; RUN(LWSync);
×
×
  • Create New...