
Lag can also occur when you add mates, when editing a part and going back to an edit assembly mode and everything just locks up, or just general lag when trying to rotate, zoom in and our, or even just holding your mouse over your assembly. Maybe SOLIDWORKS locks up or goes to a white screen. When we’re talking about an assembly that is slow to work with, what we’re talking about is it being laggy when we change from one window to another. Dealing with lag in your SOLIDWORKS Large Assembly But now we’re ready to move on and talk about an assembly that is slow to work with. These are significant savings and times that you too can achieve just by following some of the steps that we covered earlier in this blog series. So while it took twelve minutes and thirty seconds to save this assembly the first time when we were fighting some of those battles, what we find now is we can open the assembly, we can take one of the files, move it so the assembly is changed, we can save the assembly and it takes only about 6 seconds to save the assembly and move on with our work. This is really useful information for cutting down the amount of time it takes to open an assembly and this is also going to apply to the amount of time it takes to save as well because we’ll no longer be fighting when we go to save the assembly by saving it as an older version or saving it with only read access to the files, or saving it across the network. I ended up cutting the total time down to just about twenty seconds just by following the steps talked about in previous blogs. After that, we closed the assembly and we toggled on the option to load components lightweight. I went through the assembly and moved all the files to a location where they were getting the fastest possible data connection, opened all the files in a resolved state and made sure we had read/write access, we looked for any files with an unusually large file size and shrank those files, we resolved any errors in the assembly, sub-assemblies, and part files, and then we saved the assembly and all parts in the current version of SOLIDWORKS.


Earlier in the series, we opened the assembly with a bunch of older version files and I was opening it from a network and it took seven minutes and thirty seconds to open. In my SOLIDWORKS Large Assemblies blog series, I’ve talked about how large assemblies can be slow to open, slow to work with, and slow to save.
