Speed up the reconstruction of SW animations

Hello, I'm looking to improve the calculation speed of SW standard 2013 animations: in the case of animations without necessarily many components or exceptional rendering, I have calculation times that I find very long. I tested by increasing the RAM, VERY disappointing result. My configuration:

Dell Precision M6700 with SSD HDD for SW, core i7 @ 2.7 Ghz, Nvidia K5000M video card with 4GB of dedicated memory.

I tested on an animation in progress that lasts 2'15": with 16 GB of RAM the calculation time is 7' 25''. Exactly the same reconstruction with the same programs open in the background (just a file in the notepad and two one-page pdfs, not very gournmand) on the same PC with 28 GB of RAM: 7'00". A 25-second gain for 12 GB of additional RAM, not great.

My biggest problem is that for every change in the animation, I have to recalculate everything, it makes for a very, very bad productivity.

Do you have any suggestions on which parameters to change, even if only during the time it takes to build my animation, even if it means changing them at the time of the final calculation? I've already reduced the number of images but below that, I'm afraid of having conflicts in my constraints that go from active to deleted.

Thank you in advance.

Sebastian.

Hello

 

What do you mean by "with SSD hard drive for SW"? Do you have two different records?

 

I wanted to offer you the ReadyBoost (increase the RAM simply by plugging in a USB key), but if you already have SSD, I don't know if it's really useful! Finally, it doesn't cost much to try, you just need to have a fast and empty USB key.

 

http://fr.wikipedia.org/wiki/ReadyBoost

The computing time is largely related to the performance of the processor (2.7GHz is a bit light), I'm even surprised that just by adding RAM you have the slightest gain in computing time.

2 Likes

Hello

I have also noticed that contradictory or constraining constraints to a movement can require very long resolution times.

I think that by optimizing the constraints (limiting a relative motion to 2 ss together rather than asking the system to find it for example) can play on the computation time and limit these problems.

Roman

Hello

 

What type of animation do you do?

Complex cutscenes or camera animation and part movement?

In the first case of complex kinematics, SW is there for this and unfortunately we are dependent on the time of computation of the constraints.

Otherwise I can only advise you to test SolidWorks Composer which is much more practical and fluid to use for classic animations.

 

@+

2 Likes

Hello

Thank you for all these answers. I use SW on an SSD and my design files are on another SATA drive. Unfortunately, I don't have a fast USB stick to try ReadyBoost.

Well rated for the processor, but on a portable station, I don't have much possibility of upgrading the processor...

As for the constraints, the only one that runs  throughout the animation is a trajectory constraint along a 3D sketch for which I vary the position of a point throughout the animation. It is true that some components are positioned in relation to this point (vertical to a point evolving on a 3D sketch). I don't think we can put this animation in the complex category.

In short, I have to animate a crane in the construction of a building. I opted for the solution of creating the trajectory of the crane hook and following the boom with reconstruction of the cable between the boom and the hook at all times (as I don't have a simple solution to manage the cable whose length varies). The cable is therefore a part created in the assembly.

If you have examples of this type of fluid animation, I'm interested (with movements in all 3 directions and variable length elements).

Ideally, an assembly statistics function in the same spirit as function statistics would be very useful to know which function/volume is a big computational time consumer.

I'll try it out as soon as possible by removing some components, but for now, I'm facing another problem: appearances always come back after I delete them in the assembly, as soon as I rebuild. I'll look on the forum if it's a known problem and if not, open a new thread.

Kind regards.

Sebastian

Regarding Composer, it's a reflection in progress, but my banker is not warm. And I would like to see in use not just to animate exploded but to make components move / appear / disappear.

It's very interesting this information about the equipment

A group should be formed on the subject