Thanks for the info Peter.
If this is any indication of the direction they're heading, I cringe......
No...., PTC is keeping their cards close to their chest, and that the scary part.
I have a munafacturing system of over 7000 files, all in the old turning interface.
We have asked for a firm commitment for compatablity after Creo 5, can't get an answer.
As myself and my second have now seen how Creo is handling the old manufacturing files, some file just don't function, conflicts with parameters, and the lack of direction from PTC on this issue, we are more than convinced that at some stage in the future, support for old interface will be disabled permanetly.
This leaves us with the update or not to update question, and our companies directive is to keep up to date with our software, so I am now tying to redo as many files as possible in the new interface.
PTC is being very secertive in the direction, when we recieved WF5 we was told WF6 was coming, then the bomb shell, scrapping the wf platform and releasing Creo all within 12 months, they knew this was going to happen, they didn't just wake up one morning and say, lets just change everything just for the sake of it.
This is a long term business stratergy.
While I can understand the reasons why they have to do that and why the need for them to not show their hand because of the competition.., but they need to understand that we need direction and guidance so we can develop our business to suit the software direction, we are their customers...not their unpaid R & D team.
Wow, sorry to hear that! I've seen issues going from WF to creo where things just.....fail.
One thing, I've been told and also read this several places, when they make such a huge leap, completely redo your start parts. Do NOT, say, just open your WF4 parts in creo, and save them as your new start parts. Create completely new ones. As bad as it sounds like they're changing the software and as frequently, I'd make new starts parts every release.
This is extremely frustratin for a long-time user like me. Preiously, it all just worked. We never had to give thought to problems and incompatabilities like this.
To me, they're going the wrong direction, and the other expert users tend to agree with that sentiment.
Best of luck!
it is a pain, the fact that every version thay change the file format, so file saved in creo 2 can't be opened in creo 1 or below. while I understand the logic, it forces every one in a company to be on the same level, but it is also counter productive in other ways.
If I could open files saved in creo with other versions, I could have wf4 still loaded to open the old manufacturing files to maintain support....problem solved, support for the old system.
but they won't change that..
Our hate for Creo isn't about adapting to change. Like the comment about the steering wheel and the brake being in the right place in a car (don't change it!), that's the point! Another example. Suppose you get a new job, and instead of using MS Excel, your new employer uses Fly-By-Night Spreadsheets. You get used to it, sure - it's CHANGE, after all. Any college student would be happy to use a spreadsheet that doesn't sort, doesn't use formulas, doesn't allow text in the cells - only numbers - SURE! What fun! They need a job, so it's NO PROBLEM. They ask, "what's wrong with the old geezers who miss the sort command - EMBRACE CHANGE!"
This is NOT about change. It's about programmers writing software that functions well, like SolidWorks. It's about a company with excellent customer service (SolidWorks), a company who LISTENS to user input about improvements to software and interface, a company with a huge and supportive user group community (again, SolidWorks). PTC is not even in the ring.
For anyone who wants a copy of my spreadsheet comparing 142 items between Creo and SolidWorks, please provide your name and email address.
I'd like a copy of your spreadsheet.
Preben Reventlow - firstname.lastname@example.org
Starting in a new job next month, working in SolidWorks and Siemens NX.
Keeping my place here in the community in case I return to "Creppo"
Do you follow the news and plans for solidworks? Solidworks has an unclear future, thy are going to dump parasolid kernel and migrate to CATIA kernel, Solidworks will be CATIA lite. Do you know what that implies? it means a nightmare for lagacy data.users are not only fearful of the future, they are feeling the negative imapact for 5 years now. the software has literally stagnated since 2008, when they started working on Solidworks V6. Solidworks LISTENS to customers? are you joking here? Solidworks the company is completely out of touch, the users are completely unaware of what future holds for them, how are they going to use their legacy data? how does the new platform manage their data, are they forced to use ENOVIA V6 crap and cloud just to run their small shops? a ton of unanswered questations. now compare that with Creo, PTC has a clear vision about it, they started informing everyone about whats going to happen to their product when they anounced ProE to Creo transition back a couple of years ago, and now they are following the plan. The future for Creo is BRIGHT, while SOLIDWORKS will DIE, this isn't my word, this is what Jeff Ray former CEO of solidworks has said. what will happen to costumers and third party addons buit for current version of Solidworks, he has NOT said.
BTW, are you comparing Creo elements direct to solidworks? its like comparing apples to oranges, perhaps you think Solidworks is a direct modeler...
The steering wheel use to be horse reins, the brake was a pull on the reins and to go was a kick in the side... Then evolution and the brake was a hand brake and the steering wheel was two levers. The dimmer Switch use to be on the floor board and you had to step out of the car to use a hand crank just to start it. Really... I can understand the frustration.. but I also know every business I worked for if they never attempted to improve the product they would not stay in business. What everyone here should experience is a relationship with Catia.. we complain about start parts that don't migrate forward. I can recreate all my startparts in a day.... Dassult when moving from V4 to V5 completely changed the core of the models. You had to STEP or translate your V4 to V5. How would everyone like that experience. We tend to get complacent with our current situation. Trust me the grass is dead on the other side. Don't get me started regarding cost and additional applications that Dassault charges. $5,000 dollars per person for s STEP license. If you want to share your licence from a US business with your internal design center in China... You can't. At least that was the way it was 6 years ago. I could write a book on how dead the grass is on the other side. It is up to the "expert users" to inform PTC regarding what they want.
For this one, you are correct... the writting has been on the wall for quite a few years. The current core is licensed and Dassault wants to own the engine.