Jump to content

CADD Nark

Member
  • Posts

    67
  • Joined

  • Last visited

Everything posted by CADD Nark

  1. .exe is just a self extracting Zip file. if you're on a Mac, use Stuffit Expander to open the .exe file. there are a couple of problems with using the free .dxf stuff out there on the 'net is that the dxf probably has no color assignments (not to mention class assignments). the shear number of points and polygons that make up the mesh (or model) are so extreme in number, your rendering time is going to seriously increase. you can take the time to fix them if your budget can stand that big of a hit (time=money). i have found useing flat extrudes and mapping a texture (image file) to them is the way to go. although VW doesn't do this very well. check out Artlantis.... WAY faster and better results than RW. hope this helps.
  2. i have found that like rendering, reducing the memory allocation to 1 meg over the preferred setting (on the Mac) will help reduce the "out of memory" errors.
  3. and the techs/moderators for this group to answer our questions??????????
  4. you can also use QuicKeys to simplify and speed up repetitive tasks.
  5. as you know, the Export to DWG function works well for the perfect VectorWorks document (i.e.- perfect Class, Layer, Line weights, etc.) but, in reality the average VectorWorks document is not perfect. before we export to DWG, i have a Vectorscript that we run on our documents. the problem i'm having is this; i want all the text in any given document to have the same color (so when translated it will have the same line weight assignment in AutoCad). i have found that when a Layer contains more than approx. 10,500 objects, Vectorscript will not perform the functions even though it returns no errors and executes. as long as the Layer has less then approx. 10,500 objects, it works great and will perform the line weight assignment function in my script. can you give me any insight to this?? VW 9.0.1 on Mac G4/500 running OS 9.1
  6. Dellboy,in reply to your problems inporting ACAD files, you must be doing something wrong. at our firm, interchangability with ACAD is a must and we exchange files every day with consultants across the country using ACAD. when importing, be sure to set the size of the page first. i use 30x42 when i don't know what the sheet size is that is being sent to me. when you begin to import, in the Primary Settings tab; Model Space Scale, do not use the setting for the Fit To Page. i use a generic scale depending on the drawing (i.e.- if it's architectural, use 1/4" scale....civil, i use 1:30) for 2D and 3D conversion; if it's a construction document, use 2D only. this is just my practice and may not work for you but, i suggest you give it a try. good luck!!! by the way, VectorWorks stomps the crap out of ACAD!!!!!!!!
  7. I may be overlooking it but, has it been axed from VW 9.X??
  8. i agree. alot of the plug-ins are very generic and simply will not do in our practice. so we have had to make our own as symbols instead of plug-ins because we don't have a programmer. as the end users, we should be able to cutomize the tools that are provided. encrypting is good for third party developers but, straight from the manufacturer....please.
  9. can someone tell me why a VW 9 file is almost exactly 2 times the size of a VW 8.5.2 file?? this is a 3D model with 59 3D objects and the file size is 6.2 megs.... the kicker is that i only have about 25% of my model done. already it takes 3 full seconds to Enter/Exit an Object...2 full second delay to Rotate 3D View.... i know that doesn't sound like long but, to someone who is proicient with the program, this becomes a hinderance. and don't even get me started on RenderWorks... i've read the posts about the sacrifice of speed for a better foundation to build a better program....but.....having to restart my computer every 20-30 minutes is not an acceptable work around. here's an idea for Nemetschek... with all the fuss you guys are making about the "Industry" series, add a few more... like one for the Machinists who need accuracy down to the hundred millionth of an inch...a release for those who don't use any rendering portion of the current VW and rely on other software to do rendering... sorry about the rant......
  10. our office has used MiniCad since version 2 and find myself going back to old versions in order to "step up" into VW. there are some problems along the way to make you aware of. V3 stepped to V5- all lines loose weight attribute and symbols used in V3 will be usless. V5 stepped to V6 is fine and can then be opened in VW8. of course once the files are in VW8, can be opened in VW9. and you must add the ".mcd" extension for Winblows to recognize it. you can download converter versions of MC and VW to do the stepping and i think you will have to do it on your Mac.
  11. the trim tool can be worked around but, the Extend tool is vital. in our world anyway. stick with 8.5.2.
  12. it would be great if the scripts that came with VW were not encrypted so the user could modify the script and make the plug-in function as it should, not the way someone who has no clue or very limited experience on how to correctly draw a door or window. the examples of VectorScript provided in the PDF are written for fluent Pascal programmer, not the typical CAD User or Manager.
  13. i made a couple of fonts with Fontagrapher and exported them to both platforms as Trutype and Postscript (for those antique printers around the office). the demo version of the software should be able to export those fonts if you want to try it. they work great and i even use them for AutoCad translation (VW sets all custom fonts to Standard in the Export to DWG function). hope this helps.
  14. i deal with print shop all over the country and have had more headaches over PDF files.... i have learned though that most "real" print shops use Oce` plotters and can handle .Cmds (file type made by MacPlot Pro). the file sizes are much smaller than PDF and fonts are a non-issue. the HPGL/2 format is pretty universal. if your print shop is using Oce` equipment, there are 2 settings you need to make the prints shop aware of; Transpearancy = ON and Merge = ON. this settings are set within ReproDesk (Oce` software). hope this helps.
  15. on my computer (G4/500, 640 RAM). Acrobat file size is usually larger and is limited to 300 dpi (or close to it). Print ToPDF can go to 600 and above. using VW 9.0.1 and PrintToPDF 2.1.3 yeilds no problem for me. it actually prints faster than 8.5.2 and includes all fonts, and at 600 dpi!!!!!!!
  16. we have abandoned RW in favor of Artlantis. RW 9 won't even begin to render one of our files. Artlantis will even put RW 8 to shame in terms of rendering time , quality of rendering, and animations. if you ask me, make either a CAD package or a rendering package.
  17. to go along with this; when trying to resize a 3D polygon using the reshape 3D tool, it's alomost impossible to snap to a 3D locus. and the responsiveness of the cursor cues vs. actual movement of the mouse is terible (Version 9).
  18. i know the "trading post" is supposed to be in the works... has it progressed to reality yet?? i know i have several hundred image textures to contribute....
  19. i'm in my first week of testing VW 9 and wanted to share some of my findings (although some of you have already discovered some of them too) any project that you may be working on in version 8X should remain in version 8X. there is a big flaw in V9 with record field text in symbols when trying to export to AutoCad (and i've found it to happen in exporting to V8). when you have to create text for record fields, i've found that the text alignment should be set to the top left to ensure the least amount of text shift (which i have been complaing about for years). if you deal with a lot of AutoCad requrements, you should know what i mean. 9 is pretty good if you create drawings from scratch and don't have to share them with anyone else using another CAD package. but, as most of us know, that is unrealistic in the world of Architecture. i have found little to no problems with compatibility with MacPlot Pro V4.7. a little bit of fuzziness is all. we do all our plotting as saved plot files (.cmds) sent to a HP600. if you count on Scripts (as we do) to help you in complex repetitive tasks, you'll be in for hours of work in getting them updated. my AutoCad export routine, for example, that we have used since Minicad 5 has had to be updated for every new release (thank heavens releases don't come too often :-) here's the crazy thing; V8 routine will not work but, the routine for MiniCad 5 will. explain that!!! more to come....
  20. in case you haven't found the answer. if you have the nVidia card, turn of the 2D Acceleration extension and restart. your selection handles and line "ghosting" will return.
  21. i had some similar problems a while back and posted my solutions under the heading "For those with Rendering & Animation Problems " on the rendering board. check it out and see if it helps.
  22. hey Mike, if you're like me, and have to keep older versions of VW and MC on your computer, remove the prefs from the system folder and keep them in the folder that the app resides in. to launch the app with the correct prefs, drag and drop the prefs file onto the appropriate app. i have had prefs conflict before, especially with MC v2, v3, & v5. thats what i do anyway.
  23. you aren't dong anything wrong. i would suggest that when you bring in as ACAD dwg, set it to convert the ACAD layers to VW classes. i do this daily and find it to be very consistant and reliable.
  24. i've been using a wheel mouse now for several months with no problem. however, when i first got it, the driver that came with it was outdated and didn't work with most programs. Kensington Optical Pro (5 buttons + scroll wheel) ith Kensignton Mouseworks 5.50. it rocks!!!!!!! [This message has been edited by CADD Nark (edited 12-11-2000).]
  25. hmmm.....this may sound silly but, make sure the OS is the current 9.0.4 and not 9.0 . also make sure that VW is at least 8.5.1 and should be updated to 8.5.2 . we had problems with random crashes before the OS and VW update as well. something else that we had to do as well was delete the VW prefs and zap the p-ram. we're running VW on all types of G3, G4, iMac, and Cube models with hardly any crashes to speak of.
×
×
  • Create New...