Recently active
What product version are you running?2Describe the ProblemgfdhfdghAre you using a work around?gdfhdgfhWhat is the use case for your organization?gdfhdfghWhat impact does this problem currently have on your organization?gfdhdfgh
What product version are you running?2Describe the ProblemsdafsdafdsafAre you using a work around?asdfsdafWhat is the use case for your organization?asdfasdfWhat impact does this problem currently have on your organization?asdfasdf
What product version are you running?Version 2Describe the ProblemfdsgfdsgAre you using a work around?fdsggsfdWhat is the use case for your organization?fdsgsfdgWhat impact does this problem currently have on your organization?fdsgsdfg
What product version are you running?Version 3Describe the ProblemZXXZXAre you using a work around?ZXZXWhat is the use case for your organization?ZXZXWhat impact does this problem currently have on your organization?ZXZX
1. Describe the Problemhttps://www.ptc.com/en/support/article/CS130026?source=searchLists an SPR that was created for this. I want to make sure it's still a priority.Marker and tape labels created in Creo Cabling show their text tags.We would like a way to turn these off via a layer, similar to datum entity layers.2. Are you using a workaround?Turning off points display is the only way to hide these text labels.3. What is the use case for your organization?It affects every Creo Cabling user and everyone who views these harness assemblies in other higher-level assemblies.4. What impact does this problem currently have on your organization?Frustration when a user needs to see points but gets a bunch of text labels on top of them in large assemblies. Status changed to: Archived 2026-07-06We are archiving this idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement. You can always post a new idea with a
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 sa
1. Describe the ProblemIn Creo Simulate Live it is not possible to add a mass item as a point mass. A Modal Analysis of CSL cannot be performed correctly in our usecases if we cannot assign a point mass that for example simulates the engine since we do not have the model of the engine yet (supplier part) but have to continue our design. To connect the point mass (=engine) to the rest of our design also the rigid/weighted link connections of Creo Simulate would be needed.2. Are you using a workaround?For structure simulation study it is possible to add a force on a point that has the load of the gravity*mass of the object to be simulated. But that does not work for ModalAnalysis.3. What is the use case for your organization?Being able to use CSL also for ModalAnalysis without having to wait for engine models.4. What impact does this problem currently have on your organization?not being able to use ModalAnalysis of CSL
1. Describe the ProblemFor CSL there is no possibility to define areas for "finer" meshing. Depending of the size of the overall model it can happen that very small objects will be ignored since they almost do not exist in comparison to the size of the overall model. For example in CSL CFD analysis it would be good to be simulate a outlet nozzle. This is also relevant for structural and modal analysis since small objects will also be almost ignored there but could have a big impact. 2. Are you using a workaround?no workaround in CSL is used. Using other simulation tools3. What is the use case for your organization?Being able to use CSL for the described UseCases.4. What impact does this problem currently have on your organization?Not being able to use CSL for the described UseCases.
1. Describe the ProblemMissing stud welding operations include annotation symbol according to ISO 2553-2019.Add Stud Welding as an similar welding feature as spot welding. See also Picture 1 and 2.Add / Update all relevant Welding Symbols (Annotations) as per NEWEST ISO Standard.2. Are you using a workaround?To show relevant Stud welding at least within the manufacturing drawing, a new Symbol needs to be created to fulfill latest ISO compliance.3. What is the use case for your organization?Having relevant welding process operations with correct symbols according to ISO Norm available.4. What impact does this problem currently have on your organization?Self creating symbols to show at least Symbol according to ISO Norm as annotations within drawing.
1. Describe the ProblemCurrently the GEOM_CHECKS check is only applicable to Parts, not Assemblies. Addint this to Assemblies would be very valuable.For example, it is possible to check for a Minimum Bend Radius Violation of Piping Assembly via the Geometry Checks troubleshooter, but given that the check is on Assembly level (not Part level) the GEOM_CHECKS check does not report it and a user can still check in a Piping assembly containing a violation (ModelCheck Gatekeeper) See PTC article CS458454 which covers this topic.2. Are you using a workaround?It is possible to check the Minimum Bend Radius via Geometry Checks troubleshooter3. What is the use case for your organization?ModelCheck Gatekeeper is used to check model integrity an ensure users check in a clean model. the GEOM_CHECKS is one of the checks currently used, but given that this only applies to Part Mode, users are able to check-in Piping models with Minimum Bend Radius violations, as Piping models report the Ge
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 adjustmen
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
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 "
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
1. Describe the ProblemThrough Creo customization via UIEventListener with ProCmdModelSave, we never want to save to disk subcomponent models with "Read Only Features". We can stop the save but we always get this Error:If the windowed model is not set to "Read Only Features", it will save to disk, but we don't want any of the subcomponents to be saved. When setting the "Read Only Features" on subcomponent for an assembly or drawing, the model's internal version number is incremented causing Creo to think that the model needs saving. We would like some way to just suppress the "Disk Error" message.2. Are you using a workaround?We just tell the user to ignore the message.3. What is the use case for your organization?"Read Only Featured" should not be saved to disk.4. What impact does this problem currently have on your organization?Worry by users that they are not correctly saving their Assemblies and Drawings to disk.
1. Describe the ProblemWhen working in 3d, I have a light-ish background, so I have geometry and text set to a dark color. These colors work great for me in 3d, but not so great in 2d. For 2d, I would like to have a dark background, but the geometry and text colors would need to be changed to a light color, which wouldn't be easy to see in 3d. Rather than trying to find text and geometry colors that work ok in both 2d and 3d, can you add the option to control these separately? In the System Appearance section of the options menu, "Text" and "Geometry" could split into something like "3d text", "2d text" and "3d geometry" and "2d geometry" or under "Global Colors", add a separate section for "2d colors"
1. Describe the ProblemWeld preparation features should be added as assembly level features (or at least have the option to set this). At the moment they are part level features.If you want to weld 3 identical plates together you cant add different weld prep to each part based on where it is located in the assembly. This forces you to use instances or new part numbers for parts that are identical.Also when you create a fabrication drawing you often want to detail the parts and the welded assembly on the same drawing. You don't want the weld prep to display on the drawings of the plates when they are cut-out.2. Are you using a workaround?Creating the weld prep manually.3. What is the use case for your organization?Fabrication assemblies.4. What impact does this problem currently have on your organization?Slows us down.
1. Describe the ProblemProvide API for changing the parent of annotation (i.e. note) from feature to model. 2. Are you using a workaround?No workaround available3. What is the use case for your organization?We wanted to change the notes associated to feature to associate directly to the model through toolkit customization but no API available currently.4. What impact does this problem currently have on your organization?Not able to implement this feature for the customers
1. Describe the ProblemI don't know how CREO has gone so long without updating its drawing overlay/comparison. The problem is that when you overlay a drawing sheet you can't change colors. You can't identify what is different or what has changed between revisions.2. Are you using a workaround?Export as PDF or DXF and use a different software3. What is the use case for your organization?One can easily see changes between revisions4. What impact does this problem currently have on your organization?time consuming to export everything and use another software to compare.
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. Curr
1. Describe the Problem Reference ticket C17949994 When ECAD copper data is added to a PCB, it is shown at higher level assembly drawings in random locations for exploded views. This is a bug. R&D says that we should use the hidden dtl option: antiquate_drawing 6982560 I am personally not a fan of this workaround for 2 reasons: Antiquating a drawing undoes a 'fix' that was implemented for some other reason. I'd prefer not to inject an issue into the drawing to fix another bug. A bug fix shouldn't require someone to find an article (to be created) and put in a secret code. It should be more robust that applies to all users without this level of workaround. It needs to be addressed for each user in each company. 2. Are you using a workaround?antiquate_drawing 6982560 3. What is the use case for your organization?Using ECAD Copper data on a PCB and then having exploded views in a drawing at the product level4. What impact does this problem currentl
What product version are you running?3.2Describe the ProblemCAD Community Popular tagsOther General Are you using a work around?CAD Community Popular tags OtherGeneralWhat is the use case for your organization?CAD Community Popular tags OtherGeneralWhat impact does this problem currently have on your organization?CAD Community Popular tags OtherGeneral
What product version are you running?3.2Describe the ProblemHow to call a form processor on a wizard jsp which is not being called from an actionAre you using a work around?How to call a form processor on a wizard jsp which is not being called from an actionWhat is the use case for your organization?How to call a form processor on a wizard jsp which is not being called from an actionWhat impact does this problem currently have on your organization?How to call a form processor on a wizard jsp which is not being called from an action
What product and version are you running?Double click againDescribe the ProblemDouble click againAre you using a work around?Double click againWhat is the use case for your organization?Double click againWhat impact does this problem currently have on your organization?Double click again
What product and version are you running?Version 3Describe the ProblemTesting Double ClickAre you using a work around?Testing Double ClickWhat is the use case for your organization?Testing Double ClickWhat impact does this problem currently have on your organization?Testing Double Click
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.