View Single Post
Old 04-15-2009, 10:25 AM   #14 (permalink)
MechEngVT
Mechanical Engineer
 
Join Date: Jun 2008
Location: Richmond, VA
Posts: 190

The Truck - '02 Dodge Ram 1500 SLT Sport
90 day: 13.32 mpg (US)

The Van 2 - '06 Honda Odyssey EX
90 day: 20.56 mpg (US)

GoKart - '14 Hyundai Elantra GT base 6MT
90 day: 32.18 mpg (US)

Godzilla - '21 Ford F350 XL
90 day: 8.69 mpg (US)
Thanks: 0
Thanked 7 Times in 6 Posts
I presently work with SolidWorks 2007 on an XP workstation with a 3.2 GHz Xeon processor and 2 GB RAM. I deal with some large assemblies and while I have noticed they cause some rendering hiccups graphically I have not yet run into memory overruns or similar issues.

Prior to SW06/07 I worked in Pro/Engineer 2001, Wildfire, and Wildfire 2.0. SolidWorks is *much* easier to learn and become proficient with than any Pro/E package. That said, I do have SolidWorks 2008 Vista 32bit at home and don't use it much. It's quite a bit different than 2007 which I have to use at work so I don't want to confuse myself. Another issue with Pro/E is it uses far more memory resources and has more issues with memory management causing more frequent overruns and crashes.

SolidWorks can typically save various file types or "universal" export files to use on different systems. As far as I have seen SketchUp doesn't handle this as well (maybe Pro does?). SolidWorks is a real solid modeling program and is very capable...I can strongly recommend it if you want to hone your skills as a mechanical designer (not sure how well it would work out for architectural/civil engineering folks though...not sure what's involved in that type of work but they all prefer AutoCAD).
__________________
  Reply With Quote