When I saw PTC wouldn’t support Windchill 10.1 with Creo 1.0 I knew something was up. At the time I was gearing up for Creo 1.0, however Creo 2.0 came out and didn’t seem to have any major show stoppers so we are starting to deploy 2.0.
I think there is a perceived psychological barrier with running a 1.0 release, so PTC wanted to make the life of Creo 1.0 as short as possible. I suppose they could have made what is Creo 2.0, Creo 1.0 M060; however there does appear to be some behind the scenes differences in the way the software installs and operates with the “Creo Agent”.
Our user’s first impressions of Creo are that it is still Pro/E, which I think is a good thing. Yes we’ve all had frustrations with it, but it does get the job done and is underestimated by some. The GUI has been overhauled and in a lot of ways makes more sense, however when you get deeper into the advanced commands many are familiar. At this point, after some users have piloted the new software, we don’t think adoption will be as difficult as we first thought when Creo was announced. We think new users will pick it up in a snap.
Short support cycle on 1.0? It doesn’t bother me; I’m more concerned how well the software works than the arbitrary version label on it.
-Dave
