-
Website
http://www.solidsmack.com/ -
Original page
http://www.solidsmack.com/solidworks-performance-and-memory-help/2008-07-30/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Charles Culp
34 comments · 2 points
-
Brian
51 comments · 9 points
-
MatthewWest
32 comments · 2 points
-
Bruce Buck
72 comments · 6 points
-
Dave Moore
49 comments · 1 points
-
-
Popular Threads
-
Friday Smackdown: Mechtronic Melee
1 day ago · 2 comments
-
Ask The Reader: Are You Upgrading to Windows 7? {Poll}
1 week ago · 21 comments
-
The Rockin’est LED PocketWatch Mod EVER, Designed With a lil’ SolidWorks
3 days ago · 4 comments
-
FreshFiber’s 3D Printed iPhone Case Puts the Fancy in Your Pants
2 days ago · 2 comments
-
Get Into SolidWorks World 2010 for Free. No Beet Throwing Required. #SWW10
5 days ago · 5 comments
-
Friday Smackdown: Mechtronic Melee
Will the future of solidsmack be STsmack
My sidenote was to slap the mentality that one or the other doesn't require as much thought (time) because of the way history of features is implemented. I've used a direct history free modeler, started off one way and because of a change had to start over completely. In a history based model I was able to go back make the change, some adjustment and keep going. It all requires some thought. don't ya think?
Instead I'm using "shaded" view (instead of "shaded with edges"): it might be not the best to work like this 100% of the time, but I like to work like this most of the time and change view only when I need to. Also I realized SW crashes less when I'm using this option.
Another trick is to set configurations and suppress the heaviest components or features, depending on what you're working on. For example, I like to make an "envelope only" configuration to all my assemblies and I suppress everything except for the outside components, usually it's comfortable to design jigs like this.
If your model is completely stuck, you should turn it into parasolid (which deletes all its history) for it to run.