2003 save time

[metman]

File is 3,126 KB.

Added several swept features and takes 2.5 to 3 minutes to save. The feature is a relatively simple cross section swept around circular holes.

Any idea why 2003 would take so long?

 

[TateJ]

I know that some swept features are more "taxing" than others - a helix, for example.

Other than that, there's a utility called UNFRAG.
SolidWorks doesen't support it, but "everybody" uses it.
Find it and try running it on your file, see if it shrinks.

tatej@usfilter.com
aka: Little Debbie's Boy-Toy
​

 

[metman]

Tate,
is this othe one that shrinks the file until you open it again and then it is right back where you started?

I will try it anyway.

 

[TateJ]

Specifically which features are you using?
Can you place a big cube around your model?
This is a sneaky way to "shrink" the part long enough to e-mail it.
If you can send it to me, I'll have a look at it.

tatej@usfilter.com
aka: Little Debbie's Boy-Toy
​

 

[metman]

Tate,
Thanks very much for your offer but it is not likely you can help. Our SW rep has responded and is also trying to help. When I attached the file I did not include some imported surfaces so it took him even longer to save it.

I inherited the model and the cognizant engineer is not quite sure about how or whether these surface files are being referenced or how to access them so that I can attach them.

 

[metman]

Tate et al,

I deleted all “On Edge ?” relations in Sketch 17 for Cut-Extrude 5 for FS 34 Frame. It saved in seconds.

“On Edge ?” relation is apparently in-context relation and referencing the assembly model.

 

[TateJ]

In-Context Relations - I have found are great during the initial design phase.
But, I usually end up replacing them with "real" constraints during the final design.
It's just my gut feeling, but I'm skeptical about their long-term stability - at least for my products.

H_o³
tatej@usfilter.com​

 

[metman]

Tate,
You are spot on. That is how I do it also and cannot imagine how anyone could have any reasonable success otherwise unless posibly with a very simple assembly. I inherited this one and did not think to check for this complication.

 

[macPT]

In a SW2003 presentention, the var focussed a lot on the speed improvment of this version. He performed some graphic tests and some rebuilding tests, on the same PC, with the same files, using 2001+ and 2003, and the result is that the 2003 can double (some times more then double) the speed of 2001+. Do you agree with this? Were the tests realistic?

Regards

 

[metman]

macPT,

The tests were no doubt realistic for that particular demo. But clearly does not represent a valid test for what we are experiencing. It is taking minutes for relatively simple components. What works on my computer in terms of deleting in-context relations does not work for some other designers/engineers here

From Tate's Nov 26 reply:

In-Context Relations - I have found are great during the initial design phase.
But, I usually end up replacing them with "real" constraints during the final design.
It's just my gut feeling, but I'm skeptical about their long-term stability - at least for my products.

 

[SBaugh]

What kind of products do you design and produce...if you don't mind my asking? I have seen lots of different types of ways SW is used, and really I'm quite impressed to see how some folks have found ways to make SW their primary tool. So I wonder what it is your designing that would make you think SW may not be the Tool for you?

Best Regards, Scott Baugh, CSWP
3DVision Technologies
credence69@REMOVEhotmail.com

http://www.3dvisiontech.com

http://www.3dmca.com

*When in doubt always check the help*

 

[metman]

Scott,
You asked, "So I wonder what it is your designing that would make you think SW may not be the Tool for you?"

We are designing an airplane but I did not mean to intimate that SW may not be the Tool for us even though this is true to a large measure.

We have about 12 seats of SW and are in the process of buying 4 more seats plus a PDM worth about $20,000 which should help us for concurrent driving of SW. As you commented we have found ways to make SW our primary tool. For example we have one seat of Catia which helps with complex surfaces particularly with developing flat patterns.

Besides the problems associated with concurrent design, the problem I was trying to relate is that 2003 apparently has some bugs that is showing up as taking excessive time to save model files. As stated at the outset of this thread

File is 3,126 KB.

Added several swept features and takes 2.5 to 3 minutes to save. The feature is a relatively simple cross section swept around circular holes.

Any idea why 2003 would take so long?

Notice that I said swept around circular holes. This is not a helix or any such complex drive curve. It is a circle and the cross section being driven is relativley simple comprised of two concentric arcs joined with two tangent parallel lines with a perpendicular line at the ends of these two straght lines. The other end of the arcs are pierced to the circles which are the edges of hole cut thru sheet metal. There are 3 sizes of holes and aout 8 holes altogether.

To reiterate my solution given on Nov 25, "I deleted all “On Edge ?” relations in Sketch 17 for Cut-Extrude 5 for FS 34 Frame. It saved in seconds."

Now then the engineer I am working with had a similar problem with long time to save (minutes) of a different part so I checked all of his sketches but no in-context relations. Some other problem?? Bill, a designer with SW college training and one of our better SW drivers is complaining of long save times and several others are waiting and wating for files to save.

Our avionics/systems engineer who helps manage our networking got tired of wating for files to save the other day and rebooted the server. Maybe this helped because I did not hear any complaints today but maybe most folks are resigned to the problem until our rep comes in to train us for the new PDM.

Is anybody else having problems with long save times for SW 2003?