Creo 2 M030 & Creo 3 Releases

[dgschaefer]

PTC has an actual date for Creo 2 M030 on the product calendar [1], next
Wednesday, November 21st.



They also have dates for Creo M040 & Creo 3 now. There's no scheduled
new Creo 2 build until February 2013, that's 3 months between
maintenance releases. Remember when we got a new version every 6 months
and I think maintenance releases were weekly or was it every 2 weeks?



Creo 3 F000 isn't due until Q4 2013. So much for the commitment when
Creo was launched of a new release every 12 months each March.



We pay quite a lot each year for maintenance, about 90% of the value is
in getting new releases. Tech support is too slow for our needs, we
rarely get an answer before our deadline to deliver to the customer.



If they are going to stretch releases out that far, I'm seriously
considering a recommendation to not pay our maintenance that is due in
December. With Creo 3 not hitting for a year, it'll be at least 18
months, likely more, before any of our clients implement it.



There is very little reason to keep paying maintenance if PTC isn't
going to keep maintaining the product.



[1] -
http://www.ptc.com/cs/product_calendar/PTC_Product_Calendar.htm#RANGE!A2

[magnus.salomons]

In Reply to Doug Schaefer:

PTC has an actual date for Creo 2 M030 on the product calendar [1], next
Wednesday, November 21st.



They also have dates for Creo M040 & Creo 3 now. There's no scheduled
new Creo 2 build until February 2013, that's 3 months between
maintenance releases. Remember when we got a new version every 6 months
and I think maintenance releases were weekly or was it every 2 weeks?



Creo 3 F000 isn't due until Q4 2013. So much for the commitment when
Creo was launched of a new release every 12 months each March.



We pay quite a lot each year for maintenance, about 90% of the value is
in getting new releases. Tech support is too slow for our needs, we
rarely get an answer before our deadline to deliver to the customer.



If they are going to stretch releases out that far, I'm seriously
considering a recommendation to not pay our maintenance that is due in
December. With Creo 3 not hitting for a year, it'll be at least 18
months, likely more, before any of our clients implement it.



There is very little reason to keep paying maintenance if PTC isn't
going to keep maintaining the product.



[1] -
http://www.ptc.com/cs/product_calendar/PTC_Product_Calendar.htm#RANGE!A2
91



--

[BrentDrysdale]

Hi Folks,
I am just experimenting with Creo 2.0 now trying out Cabling for the first
time and using PTCU material. This is on M020 and we did not use Creo 1.0
Some quick thoughts:

- *PTCU.* This has been pretty usable. Only a couple of place where
there was missing info and that was easy enough to figure out. I give 4/5.
- *Background Colour*. I had seen previous discussion but thought I
would give the Default White a go. Well after a couple of hours I went and
found how to get the older dark blue blended background back. I was quite
worried when I thought that we only had the standard off white or the Dark
background. Personal preference I know but the work book had me switching
between Default and Dark when I could leave it alone with the pre
WF scheme (had to be accessed via the syscol.scl file we have always used
for those of us who prefer those colours).
- *Menu Manager*! Well I was thinking that it would be all ribbon but
as said just now I should have been wary after WF. Much of Cabling is
still solid Menu Manager so all you Done/Return freaks will be happy
(joking). I nearly fell of my seat when I saw an example of a connector
being oriented to the yellow side of a Datum Plane (so pre WF, let alone
Creo.)
- *tree.cfg* seems to work from WF5 so that helps.
- Lost my lovely PDF creation from WF5 but it will probably turn up.

I was thinking of Q4 for changeover but now I am thinking Q1 if then. Will
be interested to see M030 and see what is changed.

So far the stand out for Creo 2.0 is the dynamic cross sectioning. At least
for Creo (the actual Creo not the renamed WF5) the search command function
works pretty well. MS could sure pick up this for Office. Have not
experimented with Freestyle yet but can see plenty of use for some aspects
for us. We don't have a licence for Flexible Modelling and given that we
don't pick up many external models and we have long since killed (just
kidding) the sloppy modellers it should not be so much of an issue.

Releases and what you get for your Maintenance. I have said before we are
never that focussed on new releases as this is software after all and
different rules apply that we could never get away with in our branch of
Engineering. However wishing it wasn't so seems to make no difference so I
just go back to looking for a stable release that does not have bugs which
stop us from working. And yes we have a protracted discussion at every
Maintenance renewal but end up grudgingly paying. Sure glad it is not my
money though.

Anyhow for now.


Regards,

*Brent Drysdale*
*Senior Design Engineer*
Tait Communications

[DamianCastillo]

We are having great success with Creo 2.0 M020 but I also fear that PTC will not focus on getting the old "Menu Manager" features updated which would go against their goal of a user friendly UI.

From Creo 1.0 and Creo 2.0, I noticed some old "Menu Manager" features get converted and I only hope this continues. I would have to see the unfinished mess that was Wildfire.

"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"

[amedina]

I like Cro/e-Too M020. Like Mit loves Big bird and Jim Lehr...well I'm
growing to like it. Its a little late though. Like it was mentioned here,
Solidworks and others like inventor and the like have met PTC's pro/e face
to face and have continued their marry way. Mean while Pro/e has stayed the
same with new lipstick, and now broken into and sold in smaller pieces. I
can see the analogy there about Cro/e (proe/creo=Croe) being a rock when
you need a hammer. Meanwile all our competitors and colleges use hammers
with laser guides, hydraulic systems and recoil user protection. Heck even
their GUI's are more friendlier and have better documentation for free and
their for-pay training is about the same if not better. So I wonder if
there are more people leaving PTC behind because of the way they handle
their business.


On Mon, Nov 19, 2012 at 9:44 AM, Damian Castillo
<->wrote:

> We are having great success with Creo 2.0 M020 but I also fear that PTC
> will not focus on getting the old "Menu Manager" features updated which
> would go against their goal of a user friendly UI.
>
> From Creo 1.0 and Creo 2.0, I noticed some old "Menu Manager" features get
> converted and I only hope this continues. I would have to see the
> unfinished mess that was Wildfire.
>
> "Too many people walk around like Clark Kent, because they don't realize
> they can Fly like Superman"
>