Skip to main content
Nov 10, 2014 9:36 PM UTC
Solved

Creo 2.0 and Creo 3.0

Can Creo 3.0 and Creo 2.0 interact? Our school computers and most of the returning students run Creo 2.0 (releases ranging from M070 to M100 or later); students that download it now, of course, are getting Creo 3.0. We can seamlessly open Creo 2.0 assemblies and parts in the new Creo 3.0 installations, but will we run into issues going the other way? We're not in a position to upgrade the school computers, so if we can't go back and forth, we're going to have to stick with 2.0 everywhere. Is Creo 2.0 still available for download?

Thanks,

Noa Rensing

FRC Team 2877, The Ligerbots

    ChrisCarrAnswer
    Nov 10, 2014 9:38 PM UTC

    Hi Noa,

    Creo 3.0 can open 2.0 parts, but once you save a part or assembly in Creo 3.0, you won't be able to open it in Creo 2.0. Unfortunately, they're not backward-compatible.

    However, Creo 2.0 is still available for download from the same location as Creo 3.0.

    Chris

    5 replies

    ChrisCarrAnswer
    Nov 10, 2014 9:38 PM UTC

    Hi Noa,

    Creo 3.0 can open 2.0 parts, but once you save a part or assembly in Creo 3.0, you won't be able to open it in Creo 2.0. Unfortunately, they're not backward-compatible.

    However, Creo 2.0 is still available for download from the same location as Creo 3.0.

    Chris

    nrensingAuthor
    Nov 10, 2014 11:23 PM UTC

    Thanks, that's disappointing but at least it's early. Does Creo 3.0 have a compatibility mode or "save as" capability?

    Noa Rensing

    Team 2877 The Ligerbots

    Nov 11, 2014 1:17 PM UTC

    No. Pro/ENGINEER and Creo have never offered any backwards compatibility. As Chris mentioned, once you have upgraded to a new release, everyone in your extended ecosystem needs to upgrade.

    Jan 22, 2015 7:21 PM UTC

    Are there plans to create backward compatibility? I've made a horrible mistake modeling half a semesters worth of work to find out that I'm out of luck.

    Jan 22, 2015 7:54 PM UTC

    Unfortunately, no. Creo, Wildfire, Pro/ENGINEER. None of them have ever been backwards compatible. Once you've moved forward, there's no going back unless you want to work with neutral data like IGES or STEP, but you will lose your feature history and component placement definitions in the process.