Creo 2.0 M040 crashes a lot

We have not yet mad the switch from wf4 to Creo2 but are currently duing light testing.

I have heard from other users that a lot of crashing is due to using the same config files from ProE to Creo. Is this the case with both of you, or are you experiencing the crashes even without using the same config files? Do you still have a lot of crashes when using Creo's default configurations? I know this is not very practical for a work environment, but may be very good at diagnosing which config files are the culprit, if that is indeed a cause.

Boy, Creo gives a little in time advantage and then takes it away again with it being slower processing. That kind of kills the motivation to get the new functionality in Creo.

Regards,

Lawrence

In Reply to Han Wientjes:

We moved to CREO2 M030 in February with Windchill 10.0 and had a lot of problems with crashing and performance. Now we are on CREO2 M050 which has little less crashing but certainly not as stable as WF4. Performance is still a major issue because it is much slower compared to WF4!
Regards,
Han

Hi Lawrence

Actually we are using a mix of config files from WF4 to Creo 2.0. I checked with PTC which files I could re-use and which not. Our config.pro was ported from WF4 to Creo 2.0 and we removed all the obsolete options. It is kind of hard for us to test performance without our standard config.pro because half of our stuff would not work. I have not yet done much tests using Creo's default configurations as I first wanted to hear if someone was experiencing similar problems.

Regards

David

In Reply to Lawrence Scheeler:

We have not yet mad the switch from wf4 to Creo2 but are currently duing light testing.

I have heard from other users that a lot of crashing is due to using the same config files from ProE to Creo. Is this the case with both of you, or are you experiencing the crashes even without using the same config files? Do you still have a lot of crashes when using Creo's default configurations? I know this is not very practical for a work environment, but may be very good at diagnosing which config files are the culprit, if that is indeed a cause.

Boy, Creo gives a little in time advantage and then takes it away again with it being slower processing. That kind of kills the motivation to get the new functionality in Creo.

Regards,

Lawrence

In Reply to Han Wientjes:

We moved to CREO2 M030 in February with Windchill 10.0 and had a lot of problems with crashing and performance. Now we are on CREO2 M050 which has little less crashing but certainly not as stable as WF4. Performance is still a major issue because it is much slower compared to WF4!
Regards,
Han

Dear Ron

Many thanks for this useful piece of information regarding the shade_model_display. We currently have save_model_display=shading_high. So maybe this is the cause of the slow retrieval times from PDMLink. If saving a file in Creo 2 format using shading_high increase the size of the file dramatically, then I somehow guess this could really affect retreival times over a network. But once again, it is just a theory and I need to check this.

Regards

David

In Reply to Ron Rich:

We have been using Creo2 M040 for about 2 months and yes we are having random crashes 1-2 per week. We had speed issues opening parts and found the problem to be with the shade quality set to high and what the shade_model_display was set to lod now set to wireframe which helps but still crashes.

Ron