Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Combine Simple_flat.hol and Simple_drilled.hol into a single file (Simple.hol)Archived

1. Describe the Problem In Creo 10.0.0.0, the new Simple Hole functionality introduces two separate hole chart files:simple_flat.holsimple_drilled.holThis differs from the existing standard hole format, where multiple hole types are defined within a single .hol file by using the HOLE_TYPE parameter (e.g., TAPPED, DRILLED, CLEARANCE, etc.).For standard holes, a single .hol file may contain several hole types: DEFAULT_CALLOUT_FORMAT_DATAHOLE_TYPETAPPEDDRILLEDCLEARANCE However, Simple Holes do not follow this same structure. Even though the HOLE_TYPE parameter already includes:SIMPLE_FLATSIMPLE_DRILLEDthese two options are split into two separate .hol files instead of being consolidated into a single chart.This creates inconsistency and unnecessary burden for CAD administrators. Instead of reusing familiar formatting from the existing hole tables, admins now have to work with two additional files with a different structure, even though the hole types could be handled the same way as existing standard holes.2. Are you using a workaround?Right now, the only practical workaround is to use the two separate files (simple_flat.hol and simple_drilled.hol) exactly as Creo provides them. Since both simple hole types cant exist in a single .hol file, we currently have no option except to maintain and edit each file individually whenever we need to update simple hole callouts or parameters.3. What is the use case for your organization?If Simple Holes were consolidated into a single .hol file just like standard hole tables then administrators would only need to update one file for simple holes, all callouts could be managed in one place. This would eliminate the need to learn or maintain two separate formats, reduce repetitive work, and significantly cut verification time when they are updated.4. What impact does this problem currently have on your organization?Right now we’re using the two-file format that Creo provides, but it’s not ideal. Managing two separate simple hole files is tedious, and every formatting change has to be done twice. It’s repetitive, easy to mess up, and generally a pain to maintain compared to the single-file structure used for standard holes.

Adjust method to redefine 2D drawing dimensions in case of changing model componentsArchived

1. Describe the ProblemIt appears that component references get lost and have to be manually redefined.We would like to "correct" purple dimensions by only resetting the lost reference instead of manually redefining all dimensioning references. In the following example, after the upper component is lost, the dimensioning remains purple, although the lower end of the dimensioning is apparently still present. It is a pity that this dimensioning has to be completely redefined. It is currently not possible to reassign individual dimensioning references, such as only the upper edge of the lost component in this case and to "reuse" the lower circular edge. 2. Are you using a workaround?As has already been clarified with PTC, it is currently not possible to redefine/edit a dimensioning without recreating it.3. What is the use case for your organization?We assume that the greatest advantage will be for very detailed and large drawings, where time is saved for each necessary adjustment of the 2D drawing, as only half of the dimensioning needs to be redefined.4. What impact does this problem currently have on your organization?The most significant impact is expected for the mechanical design departments by reusing existing 2D drawings more efficiently and to generate proper production documentation faster with the described possibility.

Enhance Balloon Note FunctionalityArchived

1. Describe the ProblemThe issue revolves around balloon notes in Creo, which currently have limited functionality and don’t offer the full potential they could. In its current form, the balloon note is essentially a manual BOM balloon, but lacks key features that would make it more effective, especially when compared to true BOM balloons. One of the most critical missing features is the ability to stack balloons, which would allow them to orbit each other (similar to BOM balloons). This feature could have huge potential for inspection processes, as stacking and orbiting balloons would allow for more efficient marking and tracking of inspection items.Another feature that could greatly improve the usability of balloon notes is the removal of Menu Manager and use of the Format Tab ribbon. Additionally, the ability to use custom balloons, such as alternate BOM balloons, would enhance flexibility. There's also an opportunity to add a BALLOON_NOTE layer to Modelcheck UPDATE using making it easier to designate them on a PDF automatically.2. Are you using a workaround?Currently, we rely on multiple inspection balloon symbols from the symbol palette to mimic the stacked effect. However, this workaround is not ideal. While it's possible to visually align the balloons next to each other, it's a tedious process and lacks the bom balloon functionality that would make things more efficient. There are some options for grouping balloons by color or connecting them in a massive groupt, but they often add unnecessary complexity. We're considering third-party software for balloon automation to help, but even with these tools, the balloons themselves are disconnected and lack the needed functionality, such as leaders or proper alignment (vertical or horizontal).3. What is the use case for your organization?If the balloon note functionality could be updated to: Use the modern UI and Format Tab. Include the ability to stack balloons and orbit them around each other. Allow for custom balloon shapes (similar to alternate BOM balloons). Add Modelcheck UPDATE layer integration to automatically organize balloon notes on a specific layer. Then the balloon notes could serve as a better alternative for inspection management compared to our manual process. This would also open up options for third-party tools that use balloon notes with auto-numbering, offering more flexibility. Since balloon notes are controlled by settings in the DTL file, it would be easier to manage font and text size with model check, providing better consistency and customization compared to current solutions.4. What impact does this problem currently have on your organization?The current process is inefficient and time-consuming. Manually placing and managing balloons takes up a significant amount of time, and there's potential for major productivity improvements without needing third-party tools. The functionality to edit balloon note placement, stack them, and integrate them with existing features like Modelcheck UPDATE could dramatically reduce time, streamline workflows, and improve the inspection process.

Fix discrepancy between thread callout notes created by "hole" tool and "cosmetic thread" toolArchived

