I'm running 2003 for production work and 2004 only experimentally.
Just finished modeling a relatively simple part with a single loft (between one circular and one square profile) sitting on top of a circular extruded base.
With the same part modeled natively in both 2003 and 2004 (programs running side by side simultaneously) and shelling each, I then asked the respective programs to simply edit the loft feature (with no changes) and then rebuild.
In 2003 I can open the feature for editing and rebuild in a flash compared to performing the same operations in 2004. In fact, I can repeat the edit/rebuild in 2003 MULTILPE times while still waiting for2004 to complete the rebuild for the FIRST time.
Verification on Rebuild is NOT checked ON in either version and I can't think of any system settings which are set differently to any degree that would account for the "ball and chain" performance in2004.
Even with 2003 shut down to free up memory, 2004 is doggedly slow in the edit/rebuild of the simple loft.
Switching (temporarily) to the use of Software OpenGL reduces the delay, but I can't work this way on a regular basis.
But the plot thickens! - If the part created natively in 2003 is opened in 2004, its features can be edited and rebuilt rather speedily
- Just as if it was still being worked on in 2003. Even after saving the 2003 version part (converted to 2004 format), the "imported" component retains a major performance advantage.
Apparently, modeling from scratch in 2004 adds some mysterious "baggage". For reference, the file sizes are:2003 native - 192kb 2003 converted to 2004 - 537kb 2004 native 755kb
SolidWorks should try to capitalize upon a marketing campaign that focuses upon delivering the FASTEST and most ROCK SOLID performance possible and ease up on rolling out new functionality, if it can't be added without overall burden!
I'm eager to use 2004's new capabilities day in and day out; however, the current program environment is just not ready for prime time.
Per O. Hoel