Recently active
I would like to have a new API "ProDefaultAnnotationByViewShow" which shows the annotation on drawing views by default. This is possible manually by setting config "auto_show_3d_detail_items" to "YES". Currently there are no direct API to achieve this functionality. I would like to get a new API. The new API should show the annotation on General and projection views, how it shows when we add view manually. Reference: Case Details: 15578107
According to article CS29394, a saved analysis can only be deleted on the level the analysis was created. To determine what level the analysis was created, choose annotation smart filter and hover the analysis. The article itself dates from 2016 an states it's applicable for Creo 3.0 We are now working on Creo 5.0.5.0, where dis apparently doesn't work. How can a user determine the level where a saved analysis feature was created ?
Currently there's no functionality in Creo to find the best path to assemble or dis-assemble a part into an assembly (sequence of rotations and translations). This is possible in NX, see this movie. To have something like this in Creo would be of great added value.
The "From" and "To" values for a "Curve From Equation" should have the ability to be parametrically driven. One can enter a parameter in the field, but it just reads in the value and becomes a "dead" number.
Common Features already in Creo: Side plane, Top plane, Front Plane, csys, axes, etc. Add a new feature (possibly under the Annotation tab) titled "Engineering Notebook". Feature Description: 1. Create Feature "Engineering Notebook". 2. This feature opens up a large format text dialogue box (think Microsoft Notepad or similar). 3. Engineers can jot down model notes here. Make reminder notifications for future model modifications, improvements. Make notes regarding difficult features that are present in the model. Make notes regarding feature failures, circular references. Make a wish list of features to add to the model when time is available. Make other notes pertinent to the usage, purpose, analysis, or history of the model... These are all text notes relevant to other engineers. This feature is intended to be an engineering notebook written by engineers for engineers. 4. This feature appears as an "Enginee
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea post here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to check that all Orphaned Dependencies Broken and modelupdate to automatically do it. See also: https://community.ptc.com/t5/System-Administration/Creo-Parametric-Dummy-Dependencies/m-p/328439
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check Features set to Read Only and modelupdate to automatically set all features to Read Only (except for family tables and some items that have predefined flexes).
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check for any un-embedded datums or sketches that they should be named
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to check that there are no 0 dimensions for scenarios where they could be constrained to coincident (in sketches, holes, datum planes, etc.)
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check that all sketched dimensions are Locked,, where applicable
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check All dimensions should be named when used for relations. Relations should include initial and post regen.
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check All features and dimensions should be named for family tables
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check Sheetmetal flat pattern won't fail.
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check there are no nested family tables (family tables in an instance of another family table)
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check that Patterns should be set to Identical, where possible, instead of General. For 95% of the time, identical works great, but using general has a much slower regen time, especially for vent holes.
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck/modelupdate remove unnecessary comments. We have old files with some instructions in the relations as comments. We would like them to be removed.
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check for any sheetmetal features not using the default sheetmetal parameters for bend radius, etc...
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check first component in assy is not using external references. Obviously references to skeleton models are ok, but for most of the time, it should be assembled using default.
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check that the first Assembly component is only using default or coincident with default datum planes. The first component should not be placed with dimensions to the default datums. There should not be dimensional design intent for dimensions at the first component. These dimensions should be somewhere else.
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check assy submodels have the proper naming convention. Running modelcheck on all levels isn't really what we are trying to do. We wan to make sure that a specific assembly does not include specific legacy files, whether library or now. We wan to just make sure submodel names are correct.
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck for checking subcomponents in assembly for proper parameters (windChill location, based on naming convention and release state) including component level parameters, like line numbers, etc.
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to check that the assembly is not currently exploded. Modelupdate to unexplode. We've had some individuals checkin and promote assemblies in the exploded state.
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to check that the model not to be in an active Cross-Section. Modelupdate to take it out of cross-section.
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check that Drawing/Annotation Notes to only be used from a certain list, where the notes contain more than one line. The notes can also contain a symbol that can be used as a variable where the user can type anything in and the error won't flag. For instance, one line in the multi-line note can say "REFERENCE PROCEDURE NUMBER 123456". One drawing can have one procedure number and another drawing can have another. Maybe the note can check against "REFERENCE PROCEDURE NUMBER #####".
As a request by @lwestbrook, I am breaking up the massive Modelcheck idea thread here: https://community.ptc.com/t5/Creo-Parametric-Ideas/New-ModelCheck-Ideas/idc-p/692247#M13722 For this idea use modelcheck to Check that Drawing General Views to not reference Geometry that can fail and cause the views with dimensions to have an issue. Better to just reference orientations.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.