Anyone else having issues with terribly slow mating in large assemblies in SW2011? I'm on 64bit Win 7, 6G ram, nVidia FX1800.
Looking for setting changes or anything that might help.
Will this help?
First, turn the setting Nick showed to "off".
Next, make sure you aren't putting too many mates in your assembly. If you get up close to 200 in any assembly, try and see if you can use subassemblies to reduce the number of top-level mates.
Then, go to Matt Lorono's site and download all the mating macros by handleman (coincident, concentric, parallel, and distance). Map those to shortcut keys.
The reason mating gets so slow is that when you make selections, SW evaluates them to see what mates are valid for the selections you made. As your assembly grows, SW takes longer and longer to do this evaluation. 95% of the time (or greater) you want a simple mate, and you know yourself ahead of time what type of mate you want. You don't need SW to sit there and decide which mates it'll let you do. The macros will add the mates quickly - no animations, no analysis, just mates. Fast.
Thanks for the links Josh: will have a look.
In answer to the original question: it's not just you! Solidworks have admited its a bug and have provided an SPR as "critical" so hoped to see it fixind imminently. It seems to be perculiar to large assemblies only: by "Large" I mean to assemblies that take up a big space rather than have a large number of components in.
"The time taken to add mates between the two faces pre-selected in SW 2010 was about 12 seconds and in SW 2011 it was 23 seconds. We have confirmed this as regression and referred the issue to the Development team with reference as SPR 590652 "
My times are a little different to this: more like 3 seconds in 2010, 30 seconds in 2011. Either way its killing my productivity.
If you want to see this fixed quickly: search for "590652" in the knowledgebase in the customer portal: select "notify me when this is resolved" and you will be added to the SPR.
I'm suprised the forum didn't light up with this one...
OK this partly explains my troubles recently. i thought there was something wrong. But also it eludes to something else also being wrong because it doesnt fully explain other issues i'm having.
i recently re-visited an old assembly i made back in 1998-2000. Back then i could dynamically move this rather large assembly containing~700 parts and numerous sub assemblies of which many had flexible sub assembly options enabled even on multiple sub assembly levels. Back then it all seemed to at least work when you dragged components (think car suspension and steering).
Now i've revisited the assembly to try and update it and "clean" it up a bit and try to get a better dynamic motion visual.... and it just WILL NOT do it. Takes FOREVER to move after you click to drag and thats if you're lucky enough that SolidWork's thinks you can move the parts even tho you've mated them technically correct etc. It jus twon't play ball. Very frustrating.
I got jack of it and opened up a backup of the old assembly and to my suprise it dynamically moves far better then the newly created ones. Its got me stumped! But no doubt this has something to do with it.
SWCorp really need to fix their mating issues. It really is a joke. They are far from solid and reliable... hell they aren't even predictable and thats the whole reason for their existance in the first place! *head shake*
Any resolve in sp 3 with this? I've been dealing with this issue since December and I really hope Solidworks can fix this.
The only thing I see about your system specs that might be suspect is
your memory amount. I was running 12 GB on 64 bit XP with 2010 and
it ran fine. I know different OPS and version but try adding more memory.
yeah me too, but after upgrading too 2011 is when the issue is being seen.
I am thinking I had better stay with 2010. I know 2010 started out shacky at best
but but became pretty stable after SP4.0
Looks as though 2011 is going down the same path from what I am reading on this forum.
The same assemblies that worked OK in 2010 are now very slow. It is definitely a "dis"-improvement for 2011. Unfortunately, once you take the plunge you must continue to swim...
We work with large assemblies... always have and always will. I hope that Solidworks will continue to work with them too.
Sorry to here that you are at the point of no return.
What you might want to check out is under the Solidworks World portion of the forum
under sessions there are handling large assembly presentations. I saw a few myself
at SWW2011. Maybe they might relieve some of your pain.
I just upgraded to sp 3.0 an still no resolve.
I feel your pain man......
Give me back 2001+. Imagine how that would run with the computer power we have today?
I know... I know. It probably wouldn't run at all on Win 7 64 bit blah blah. But I like to dream.
Give me back 2007. That was a very stable version from start to finish
from what I remember. All down hill after that.
I'm having some problems with an older assembly (2007) where I have recently added some in-context references. Now the incontext part shows a perpetual rebuild symbol, and adding or even reordering mates causes the whole thing to rebuild, which takes about 30 seconds. I'm using SW11 sp3.
Okay I received a large assembly from an outside source that was drawn up in solidworks 2011. This assembly is using some of our companies components that I've drawn up here in house. I am not seeing the slow mating in this assembly. I did a little testing, I brought a large assembly file (35mb) into an empty assembly and mated it up, that took 30 seconds per mate. I then brought that same 35mb file into the "good" assembly i recieved from an outside source, which also has a different 30mb file in it, and it mated right up with no wait time. So maybe we can narrow it down a little further with that info? Maybe it's my assembly template I'm using? So after typing this I went to the solidworks standard template and brought the 35 mb file in and it mated right up. It looks like it has something to do with the template's. I'm going to investigate further, but if you have time to look into it then i would go that route.
Definetly templates on my end. I can bring a "slow" assembly into a new assembly template, edit the "slow" assembly and everything is fast and smooth. Open that "slow" assembly up by itself and it's slooooooow. So work around for now is to just take the top level and put it into a new assembly template.
Tim, do you mean an .asmdot type template?
If you do, can you post the old and new for comparison?
What happens then if you dissolve that assy in the new assy? Does the problem reappear? Maybe it's an issue not with templates, but with the other mates that are already in that assy. Putting that assy into another one forces all those mates one level down and out of consideration. But then you mention editing that assy inside the new upper assy and still seeing a difference. I wonder if existing mates are being considered differently in the two scenarios. Do you see the same overall situation with an assy with only a few mates?
Okay this may be some sort of twighlight episode. Yes I was talking about the .asmdot file, once I figured out that was the cause and created my new assembly templates, I deleted my old ones. Then you asked for the template files, so i went into my backup and restored the template files and now they work just fine. My head is spinnging right now, 4 months of trying to get rid of this and now I can't recreated it! I've done a pack and go on an assembly file that has this issue. There is supposed to be 2 full assembly doors in here, but do to file size i left them out. You can still see the delay in mating, now imagine it being 10x worse with the two large files included. Now if you put this assembly file into higher level assembly and edit it, there won't be a problem. S211024A01.SLDASM is the highest level assembly
OK, I'm getting about a 2 second delay, so if the full delay really is 10x worse, I can definitely see the problem.
Minimum delay seen in a new top level assy.
Okay in my .asmdot file i've created some custom properties, one of those is the material. Well there isn't a material in an assembly file, I think when I created these templates I just used the same properties between the .prtdot & .asmdot. This custom propertey has never caused as issue before upgrading to 2011. So this is what is causing the problems, once I delete the "material" row in my old assembly files everything runs smooth.
I've been watching this thread for awhile, but am still on SW2010.
You're talking about File->Properties...Custom and/or Configuration Specific tabs, right? And just having a Property Name of "Material" is causing issues? Granted, assemblies don't really have a material per se, but I've always used the Material property to automagically fill in the drawing (which are obviously common regardless of assy or part) fields. For assemblies the Material is typically "SEE BOM".
Man, that's bad.
Yes those are the properties I am reffering too. Here is a screen shot, row 8 is my material propertey. Now I don't have to remove the entire row, I only have to remove the "value/text expression" equation. Once I remove that solidworks is not trying to figure it out.
Ah. You have yours linked to an actual SW property. Mine is just plain old text, so shouldn't (?) be an issue. If I ever go to 2011.
Retrieving data ...