Skip to main content
1-Visitor
March 11, 2014
Question

Creo II Parametric Build M090

  • March 11, 2014
  • 5 replies
  • 2329 views
Good Day All,

I had sent out an email back in November asking about Creo II Parametric and any gotcha's (see results below).

Now I would like to gauge the user community to get their opinions on build M090.

So please, if you have any opinion (good or bad) please reply to this email and share your feelings.

I will post a summary when completed.

Jim
Jim Van Dragt
PLM Architect
Information Technology

hermanmiller.com

    5 replies

    11-Garnet
    March 11, 2014

    Jim,


    Thanks for posting this. I just started testing M090 in preparation for deploying it here. We are on M030 which has a number of stability issues, especially with Windchill CAD data management. There are some other known bugs in this build code we want resolved, but have been hesitant with maintenance updates because of the horror stories about M040, M060, M080, etc. Better the devil you know...


    Thanks in advance to anyone who can provide feedback about M090 (or M100).


    David R. Martin II


    Senior CAD Application Specialist


    Amazon

    13-Aquamarine
    March 11, 2014
    The build I have most of my folks on is m070.

    I have m090 on my laptop and use it almost every day. The only issue I've found is, it sometimes it will not exit properly. Just sits there. You pick the red X again and then you get this error:

    [cid:image002.png@01CF0DFA.03560D70]

    If you have automatic publishing, this exit behavior may cause you problem.

    I plan to start looking at m100 later this week or next.

    David Haigh
    1-Visitor
    March 12, 2014
    Jim

    We have gone through a couple of build codes...m050 and m090.

    We have experienced a couple of repeat offenders...first one is highlighted below.

    [cid:image002.jpg@01CF3DD9.55C5AED0]

    This appears to be random...it has nothing to do with too little disk space or the users' permissions, it seems to be related to the actual models.

    The second is when Creo crashes after getting the following error message

    [cid:image004.jpg@01CF3DD9.55C5AED0]

    Again it appears to be random, can occur when either working in a drawing or an assembly.

    In both cases PTC told that us m080 would resolve but we have still had both occurrences with m090.

    Generally as well our engineers would say that performance (spin, pan, zoom etc.) has got worse since we moved from Wildfire 4 m220.

    I'm hoping m100 resolves these.

    Regards,

    Neal Hanratty
    Engineering Systems and Standards Manager
    Terex Materials Processing Group

    T +44 (0)28 8241 8769
    F +44 (0)28 8225 2740
    M +44 (0)75 3495 2739
    E neal.hanratty@terex.com<">mailto:neal.hanratty@terex.com>
    10-Marble
    March 13, 2014
    Neal,



    This first error you show (below) is an error we first noticed in WF1. We
    were unable to get any resolution through PTC support, getting the "...must
    be machine specific" excuse at the time. When it didn't go away by WF3 I
    did some sleuthing. I haven't seen it as often lately, but a quick test of
    WF4 does reproduce it. Tell me if I'm right...does this error occur when
    you request INFO of some sort that would be displayed in the embedded
    browser? If so, than it likely occurs when someone has an assembly open,
    right clicks on a part and opens it, then requests some Model Info or
    Feature Info. I found that closing all windows back to the base or initial
    window and opening the part there before requesting the Info would alleviate
    the problem. It seems to be related to a temp file that is written in the
    User Profile when a browser info screen is requested.



    I can re-create it this morning in WF4...seems to have a different error
    message though.





    Unable to re-create it in WF5/EP5 or Creo2.



    Gavin B. Rumble, PE

    Solid Engineering

    336-224-2312 x101


    1-Visitor
    March 13, 2014
    Thank Gavin

    No unfortunately ours is not the same as you describe.

    It has been random but on a couple of occasions it has happened the user said that they had first created a new sub-assembly whilst working in a top level assembly and then created a part in that sub assembly. The error comes up when they then open the part or sub-assembly in their own window and try to carry out a Creo save.

    One thing we are trying to determine is if it is a Windows problem, i.e. too many files in the working directory. Our users can have typically tens of thousands of files in their working directory.

    Thanks for the info however.

    Regards,

    Neal Hanratty
    Engineering Systems and Standards Manager
    Terex Materials Processing Group

    T +44 (0)28 8241 8769
    F +44 (0)28 8225 2740
    M +44 (0)75 3495 2739
    E neal.hanratty@terex.com<">mailto:neal.hanratty@terex.com>