Creo Parametric Ideas

 Creo 4 introduced: 1. 'Shown Items' layer enabling to show an item quickly, not having to search for the layer(s) it is in. 2. AND it introduced 'hidden by layer is hidden in model tree as well'   At least.. I thought this was the intent of the enhancement... appearantly not...   Problem; Some items hidden by some types of layers are hidden in Model Tree, most items hidden by layer are NOT hidden in Model Tree; NO LOGIC there Problem2; As a result you need to go to layer tree and search for a layer with the item after all to RMB show the item (and make it 'shown' independent of layer status) Problem3; Items can be both is the 'shown items' layer and the 'hidden items' layer; BAD OVERVIEW   ... View more

Up to Wildfire 4 it was possible to select annotations (dimensions, axis, ...) during the show / erase dialog by using a selection box. User was able to select an area with a rectangle. Since Creo the new dialog does not allow or support this procedure. User must select or deselect each item in an area by mouse click. Would be nice to have the old feature again. ... View more

Dear Sir ,   I have clients who are getting parts from Tata Motors division in Catie format.They are using creo software for importing and using the design for downstream activities. Since tata Motors has upgraded their Catie version to V6 R28 but as per the creo compatibility matrix , we cannot import Catie file since we are supporting only upto  Catie V5. Request you to look into this asap. Regards, Rahul Sardar Santi Software LLP ... View more

If I am working collaboratively and publishing many quilts it would be nice to have a dashboard to be able to see all published elements, re-name and re-define them.   Similarly in a part with many imported publications it would be helpful to see a list of imported publications and easily re0route to a different part.   This is done vary well in Catia, at the moment we cannot work collaboratively (ie sharing data between many designers) in Creo in the same as we do in Catia because there is no way to easily manage the publications coming in and out of the part. ... View more

Actuellement les tables de trous ne supportent pas les parametres thread_depth et drill_depth. Les profondeur sont calculé directement dans CREO lors de la creation des trous standards. Les profondeurs proposé par defauf ne correspondent pas au standard (NFE 25-030).   Ajouter les parametres thread_depth et drill_depth à la table de trous afin de pour piloter ces 2 profondeurs comme les autres parametres ( FASTENER_ID  BASIC_DIAM  THREAD  TAP_DR ....)       ... View more

Les zones text supplémentaires des tolérances géométrique ne supportent pas l'utilisation des symboles (&p99). Elles affichent le texte brute : &P99 sera affiché en &P99 en non le nombre d'instance d'une repetition. ... View more

Please allow "Medium Fit" to be available for use with other standard hole types.  Currently it is only available for ISO holes.   UNC Holes   ISO Holes   Adding this will require populating the medium fit values in the .hol files.   Once this is working, please allow "Medium Fit" to be configurable as the default fit when placing new holes.  (See existing idea for that.) ... View more

Parameter values from a STEP file fail to import if 'use templates' is enabled and the template model contains matching parameter names. The whole point of using template models is to make sure that all planes, views, and parameters exist in every model. Using a template during import shouldn't block the parameter values from being transferred in. ... View more

Usually when placing a cross section, it is an engineer's intent to place the cross section arrows on the view that the cross section is enabled on. Sometimes they would like to move it to another view, but oftentimes it just stays on the view the cross section was enabled on. This would save digging around the View Properties menu for the arrows table entry, or needing to click the Arrows UI button multiple times. ... View more

In cases a model is saved in a higher revision of Creo it can not be retrieved. Currently this message will not offer the reason why and it can be different.  "can not be retrieved" will not really offer the user any idea why and it should be implemented a mechanism to interpret models saved in a higher version to offer text. "Model already stored in a higher version and can not be retrieved anymore." ... View more

When replacing a component, the Family Tree dialog box only shows the filename column. Additional columns (eg: Common Name) have to be configured to be shown everytime when accessing the dialog box. I will be helpful if the Familyt Tree dialog setup (columns) can be saved. ... View more