Creo2 - build code

[nrollins]

Hi all - I found a reason to leave Creo2 M070 and want to update.



Should I go M090 or M100?



I run without PDM - but I don't run with scissors or a lollypop in my mouth.



Thanks

[BobMonat]

M110 is supposed to be available today.

Is the list of fixes between builds still available? If so, where is it?

Thanks,
Bob

Bob Monat
Jerand Technical Services, Inc.
bob@jerand.com
www.jerand.com
1-317-875-6087


On Wed, May 14, 2014 at 2:48 PM, Nathan Rollins
<->wrote:

> Hi all – I found a reason to leave Creo2 M070 and want to update…
>
>
>
> Should I go M090 or M100?
>
>
>
> I run without PDM – but I don’t run with scissors or a lollypop in my
> mouth…
>
>
>
> Thanks
>

[BrianToussaint]

Under eSupport Tools on your PTC support page.

[cid:image001.png@01CF6F89.7DF86FF0]

Brian Toussaint
Systems Administrator

Hoshizaki America, Inc.
“A Superior Degree Of Reliability”
618 Hwy. 74 S., Peachtree City, GA 30269

[DeanLong]

Brian,

Use caution jumping above M080. I have recently found out that my HP with on-board grahics will not work above M080 without OpenGL disabled. If you are using an approved hardware configuration then you are fine. Just make sure before the jump up.

[davehaigh]

You should go with m110

PTC strongly discourages using Creo Parametric 2.0 M110 with older datecodes. It is important to move all users at once, to avoid models being modified again in older datecodes by other users.

Document - CS150760

Document Information
Type

Article

Date Created

12-Nov-2013 13:04:12 EST

Date Last Updated

10-Mar-2014 12:27:34 EDT


Document Details
Title

Defect in handling of unitized expressions of angular values in PTC Creo Parametric 2.0

Description

• Defect in handling of unitized expressions of angular values
• A dimension driving a coordinate system shows an incorrect value, when a UDF containing relations is placed.
• In Wildfire 4.0 the value is correct, but in Creo Parametric 2.0 a different value is displayed

Applies To

• Creo Parametric 2.0 datecodes: F000 - M100

Cause

• Defect in handling of unitized expressions of angular values in PTC Creo Parametric 2.0 F000 - M100
• The System of Units in PTC Creo Parametric is defined by three primary basic units: length, mass/force, and time. There are two more quantity types included in a System Unit definition: temperature and angle. Inside Creo, all standard System Units contain radian as the basic unit for angular values. However, angular measurements in Creo models are reported in degrees. These contradictions cause inaccurate support of angular values in Relations and Parameters.

Resolution

• SPR 2201931 has been filed with PTC R&D
• Corrected in Creo Parametric 2.0 M110
• PTC strongly discourages using Creo Parametric 2.0 M110 with older datecodes. It is important to move all users at once, to avoid models being modified again in older datecodes by other users.


SPR Information
Product

Creo Parametric, Direct, and Layout

Module

FEATURE OPERATIONS

Reported Release

Creo 2.0

Reported Datecode

M090

Affected Platform

All

Resolution Status

Release

Status

Datecode

Creo 3.0

Evaluating

-

Creo 2.0

Planned

M110


Related Documents
Type

Number

Status

Description

SPR

2201931<">https://www.ptc.com/appserver/cs/view/spr.jsp?n=2201931>

Open

The dimension 'PROFILE_ANGLE' in coordinate system 'BACKUP_CTR_TIP' shows up as
-128.69 instead of -2.25, when UDF is placed. In Wildfire 4.0 the value can be seen
as -2.25, but Creo Parametric 2.0 displays a different value.




David Haigh

[BrianKrieger]

I would say go to M100*. Our tests show that M100 is faster than M070 (didn't test against m090, though) when disconnected from PDMLink. When connected, though, our guy's tests showed slower performance. M100 does solve a few things, though, like Model Check misinformation and some drawing exits. As mentioned, though, the upgrade advisor is a nice tool.

We run PDMLink, so I guess we're running with a lollipop in our hands and scissors........oh, never mind...........

BK

* - That said, M110 is due tomorrow, so if there hasn't been testing, this one might be slated instead to circumvent the "try in the latest build" scenario when something does go wrong.

[dmartin]

Windchill users, be aware that your Windchill cache is not supported if jumping more than one maintenance build code. We are in the process of moving from M030 to M090 and just found that out. Recommended practice is to upload or check in all new or modified objects from all workspaces prior to upgrade. Our internal MCAD AE discovered this when one of our users had some weird workspace behavior after upgrading.

David R. Martin II

Senior CAD Application Specialist

Amazon

[davehaigh]

I'm not sure that's a hard and fast rule.

M030 had lots of issues with Windchill and the cache, most of that stuff was fixed by m050/m060.

I can totally believe you would have issues updating from that version.

David Haigh

[TomU]

We recently jumped from CEP5 M120 to M220 with no issues. The only thing we noticed is that the first time you launched Pro/e, it would take between 10 and 15 minutes to start up. There seemed to be some type of cache update or backup taking place in the background. After that initial startup delay, everything was fine. Users did not check-in, upload, or anything prior to the jump. FWIW.

Tom U.

[BillRyan]

Go to M110 if you are connected to Windchill and depend on Creo calling for the objects on the fly. For some reason, M110 is able to utilize 100% of the network which has given us a 20% improvement in opening files(initial testing). Thank you PTC!

[cid:image001.png@01CF737D.CA1D2E50]

[ScottPearson]

More food for thought about which build of Creo 2 to shoot for.

Per PTC's Windchill/Creo Compatibility Matrix (see

BTW, the significance of WC 10.2 m020 is that it is the first build to provide support for Win 8.1 and IE11. Few if any of us out here are jumping on the Win 8.1 bandwagon, but a year from now (or less) all OEM workstations may start shipping with Win 8.1 and IE 11. So WC 10.2 m020 may pay benefits ...

[bbigelow]

Bill is the improved something you just noticed through testing, or did you actaully see or read about this improvement?

We are getting ready to pull the trigger and load M100, and we do use PDM/Link.

Let me know if you have any further info.

Thanks

[BrianToussaint]

We have been on M050 for a while and have issues with check-ins of assemblies from CREO workspaces where it would start the check-in but never finish and we would have to force CREO to shut down. It seems that each time a new build had come out, there seemed to be something to pop up right away and I waited. Then someone mentioned that M100 seemed to get rid of this. So I put it on the user that had the most issues for this and let him test it. He started checking in and it seems to have fixed his check-in problems. I also updated to the latest update of Java 7 at the same time. Before updating his CREO, I looked at the list of issues between M050 and M100 and picked out the ones that seemed like they would affect us and I could not get them to duplicate on my system, so it seemed that they might be more company/case specific. Grant it, this is only our third day on M100, but all is going good still.

Brian Toussaint
Systems Administrator

Hoshizaki America, Inc.
"A Superior Degree Of Reliability"
618 Hwy. 74 S., Peachtree City, GA 30269

[BillRyan]

Brad,
Actual testing...We received a pre-release of M110 along with testing the released version of M110.

In our environment...
M100 is more reliable when compared to M070 and M050. Just started testing M110 so have no comment here yet.
M100 is the slowest build we tested out of all Creo 2 builds for communication with Windchill.

We are using M100 because of a reliability issue with M070. (TMP files in users cache folders which hung the Creo session)

[bbigelow]

Thanks for all the info Bill!

Which version of Windchill are you on?
We are using 10.1 m020.

Thanks,
Brad