3 ms·
I'll have to work through the 650 pages. I use CATIA v5 every day, first released in 1998. It's sharp and crusty and huge, but does everything (with the right
by tape_measure 2y ago
I'll have to work through the 650 pages.
I use CATIA v5 every day, first released in 1998. It's sharp and crusty and huge, but does everything (with the right license).
- smartis2812 2y agoMe too. But I really looking forward to it.
- nraynaud 2y agoFunny, I'm French, and I know people who developed a bit of it.
- buildsjets 2y agoIf you really push CATIA hard, you can get it to crash in French, or at least crash with a poorly translated error message. "The Document cannot be unloaded because he is dirty" was one of my favorites.
- satiric 2y agoI like the "Click OK to terminate" error. As though it wants to make sure it has my permission to crash.
- WillAdams 2y agoYeah, the whole button for user to click "Okay" for something which is abjectly _not_ acceptable has _got_ to go away. Please replace it with "Understood" or "Acknowledged".
- guenthert 2y agoOr the not too uncommon "dismiss".
- buildsjets 2y agoI keep a PowerPoint with screenshots of bizarre CATIA/ENOVIA error messages. It's up to 8 slides now, completely covered with errors. A few other highlights: "As it was too important, the number of workspaces has been reduced." "Primitive Value is not an AggrInstance" "Instead of directly transforming an import, we recommend you apply the Add Position contextual command onto the solid. Then the required GSD transformation must be applied to the axis system of the Positioning Set. Do you want to go on with the transformation or quit the command and follow our recommendation? (Yes/No buttons)" "A problem occurs during Process." "Error: Error Stack is empty." an empty dialog box with options of "OK" or "Cancel." "An error condition has been detected, but no error information." While performing a Surface to Surface analysis: Status: 104% complete, 1193hr 2min 46sec remaining. "Cannot bitblt" "Technological Package found use appropriate engine to handle it. It can not be saved as a File."
- buildsjets 2y agoCrusty it is. The fillet tool STILL totally sucks after 27 years, and I STILL frequently find myself needing to define surface geometry, fillet the surface, and use that to split the solid rather than just directly filleting the solid, in order to get the same type of fillet intersections that you get when you machine the part.