Time to move to Creo 2.0?

Hi,

We're planning a move from Wildfire 4.0 to Creo 2.0 later this year: I've begun testing and preparing an install file, plus training materials. There will still be bugs like the silent install and others, but I'm going with it for 700 users eventually.

Would be interested to hear from others on the same topic.

Edwin

In Reply to Marc DeBower:

Hi,

Wondering what the wisdom is with moving to Creo 2.0 later this summer. I see by the product calendar that Creo 2.0 m020 will be out in late August. Is the product stable enough?

We would be moving from Wildfire 4.0 any thoughts on that jump?

-marc

----=----
Urgent messages: I try to limit checking email to 3-4 times per day. If you have an urgent message for me, please call or stop by.

We have been using Creo 1.0 since it was available for production. We currently run Creo 1.0 M030 and will move over to Creo 2.0 M010 by the end of the month.

Creo 1.0 has given us no major problems. It has bugs here and there like all software but nothing was a show stopper for us. Moving from Creo 1 to Creo 2 will be very easy and require no training or preparation for my users. I will only create a short video with some of the new enhancements like Dynamic Cross Sections and that's it.

Moving from WF4 to Creo 2.0 will be a much larger jump since WF5 actually had a Ribbon UI for drawing mode. You will require some training up front to get people ready for the change but I believe it will be easier than most people think. The Command Search tool in Creo is very useful and allows your users to find the commands they are looking for and learn the UI at the same time. This made our down time almost nothing and within a week everyone was loving Creo over WF5.

The only issue we have is not something Creo 1.0 or 2.0 does incorrectly but a decision PTC made to the FEA animation process. You can no longer add multiple animation frames without calculating every step during the anaysis. We used to run an analysis and then add 15 frames to show the animation between the start and finish. If you do that now, it will run calculations for each animation frame which makes the analysis take 15 times longer than it did in WF5.

PTC said they change this because the results were only accurate for the first and last frame, but we did not care about this. We understood the frames in the middle were only for a visual feedback of how things are moving but now we can't do this anymore. Each frame is forcing the calculations to be calculated which is a waste of time for us and I assume for many others that were using the extra frames for a visual purpose.

Just an FYI

"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"

Bjarne, What type of problems did you experience on the computers that required upgrading the graphics hardware? Rendering? Crashing? other?

Thanks, Lawrence