Skip to main content
J
jv83421-Visitor
1-Visitor
November 26, 2013
Question

Creo 2.0 Parametric

  • November 26, 2013
  • 17 replies
  • 2722 views
Good Day All,

We are in the process of planning an upgrade from Wildfire 5 to Creo 2. I was wondering what horror stories or gotcha's other companies have run into, if any, when performing an upgrade.

Thanks in advance.

Jim

Jim Van Dragt
PLM Architect
Information Technology

hermanmiller.com

    17 replies

    Show previous replies
    P
    ptc-52565611-Visitor
    1-Visitor
    November 26, 2013
    I would stay away from Creo 2 for now...



    We currently use m030 and have some crashing issues as well as an issue
    for bolt analysis in Creo Simulate. We tested m080, but that was a
    complete train wreck. Read only objects in workspaces needing to regen
    would cause your model not to save. We also had some data loss for
    objects modified in m080, the changes would not show up in m030. (I
    always thought build codes were backwards/forwards compatible.)



    ... we are waiting for m090 now... come on PTC....



    Derek


    L
    Lohbauer1-Visitor
    1-Visitor
    November 26, 2013
    We are doing the same thing. Holding tight at M040 (With the crashing and datum display issues) and waiting for Windchill 10.2 M010 to release and then upgrade Creo to M090 when it comes out.

    N
    nrollins1-Visitor
    1-Visitor
    November 26, 2013
    Wow - and my VAR said Creo 2 was awesome. I guess I never asked them if it
    was awesome but crashed a lot and didn't work right.



    "Awesome is as awesome does" - when it works, it's awesome.



    Come on PTC. Maybe Creo 3 will be better.



    I just updated my license to Creo 2 for an upcoming project. I am waiting
    for my license file to come. But, now I am a bit nervous.


    P
    ptc-438741-Visitor
    1-Visitor
    November 26, 2013
    We've been on Creo 2 for some time without any significant issues using build M030. We went from WF 5 to Creo 2 because of some issues with Creo 1 and assemblies.

    Dorian Ferrari|Director|Digital Development & Model Services|310-252-4007
    B
    23-Emerald III
    BenLoosli23-Emerald III
    23-Emerald III
    November 26, 2013
    See David Haight's warning about M080! Stay away, it has a major bug.

    PTC has come across a Creo/Windchill interaction issue in Creo Parametric 2.0 M080 where models fail to save to the Workspace components are modified and have a read-only status:
    C
    ChrisCollinson12-Amethyst
    12-Amethyst
    November 27, 2013
    We've been on M060 for a while now and no significant issues with it,
    Having said that I did upgrade the windchill 9.1 server to M070 and put it
    on new Hardware and also upgraded the users PCs to 64 bit loads of RAM etc

    Think we'll stop there for now

    Thanks to all who pointed out M080 was a dud



    Best Regards

    Chris Collinson
    CAD Administrator
    R
    rrich1-Visitor
    1-Visitor
    November 27, 2013
    Very interesting reading. I did learn something I believe. I have one single user here that has been losing saves on parts and drawings and I was blaming his bad practices or just stupidity because he was the only one experiencing this. But reading below and hearing of making parts drawings or assemblies read only in the Workspace may cause this, flipped the light switch in my head. My user is the only one in the group who has been using this read only feature as a lock to ensure he would not change a part by accident. Who would have thought that a read only item in your workspace would cause the software to have seizures. I now have an edict for my users -- Do not to use read only.

    I really hope PTC finds this bug and fixes it. We are using Creo 2 M040

    Ron Rich
    Mechanical Engineer
    Keithley Instruments, Inc.
    28775 Aurora Road
    Solon, OH 44139
    440-498-2842


    Terms & ConditionsCookie settingsAccessibility statement