Wildfire4.0 .prt to Wildfire 3.0

[bjk2]

Gentlemen, is there backward compatibility from Wildfire 4.0 to Wildfire 3.0 using the associative topology bus, or any other means?


Thanks,


benny

 

[design-engine]

PTC will typically tell you that the software is backyards compatible. Usually they neglect to tell you that they mean only iges or step ...

I laugh every time I hear that.

 

[jeff4136]

http://www.eng-tips.com/viewthread.cfm?qid=216802&page=1

 

[tommypurple2]

It would be like asking a fourth grader a fifth grade question and expecting them to answer it.


If all that changed was the software icons/screen I could see how it could be backwards compatable, but if they change the way the program computes. Then you would have real issues with backwards compatiblity.

 

[dr_gallup]

http://www.ptc.com/products/granite/gcri/index.htm

GRANITE Cross-Release Interoperability (GCRI) extends the original
neutral file based CRI interaction, allowing earlier release users to
view existing feature information in the model tree in a read-only
format GCRI model. GCRI offers the ability to append features added to
the GCRI model in the earlier release to the original, fully featured
model in the later release model. This results in a completed, fully
modifiable model consisting of features added by more than one
Pro/ENGINEER version.

 

[davisdony]

2008-06-10_031842_GCRI_Operational_Use_And_Limitations2.zip



Try this it is having its own limitations

 

[bjk2]

Thanks for the replies. It's great having such an intelligent group for support.

benny