difference between wildfire 5.0 and creo elements\pro 5.0

[Dancan]

someone can tell me what the difference between wildfire5.0 and co elements|pro 5.0?

2 versions are compatible (?), can you upload files from one version to another? ..it seems to me that I create elements|pro 5.0 , is the most recent ver. of 2 , so with the wf5.0 I have the doubt that you can not load the native files of creo elements|pro 5.0 .

Thank you.
d.

 

[Parametric_Ozzy]

someone can tell me what the difference between wildfire5.0 and co elements|pro 5.0?

2 versions are compatible (?), can you upload files from one version to another? ..it seems to me that I create elements|pro 5.0 , is the most recent ver. of 2 , so with the wf5.0 I have the doubt that you can not load the native files of creo elements|pro 5.0 .

Thank you.
d.

none, except the initial screen and the name due to the brand rebrand.
pro/e wf5.0 came up to the build code m060, after which created creo elements/pro 5.0 that started from the code m070.
then compatibility is full because at the bottom is the same version, you can open previous files as in all other versions proe.

I hope I've cleared your mind.
greetings

 

[nicksoft]

none, except the initial screen and the name due to the brand rebrand.
pro/e wf5.0 came up to the build code m060, after which created creo elements/pro 5.0 that started from the code m070.
then compatibility is full because at the bottom is the same version, you can open previous files as in all other versions proe.

I hope I've cleared your mind.
greetings

