The community will undergo maintenance on October 16th at 10:00 PM PDT and will be unavailable for up to one hour.
Indeed, there have been some major adjustments I've had to make between starting on Ver. 11/Unix and now at Creo 2.0.W7/64 and some were indeed painful; but overall as a long time Windows user I really like the movement to the new UI.
Even though the need to customize processes (e.g. Mapkeys) is less I find it is more easily done when I want to. Modifying the existing icons in the ribbons is way easier than it ever was to edit the UI layout in earlier versions. The ease of moving items to the QuickAccess Toolbar is truly welcomed.
I also agree with comments made on the improved sketcher. It is much more intuitive, controlable and flexible.
As a person who learned CAD while working in a precision sheetmetal job shop I REALLY like the improvements to the sheetmetal module.
Are there some things I don't like, sure, bur even though there is still much to improve, I wouldn't want to go back. Change is hard, but growth is rewarding.
My $.02
All in all Creo is a "better" evolution on many fronts. Being a "lifer" (Rev6 Vet) I have seen much from PTC over the years.It's safe to say it was free market competition from SolidWorksthat forced PTC to take a hard look at the GUI and functionality that resulted in Creo. There are some things that were overshoots in my opinion. The Creo colors are abysmal and terrible for old guy's eyes. My retinas have been in front of a CAD screen for 30 years and are wearing out. I know I can change them...but I get so busy thatI have not had atime to set it all up to a more "benign" interface. (If any old fellow geezers have created a pallet they would like to share, I am accepting charity)
Cannot stand the pre-highlighting at times, especially when trying to change dim values in a model.
I likeSimulate Lite (Thanks SW for the forced functionality). BUT....200 surfaces max? C'mon you stingy rats. Allow us the full hot order with Lite. It's already limited on many fronts so what sense does it make to limit the suface count?
Reps are still too cumbersome for me....better but still a bit of drudgery.
BOMS and tables...still too esoteric and cumbersome.
Setting colors and surface textures went the wrong direction. WF4 was nice....I hear Creo3 has some goodies. I have yet to do actual work with shadows, rendering and background "On" so it's functionality I do not find useful.
Mr. Doug Shaeffer will jump on me for this...but Configs are too confusing for me. The "Current Config" thing is something I believe is overkill. Keep in mind I am a Simple CAD Monkey and do not have Admin requirements. It may be nice for them but gets in my way.
The sketcher setup assumptions are a hidden danger for Parent Child relationships. I Always, Always, Always make a point to verify my sketcher setup is the way I want it and not what Mr. Creo thinks I want. 9.9 out of 10 times it chooses a random surface as the orthographic reference I do not want. That is fundamentallyopposite to good Pro/E modeling robustness.
End $.02
I wondered if you would! LOL I promise to spell your name correctly from now on Mr. Doug SCHAEFER
I am with you on both the invaluableaspects of config and the failure to launch on some of the new stuff. For example, when I first loaded Creo2, I set my colors to a scheme I liked that didn't burn a hole thru the back of my head and saved it to what I thought was
"Current config" is a decent idea - show the user what the current software configuration is - except that "current config" doesn't actually exist, it's simply the sum of the config files loaded and whatever changes the user has made. Those changes, however, if not saved to a config file, are lost when the software is restarted and the UI does nothing to educate the user that this is how things work. It's difficult, in the interface, to understand the robust system behind Creo configurations and how to use it.
Other software, like SW, make it easy on the user to change the setup, but give no insight as to where those things are stored. This makes it impossible (or at least very difficult) to share that configuration across the organization or even to a new workstation.
The Creo UI tries to be easy like SW but keep the power of the config files in the background. The end result, however, is harder for everyone.
--