Only because I hate the idea of losing the e-mail (ha ha). My 0.02 would be to implement m090 at least as there are some really good fixes included with it over m080. Below is the summary I wrote out and just didn't send. And please note, my views do not represent company positions, etc.
BK
Just to chime in with our experience (m050 imp in July, m070 currently). CP2 has some ready-seen warts. The pitfalls I would mention:
* When interacting with WC, watch out for tmp files (in cache). These will cause many/any subsequent sessions to crash. (No fix in sight)
* Family Tables took a turn down. Many performance issues we've had seem to coincide with FT's.
* Bad modeling in previous models makes.....things.....much......worse in CP2.
* When connecting to multiple servers (i.e. tests, etc.), watch out for same-named workspaces, this could cause loss of workspace cache.
* When creating a note, drawing will cycle and eventually lose table data. (fixed in M090)
* Various crashes with simplified reps. We don't leverage Graphics Reps, but I understand that these are a huge source of crashes. (Many/most are fixed in M090)
* Watch out for updating customization files and config.pro files. There is a hole somewhere that CP2 remembers its previous customizations but the updated/new file doesn't match.......so it deletes the .ui file.
* Simp Rep preview panel still an issue with WC (it wants to download everything). Sort of fixed in m070, fixed in a solid way in m080.
* Command search will not find items if they are removed during customizations. So don't remove, just push to overflow :).
* PTC essentially removed common installation. While it's possible, it now (essentially) requires Admin privileges to use.
o To get around this in a non-supported way, when using WC, delete the ".do_not_read_config.fld" file and rename the creoagent installer.
* Annotation tool wreaks havoc on existing gd&t and takes some getting used to.
* Normal constraint nice, but comps keep assuming it unnecessarily. Use comp_normal_offset_eps config.pro setting.
* Saving is a pain if using WC in conjunction with items marked as read only.
* Overall poor/worse performance with WC. Outstanding issue that just gets worse in CP2. Of everything, the flagship CAD tool working so poorly with the flagship Data Administration tool just overall leaves a bad taste. When used in standalone mode, I think CP2 is a clear improvement over previous gens. But that's not real world.
Things that we see as good:
* Command Search (this is a great tool for moving to CP2, but as a seasoned user, it's also just a great tool to find commands that I hardly ever use and were difficult to find in any version). I find myself looking for the command search in Excel, etc.
* Learning Connector (very good tool, good smattering of included content)
* Love tab customization (if you don't like office 2010, CP2 is gonna be a curse to you).
* Better range of environment tweaking (icon images, etc.)
* Dynamic sectioning (though there are still performance and file size drawbacks)
* Easier to get new users up and going (seems to be the case, but this is based on a very small sampling).
* Flexible modeling (but this can also be a very bad thing, depending on your viewpoint).
* Tabs, I think, are a better layout for accessing functionality.
* Custom selection filter
* Assembly 3D dragger (many curse this initially but most users that I finally got to using it now like it)
* For the rare occasion, the new sketched rib feature is nice.
* (Personal) I am one of the few who like the new measure tool overall. But the selection wasn't intuitive (for seasoned or for new users).
* Sketcher overall is better (feature tools, palette, offset entity, etc.).
* On-screen assembly constraint changes
Overall, I would say CP2 is a wash. If the terrible intra-system integration would have been even the same rather than worse, it would have been an overall better imp. Instead it winds up being another in a long line of meh. Unfortunate.
BK
-med.png "BrianKrieger"){kind=avatar}