a clamorous topic of the marketing department according to me ... already if I have to look for something on the internet that concerns this software you become crazy ... proengineer, pro/engineer, pro-engineer? proe... proe, creo, wildfire, creo1? Creo2? ... but yes, we also add creo elements pro, indeed creo*elements*pro and hope that san google will help the most confused (the least confused come directly on cad3d :smile

 

[Parametric_Ozzy]

a clamorous topic of the marketing department according to me ... already if I have to look for something on the internet that concerns this software you become crazy ... proengineer, pro/engineer, pro-engineer? proe... proe, creo, wildfire, creo1? Creo2? ... but yes, we also add creo elements pro, indeed creo*elements*pro and hope that san google will help the most confused (the least confused come directly on cad3d :smile

Hi, Nick.
I agree with you, it had to be a help for the passage to the definitive creo but in reality it has created only more confusion between both existing customers and new ones and I do not deny you also for us to go...:wink:
if nothing else now with creo is all much clearer, with the concept app and extension, if you have doubts... ask:

 

[calacc]

I would have a curiosity. .
a when a granite-based cross-release interoperability (gcri) for creo??? that glue face maybe between creo elements pro (wf5), create parametric 1.0 and 2.0. to now exists only for pro/e wf 2-4... I highly hope that the ptc is working on it!

 

[Parametric_Ozzy]

I would have a curiosity. .
a when a granite-based cross-release interoperability (gcri) for creo??? that glue face maybe between creo elements pro (wf5), create parametric 1.0 and 2.0. to now exists only for pro/e wf 2-4... I highly hope that the ptc is working on it!

exists already calacc.. .
from creo 2.0 to creo 1.0 and wf5.0
from creo 1.0 for wf5.0 and wf 4.0

*.dll files are now part of creo installation and are available in
<directory di="" installazione="">\common files\<codice data="">♪<tipo_sistema>\gcri\readnewermodels.dll

greetings</tipo_sistema></codice></directory>

 

[nicksoft]

Hi, Nick.
I agree with you, it had to be a help for the passage to the definitive creo but in reality it has created only more confusion between both existing customers and new ones and I do not deny you also for us to go...:wink:
if nothing else now with creo is all much clearer, with the concept app and extension, if you have doubts... ask:

Yes it is all clear...but I turn again with a scheme for the direction to be drawn out to the need because every time it is a mess for them, especially when they enter the speech also I create direct and cocreate ... indeed, I create elements/direct !!!

 

[Parametric_Ozzy]

Yes it is all clear...but I turn again with a scheme for the direction to be drawn out to the need because every time it is a mess for them, especially when they enter the speech also I create direct and cocreate ... indeed, I create elements/direct !!!

e eh si in fact for non-workers is even more complex, especially if you have the 2 systems, but in fact now you are increasingly outlining the strategy of complete shortening of the 2 " entities".

 

[calacc]

exists already calacc.. .
from creo 2.0 to creo 1.0 and wf5.0
from creo 1.0 for wf5.0 and wf 4.0

*.dll files are now part of creo installation and are available in
<directory di="" installazione="">\common files\<codice data="">♪<tipo_sistema>\gcri\readnewermodels.dll

greetings</tipo_sistema></codice></directory>

good thing that they are already integrated into the installation file. but we are sure that the speech is equivalent to what is described qui? ?

from how you describe it you can only go back. . .
Basically if I have 1.0 I can open a model created with a 2.0, modify it by adding features?? this is meant by cri (cross-release interoperability)

 

[Parametric_Ozzy]

good thing that they are already integrated into the installation file. but we are sure that the speech is equivalent to what is described qui? ?

from how you describe it you can only go back. . .
Basically if I have 1.0 I can open a model created with a 2.0, modify it by adding features?? this is meant by cri (cross-release interoperability)

calacc forgive me but I know very well what I say and what it takes.. .
It is quite clear that the cgri (among other things I had done a nice document posted here several years ago...) is a technology that gives the possibility to open files created with new versions (eg creo 2.0) with less recent version (pro/e wf5)
on the contrary it is always obvious that you can, as in all software applications.
Since it does not exist in rescue with the previous version name, they have created this tool, which works on the interoperability of the clay granite kernel.
then visualize (view copy) the model tree cannot change the definition of existing features and add new ones, without having to switch from other non-native formats (step,iges,sat,ecc).
you can only go back certain, because going forward does not need to.. .

 

[calacc]

you can only go back certain, because going forward does not need to.. .

Well, then I think I miss a few steps: I in the description of the infamous tool read textual words: Pro/engineer wildfire 2.0 user can view the entire feature tree, add feature and save the model. a pro/engineer wildfire 4.0 user can open the original model and graft additional information on features created in pro/engineer wildfire 2.0 in the original pro/engineer wildfire 4.0. you get a complete model in pro/engineer wildfire 4.0.the question now is: if I replace the previous quote "I believe elements pro 5.0" a "pro/engineer wildfire 2.0" e "creo parametric 2.0" a "pro/engineer wildfire 4.0" Do I get a true or false statement?

Thank you for your clarification

 

[Parametric_Ozzy]

Well, then I think I miss a few steps: I in the description of the infamous tool read textual words: Pro/engineer wildfire 2.0 user can view the entire feature tree, add feature and save the model. a pro/engineer wildfire 4.0 user can open the original model and graft additional information on features created in pro/engineer wildfire 2.0 in the original pro/engineer wildfire 4.0. you get a complete model in pro/engineer wildfire 4.0.the question now is: if I replace the previous quote "I believe elements pro 5.0" a "pro/engineer wildfire 2.0" e "creo parametric 2.0" a "pro/engineer wildfire 4.0" Do I get a true or false statement?

Thank you for your clarification

Of course it is true, the methodology is always the same.
I don't understand what is unclear to you sincerely, what doubt you have to give me a practical example.

 

[calacc]

Great! ie now with creo it is no longer necessary a tool to move from one version to another because it is already included in the installation file, I seem to understand.

practical example:

- user a. prepares a model using creo parametric 2

- user b. takes the user model to but has only create parametric 1.

the question I ask myself is: what b can do to the maximum with the model available? view, scroll pattern tree, add features, edit, etc...

 

[Parametric_Ozzy]

exactly you understood well, your example is correct.

the user b can do:

-open and view the file
-to run the model tree but not to inherit the definition at least until the previous one was so
-add new features
- all other classical creation tools living in creo parametric 1.0
-Save and make available the features created in creo 1.0 for the user using creo 2.0

the interoperability remains unchanged, the file is always the *.prt.

greetings

 

[calacc]

well, the only limit would therefore be in the editing of the features made with the most recent relaise, which only change using the same. but if (back to the example of before) b wants to change a features that he does not like to to can suppress it in the model tree and recreate it from scratch? from the last post it would seem like yes... in what I read below it would seem no

then visualize (view copy) the model tree cannot change the definition of existing features and add new ones, without having to switch from other non-native formats (step,iges,sat,ecc).

 

[Parametric_Ozzy]

well, the only limit would therefore be in the editing of the features made with the most recent relaise, which only change using the same.

yes correct, at least on the old was so, I have not yet tried on the new, but should not differ.

but if (back to the example of before) b wants to change a features that he does not like to to can suppress it in the model tree and recreate it from scratch? from the last post it would seem like yes... in what I read below it would seem no

recreating it of zero surely, suppressing it I don't remember sincerely but I doubt strongly, since it practically visualizes the model tree as if it were in "read only", the one that commands is the application of initial authoring and that is in this example I create 2.0.
I'll let you know as soon as I can try it on the new versions.
greetings

 

[calacc]

Okay, thank you very much for the disappointments, it would be interesting to do some tests on the subject. I have 1.0 and we are evaluating in the company if switching to 2.0 renewing the maintenance contract. but they shot us a cifrona. .

 

[Parametric_Ozzy]

Okay, thank you very much for the disappointments, it would be interesting to do some tests on the subject. I have 1.0 and we are evaluating in the company if switching to 2.0 renewing the maintenance contract. but they shot us a cifrona. .

I'll let you know asap.
for switching to 2.0 you would still not have this need since the files created with 1.0 would always open them.
if you can linger pro/e is one of the few cad systems that opens file versions made with prehistoric releases without any problem.
for example I recently opened files created with pro/e r17 (exit in 95-96 I think) in creo 2.0.
for the cost... the annual maintenance fees are always the same unless you have to pay for retroactives, but if you have created 1.0 I doubt it.
who ptc or var?
greetings

 

[PTC]

Hi.

gcri uses the ptc atb is therefore possible:

1) open models up to 2 later releases (parts and assemblies).

2) display the model tree as it was created (the patterns result in single features)

3) add feature to the model tree

4) hide feature (do not suppress)

5) add/remove/change levels

6) add/remove/change parameters (also feature and in any case the connected feature will not be regenerated)

7) add reports (also feature)

8) create simpl rep, combined views, sections etc.

is not possible:

1) suppress feature

2) edit feature

3) change or display existing relationships.

4) recoil components in an imported set

5) open axioms with motion skeleton

6) edit simpl rep, combined views, sections etc. existing.

works very well with flexible modeling and I create direct where some limits imposed on changes come to fall.

I hope I've been helpful.

Hi.

 

[mosca65]

Friday I come to install creo instead of wildfire5: your comments and discussions make me enter a little apprehension! We hope well, I see that the last post was 3 years ago and I hope that things have improved in the meantime. Hi.