Creo Explained – Part 2

<< Part 1

Creo Parametric is nothing but the next version of Pro/ENGINEER Wildfire. So there is not a great deal to explain there. Creo Direct is Creo Parametric wearing a different suit, that’s all. If you are interested in a technical explanation of the preceding statement click the image below to enlarge it. Or you can take my word for it and skip to the next part of this series.

Click to enlarge

This is screenshot of Dependency Walker with three very similar looking executables – direct.exe, parametric.exe and proe.exe. These are Creo Direct, Creo Parametric and Pro/ENGINEER Wildfire respectively. As you can see they are pretty much all the same. If you are programmer you may find a few of the exported function names interesting – the one’s starting with “dont_ever_call_me”. 😉

So basically Creo Parametric and Creo Direct are two Pro/ENGINEER programs installed and running on a computer. This can be seen by taking a closer look at the Creo 1.0 installation folder.

Obviously there is no point to literally have two copies of Pro/ENGINEER. So PTC has put the files common to both programs in the “Common Files” folder and created a folder each for Creo Parametric and Creo Direct. The size of the “Common Files” folder is 3.4 GB. Whereas the size of the “Direct” and “Parametric” folders are about 100MB each with almost identical sub-folder structures and contents. So that should give you a good idea of how much is common between both the programs – a lot.

So when PTC says that all CoCreate users would one day migrate to Creo Direct, they are actually saying that all CoCreate users will one day be working on the Pro/ENGINEER (now Creo) platform. Looking at the way things have panned out I get the feeling that PTC acquired CoCreate more for its customer base and less for its software because they are going to more or less do away with it sooner or later.

Part 3 >>

  • Pingback: Creo Explained – Part 1 |

  • Pingback: Creo Explained – Part 3 |

  • Pingback: Creo Explained – Part 6 |

  • Geoff Hedges, PTC

    Hello Deelip,

    At our unveiling of Creo almost a year ago, we said Creo is  ‘Built from the elements of Pro/ENGINEER®, CoCreate® and ProductView®’ . But more importantly, Creo has new breakthrough, patent-pending technology’ that changes the way designers and engineers do what they do best. I discuss this further on

    Best Regards,
    Geoff Hedges,
    PTC Marketing

    • Sure, PTC took the concepts from Pro/ENGINEER, CoCreate and ProductView. But which platform did it apply those concepts to? It definitely looks like Pro/ENGINEER to me. Not ProductView or CoCreate. Are you denying that?

  • Hi Deelip,

    why should they take the “not in PDS integrated” CoCreate as a platform for the future? I find nothing surprising in that fact, on the other hand it’s good to see that there already is so much common stuff. Direct will be a history-free app on the Granite/PDS Framework/kernel/whatever – just as Parametric will be. That is the idea behid Creo (as far as I understand it. Nice insight though.

    Best Regards, Ralf Steck

    • I’m not suggesting that dumping the CoCreate platform is a right or wrong thing to do. I’m merely explaining that this is being done and how it is being done. That’s all.

  • Geoff Hedges, PTC

    Hello Deelip,
    Does Creo Direct signal the death of Creo Elements/Direct Modeling? The answer is no!  In this blog, I recap our strategy for CoCreate customers and users, the roadmap, and show the highlights from the recently released Creo Elements/Direct 18.0, which coincided with the release of Creo 1.0.
    Best Regards,Geoff HedgesPTC Marketing

  • So will all CoCreate customers eventually move to the Creo/ProENGINEER platform or not? You can’t have it both ways. 😉

    • Guest

      Classic PTC “smoke n mirrors” ….now you see it …now you don’t.

    • Geoff Hedges, PTC

      Hi Deelip,

      Customers using Creo Elements/Direct (CoCreate) have choice  and there are product roadmaps for both Creo and Creo Elements/Direct. 

      As I mentioned in the blog, customers of Creo Elements/Direct continue to evaluate Creo Direct and other apps as they evolve. That’s really no suprise, and I expect that at some stage they will see the value of moving to Creo, but there are no plans to ‘force’ this.
      I sense from the general undertone of your comments that you feel PTC is forcing a change on Creo Elements/Direct customers, when the reality is different.

      Since acqusition in 2007, PTC has invested heavily in CoCreate or Creo Elemens/Direct, how it works with other PTC products (to expand the footprint of solutions customers can enjoy), and entering new markets; gaining new customers globally.

      Best Regards,
      Geoff Hedges
      PTC Marketing

      • Fred

        ptc has NOT invested heavily in CoCreate. PTC has invested only enough to prevent further backslide due to  years of underinvestment. If you look closely you see PTC investing mostly in features that will facilitate a smoother transition to the CREO product. For instance, try administering Model Manager and you will be transported back to user interfaces from the early 1990’s. Model Manager also has a “337” bug that is the single worst bug I have ever seen in any PDM system! Look for PTC to migrate whatever customers they can, then spin off cocreate to the development people in Germany.

  • Deelip,

    Thanks for doing this great technical coverage. I think you are helping people to understand what is going on in a very unbiased manner.

  • Pingback: The Dassault Systemes And PTC Modeling Kernel Problem |