1. Describe the ProblemThread notes created using the "hole" tool and the "cosmetic thread" tool are completely different despite both being created with the same .hol file as a reference. Here is a part I made up to demonstrate the issue:  Step 1: Using the "Cosmetic Thread" tool, I selected the "Standard Thread" option, then specified a 3/8-16 thread using my UNC.hol file.  Step 2: The hole was created using the hole tool as a "Standard" hole, with the 3/8-16 thread specified from the same UNC.hol file used in the previous step.  Here is the feature tree for this part:  Step 3: Now we go to 2d and add a general view to the drawing.   Step 4: Using the "Show Model Annotations" tool, I selected the notes created in steps 1 & 2.  Step 5: Now we see the problem. Despite these threads being created with the same UNC.hol file as a reference, the notes are formatted completely differently.  For the hole, we get "3/8-16 UNC THRU", which is what is set up in the UNC.hol file.  But for the threaded shaft, we get ".375 - 16.000 UNC - EXTERNAL", which not only isn't what we want, it also doesn't match common professional practice (where are UN series threads ever called out with decimals, let alone with 3 decimal precision?). Drawing with bad notes Can you please fix this so that internal and external threads created with the exact same .hol file have consistent note formatting? (Also, please fix the hole notes so that they rotate around the hole axis and not the hole edge per ASME Y14.5 sec 4.4.4.2) Thanks. 2. Are you using a workaround?No3. What is the use case for your organization?We are a government organization creating thousands of part drawings for fabrication at a variety of manufacturing facilities. We need our annotations to be consistent without having to manually edit them.4. What impact does this problem currently have on your organization?Affects all users creating manufacturing drawings. Lost productivity and manufacturing/cost issues from hand-edited notes are unestimated.

Improvement Suggestion – Appearance Organization in Creo ParametricArchived

1. Describe the ProblemDear Team,We operate in an environment where several industries use Creo Parametric for the creation and editing of appearances applied to parts and wires. We are currently using Creo Parametric version 12.0.2.0.We would like to suggest an improvement related to the organization of custom appearances. Currently, all created appearances are grouped under the “My Appearance” tab, which mixes appearances intended for wires, solid models, and sheet metal. This limitation directly affects organization and workflow efficiency.Our suggestion is to allow the creation of new custom tabs or categories within the Appearance Manager, enabling users to separate appearances by application type (wires, solids, sheet metal, among others).This functionality would significantly improve ease of use when creating and editing appearances, as well as provide better color organization. As a direct result, it would also help reduce design time, leading to increased productivity and cost savings for companies.Thank you for your attention. We remain available for any additional details or practical examples of this request.2. Are you using a workaround?leaving all the colors together in my appearance or keeping separate (.dmt) files and loading them whenever necessary3. What is the use case for your organization?wire and cable designs4. What impact does this problem currently have on your organization?a matter of speed and organization

Convex hullArchived

1. Describe the Problem Hi, Creo currently lacks a native capability to create and analyze a Convex Hull from geometry. This limitation prevents users from performing several engineering-critical analyses directly within the CAD environment.   Key missing capabilities include: Stability and tipping analysis based on the Convex Hull of support points, legs, or wheels, including verification that the projection of the center of gravity lies within the support polygon. This is essential for cranes, mobile robots, industrial equipment, and heavy machinery. Packaging and minimal volume analysis, including verification of fit within shipping containers and identification of regions where additional protective padding is required. Biomedical engineering analyses such as orthopedic implant stability using the Convex Hull of bone–implant contact regions. Generative Design workflows, where engineers need an optimal design-space envelope that tightly conforms to the external geometry. Current auto-envelope tools are often too large and detached from the actual model, leading to wasted design space and suboptimal optimization results. Current bounding-box-based tools provide overly conservative approximations and do not represent true worst-case geometric or physical conditions, which typically occur on the convex boundary of the model. 2. Are you using a workaround?Yes, but the available workarounds are complex, inefficient, and unsuitable for regular engineering workflows. In order to perform Convex Hull analyses, data must be exported from Creo to external tools such as MeshLab and Qhull, or processed through custom scripts in MATLAB or Python. These tools operate outside the CAD environment and require significant manual preparation, data conversion, and validation. This process breaks full model associativity and makes iterative design studies extremely difficult. Even small design changes require repeating multiple steps, including re-exporting data, recalculating convex hulls, and manually interpreting or re-importing results. The lack of direct integration increases the risk of inconsistencies, interpretation errors, and outdated analysis results being used in design decisions. As a result, these workarounds are often avoided altogether or replaced with overly conservative approximations, which negatively affects analysis accuracy and engineering confidence.3. What is the use case for your organization?Packaging Optimization: Determine the optimal packaging size and shape by calculating the minimal convex volume of the assembly. Identify precise locations for protective padding inside the package based on the convex hull boundary, ensuring safety during transport while minimizing material waste. Biomedical Engineering: Assess orthopedic implant stability by analyzing the Convex Hull of bone–implant contact regions.4. What impact does this problem currently have on your organization?The absence of a native Convex Hull capability increases engineering effort, analysis time, and technical risk from Non-associative geometry. user are forced to rely on external tools or overly conservative approximations, which reduces analysis accuracy and limits the ability to perform rapid design iterations. This results in longer design cycles and increased potential for errors due to disconnected analysis workflows. Integrating Convex Hull functionality directly into Creo would significantly improve efficiency, analysis quality, and engineering decision-making across multiple disciplines.