A New Outlook on PTC's Pro/Engineer Wildfire




Home > Technical Articles > A New Outlook on Wildfire

A New Outlook on Wildfire
An opinion by Eldon Goates, May 2003

I've been asked by several of you to offer an updated opinion on Wildfire. I've been hesitant as I don't like being negative, but I'm not impressed. Sure, it's a fun toy that makes enticing presentations, but it's not really suited for efficient production work. (An opinion shared by many.)
This opinion stems from an unsuccessful attempt to do a small, complex project in Wildfire. Even after several calls to Tech Support, I was unable to complete the job and had to start over in Pro/E 2001. I'm very sad because I was really looking forward to using the new functionality.
My recommendation: . . . Wildfire is not ready for production. I highly recommend that companies do not migrate, and furthermore, new customers should approach purchases of Wildfire with extreme caution - regardless of propaganda or promises from PTC.
It's truly sad that the very cool new functionality is wrapped in a package so riddled with issues.

Summary:

The biggest issues with Wildfire are in the Lost and Degraded Functionality: * You can't create "Make Datums" anymore (all datums are "hard"). * In many cases you must pick datums from the screen (now cluttered with datums) -- you can't pick them from the Model Tree for instance. * You can't modify Part dimensions directly in Assembly! -- you have to enter a Part mode (which means you can't see dimensions of more than one Part at a time!) * In fact, to see dimensions of more than one feature at a time (in the same Part only), you must pre-select the features all at once! * Many things that were single features are now created as multiple features -- meaning to modify one, you must find and select many. * Selection is now obnoxious in many ways. * Poor modeling practices are now the "Default", so a user must be savvy (and willing to fight with Wildfire), or models will be constructed poorly, making them difficult to change or reuse. * And the list goes on.
No, Wildfire is NOT an "Improvement". There are many cool new things, but the bad out weighs the good, and you can read my long list of reasons. As mentioned in the previous article, it appears PTC is chasing their low-end competitors. They have removed capability and "dumbified" the software. Sure it's simpler, like a Censna is simpler than an F15, but it's also less capable. Why take away great features and functionality?
There is a lot of really cool new functionality in Wildfire -- I wish I could use it -- but I can't justify the inefficiency and difficulty of the rest. Even after implementing PTC's recommended methods the evidence just isn't there. On the contrary, evidence shows that working with models is more difficult, and users will never be as fast, efficient or as capable in Wildfire.
In the propaganda PTC says Wildfire is the end all in CAD . . . but when pressed, they say it's a "Work in Progress". Why should we buy a "Work in Progress"? For my money, I want the finished product !! (And I don't want a SolidWorks look-alike . . . or . . . Perhaps I should buy SolidWorks . . . if that's the "Finished Product" PTC is striving for? . . . which is silly, because Pro/E is the "Finished Product" SolidWorks is trying to be.)

What to do?

It's too bad PTC would choose to output such an inferior product -- especially after stating clearly their understanding that users don't want to fight with the software.
The good news: We don't have to accept this poison pill. As users, we can decided it's just not acceptable and refuse to migrate. Here are several other ideas on sending the message.
I am indeed sad about the wasted years of development, and I wish the cool new functionality was in a usable package. The worst part is PTC invited several groups (for customer input), but obviously didn't listen to much we said a year ago. Maybe they'll learn something about listening to the customer as we all refuse Wildfire . . . and refuse to pay the maintenance of with it.

More Detail?

If you're interested in details supporting these conclusions, here is the long list (uncensored).
Are you as frustrated as I? Here are some alternatives to taking the poison pill.
Do you disagree? Post your own opinions. I sent this list to PTC's management requesting their views to post here (in fairness and for completeness) -- unfortunately, they have been unable to refute it.
Disclaimer: These are my opinions, and though not without emotion, they are based on fact. The long list includes plenty of detail and evidence to support the accusations. More...

Please join me in refusing to accept this fiasco they call Wildfire.

A New Outlook on Wildfire An opinion by Eldon Goates, May 2003
	I've been asked by several of you to offer an updated opinion on Wildfire. I've been hesitant as I don't like being negative, but I'm not impressed. Sure, it's a fun toy that makes enticing presentations, but it's not really suited for efficient production work. (An opinion shared by many.) This opinion stems from an unsuccessful attempt to do a small, complex project in Wildfire. Even after several calls to Tech Support, I was unable to complete the job and had to start over in Pro/E 2001. I'm very sad because I was really looking forward to using the new functionality. My recommendation: . . . Wildfire is not ready for production. I highly recommend that companies do not migrate, and furthermore, new customers should approach purchases of Wildfire with extreme caution - regardless of propaganda or promises from PTC. It's truly sad that the very cool new functionality is wrapped in a package so riddled with issues.
Summary:
	The biggest issues with Wildfire are in the Lost and Degraded Functionality: * You can't create "Make Datums" anymore (all datums are "hard"). * In many cases you must pick datums from the screen (now cluttered with datums) -- you can't pick them from the Model Tree for instance. * You can't modify Part dimensions directly in Assembly! -- you have to enter a Part mode (which means you can't see dimensions of more than one Part at a time!) * In fact, to see dimensions of more than one feature at a time (in the same Part only), you must pre-select the features all at once! * Many things that were single features are now created as multiple features -- meaning to modify one, you must find and select many. * Selection is now obnoxious in many ways. * Poor modeling practices are now the "Default", so a user must be savvy (and willing to fight with Wildfire), or models will be constructed poorly, making them difficult to change or reuse. * And the list goes on. No, Wildfire is NOT an "Improvement". There are many cool new things, but the bad out weighs the good, and you can read my long list of reasons. As mentioned in the previous article, it appears PTC is chasing their low-end competitors. They have removed capability and "dumbified" the software. Sure it's simpler, like a Censna is simpler than an F15, but it's also less capable. Why take away great features and functionality? There is a lot of really cool new functionality in Wildfire -- I wish I could use it -- but I can't justify the inefficiency and difficulty of the rest. Even after implementing PTC's recommended methods the evidence just isn't there. On the contrary, evidence shows that working with models is more difficult, and users will never be as fast, efficient or as capable in Wildfire. In the propaganda PTC says Wildfire is the end all in CAD . . . but when pressed, they say it's a "Work in Progress". *Why should we buy a "Work in Progress"?* For my money, I want the finished product !! (And I don't want a SolidWorks look-alike . . . or . . . Perhaps I should buy SolidWorks . . . if that's the "Finished Product" PTC is striving for? . . . which is silly, because Pro/E is the "Finished Product" SolidWorks is trying to be.)
What to do?
	It's too bad PTC would choose to output such an inferior product -- especially after stating clearly their understanding that users don't want to fight with the software. The good news: We don't have to accept this poison pill. As users, we can decided it's just not acceptable and refuse to migrate. Here are several other ideas on sending the message. I am indeed sad about the wasted years of development, and I wish the cool new functionality was in a usable package. The worst part is PTC invited several groups (for customer input), but obviously didn't listen to much we said a year ago. Maybe they'll learn something about listening to the customer as we all refuse Wildfire . . . and refuse to pay the maintenance of with it.
More Detail?
	If you're interested in details supporting these conclusions, here is the long list (uncensored). Are you as frustrated as I? Here are some alternatives to taking the poison pill. Do you disagree? Post your own opinions. I sent this list to PTC's management requesting their views to post here (in fairness and for completeness) -- unfortunately, they have been unable to refute it. Disclaimer: These are my opinions, and though not without emotion, they are based on fact. The long list includes plenty of detail and evidence to support the accusations. More...
Please join me in refusing to accept this fiasco they call Wildfire.