Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Way to configure CreoView to not add Default and Empty View to filesAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Running on Creo Parametric 10.0.8.0, CreoView 11.1, Windchill 13.0.22. What is the problem?Representations generated from Annotated CAD models with combined states are adding a Default View and Empty View when representations are generated from Windchill.The response was that CreoView always adds these states.It is causing confusion when providing representations or users are looking at representations and the data has information not in the model creating a disparity with the viewable, which makes the delivered file undesirable for viewing model-based dataset.Would like an option to make it so these aren't part of the CAD representation, or have the ability to set which Viewable State the file would open in, and if those 2 Views have to be there for CreoView have a preference/option to hide those by default.3. Are you using a workaround? If yes, please describe it.Telling folks that are viewing the file "Everything in the CreoView representation is generated from the model EXCEPT the Default View and Empty View, but the one called Default under Viewables is from the model"4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.Looking to make the deliverables from Model Based Definition datasets as digestible as possible and consistent between viewers to minimize confusion and adoption.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Causes confusion for users digesting and adopting Model Based Data sets.

Retrieve annotation plane normal vector of a feature based dimensionArchived

1. Describe the ProblemNot able to retrieve the information of the annotation plane & it's normal vector of a dimension which is from a feature (e.g, dimension from an extrude, revolve, etc).2. Are you using a workaround?No workaround3. What is the use case for your organization?I have part with set of features & a drawing with few 2D views of the part. I need to show the model annotation in the drawing. For example, I need to show the dimensions of a hole feature. I would like to show the dimensions with best shown 2D view. If a hole is normal to FRONT view - I need to show the diameter & location from top side surfaces in FRONT view of drawing. And hole depth dimension in TOP view. In order to do this, I need to retrieve the normal vector of the feature dimension, so that I can do some math to find the best 2D view to show the dimension. If there's any alternate workaround, then please let me know how to approach this,4. What impact does this problem currently have on your organization?High impact. We're working something on Automatic Dimensioning. I need this feature.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 all the details required in the form.Thank you for your participation.

Sheetmetal transitionAcknowledged

1. Describe the ProblemRequirement: We're currently facing a critical limitation in our sheet metal design workflow: Creo lacks native functionality to create square-to-round transitions, which are essential for hopper designs. While we've developed a workaround, it's both time-consuming and compromises accuracy. This gap is especially frustrating given our deep investment in Model Based Definition (MBD). We've spent significant time and effort building a robust MBD workflow that allows us to represent both formed and flat states within a single sheet metal model—streamlining communication between design and manufacturing.Unfortunately, because Creo doesn't support this transition geometry, we're forced to rely on Autodesk Inventor for its lofted flange feature. This dependency disrupts our goal of a unified, model-driven process and introduces inefficiencies and data fragmentation. It’s a roadblock in our journey toward full MBD adoption across the enterprise. For a company committed to digital continuity and manufacturing precision, this missing capability in Creo is more than a feature request—it’s a strategic necessity.Functional Requirements:Converged:  Most of our transitions need to be converging at the square/rectangular corners (see image below)Figure 1: Converge Figure 2: Rounded Corner (Not Converged) Control of Facet Length:  We should be able to control the minimum length of the facet of the transition  Controlling the facet length is essential in V-die bending because the material must rest securely on the die surface to ensure a proper bend. The size of the V-die is selected based on the material's thickness, and each die requires a minimum flange length to support the material during the break. When forming accurate transition quarter sections, it's important to bend fresh, unbroken material each time. To achieve this, the previous bend line must lie outside the V-die during the next operation. This is only possible when the facet length exceeds the opening of the V-die, allowing each new bend to occur without interference from the last  Eccentric Transition:  Should be able to work with eccentricity.     @AR_11005271   2. Are you using a workaround?We are forced to rely on Autodesk Inventor for its lofted flange feature and bring the translated part into the Creo assemblies.3. What is the use case for your organization?We manufacture industrial filtration equipment, which often includes hoppers that require complex transitions from round to square or rectangular geometries. This feature will help us complete the MBD workflow for all of our equipment.4. What impact does this problem currently have on your organization?1. Reduces design efficiency and increases lead time 2. Complicates data management and traceability 3. Prevents full adoption of MBD across our sheet metal operations 4. Forces reliance on external software, increasing overhead and training requirements

Color gradient thickness analysis in Creo ParametricImplementation In Progress

1. Describe the ProblemCurrently, thickness analysis feature is, sadly, inferior to the solution provided in the tools from other vendors - and also to another tool of PTC portfolio. In most modern 3D design tools we have a full rolling ball analysis with color gradient flow indicating how thickness varies on the external surface of a part – making it easy to identify manufacturing defects: In Creo, you can only specify some limits and that’s it. The results, according to our engineers, are not good enough to assess the potential issues: As I made my research, to my surprise, I noticed that PTC owns a tool not only with a rolling ball, but also with ray method and others (gradients).This functionality (the best I’ve seen so far) is available in a tool that is in a lower tier than  Creo; that is in Onshape (https://www.youtube.com/watch?v=ULI0yQIGZkU).The tweaking in functionality of the tool – easy win for PTC development team – would beto do do the following:Shoot the ball from every point as usual, but instead of marking the points where the thickness is above or below, just store the diameter value. This way we can have a table with polygon (or vertex) number, ball diameter value and color value. We can then sort this table by thickness, assign color of a gradient range to each of the polygons and color the texture of the external surface. The result will bring tremendous value to the users.I’d love to know when you are planning to carry that functionality over to Creo? 2. Are you using a workaround?We are currently using this functionality in tools from other vendors.3. What is the use case for your organization?The use case is to assess the quality of the external surfaces of plastic parts before the components go to injection mold design team for detailed assessment. This allows for significant reduction of rework time.4. What impact does this problem currently have on your organization?We are unable to successfully implement Creo for teams who's design process relies on this feature.

diamond patternArchived

1. Describe the ProblemThe "square fill pattern" and the "diamond fill pattern" are identical.  You can rotate the square pattern by 45 degrees to get the diamond pattern, and a diamond pattern rotated by 45 degrees is a square pattern.  The diamond pattern should be similar to the hexagon pattern, but with the ability to set the spacing in the X and Y directions independently and/or to set the X spacing and the angle of the diamond. Creation of a diamond mesh using a workaround of 2 directional patterns:   2. Are you using a workaround?This can be achieved by using 2 "direction" patterns, since a direction pattern allows different spacing in the X and Y directions. A second direction pattern of a second feature is needed to get the "offset" members. See screenshot in the problem description.3. What is the use case for your organization?A practical application would be the diamond shaped mesh of an expanded metal mesh. See screenshot in problem description.4. What impact does this problem currently have on your organization?Minimal impact. This would make the diamond fill pattern actually a diamond instead of a redundant rotated square fill pattern.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 all the details required in the form.Thank you for your participation.

Ability to "update" a merge or inheritance feature that is set to "manual update"Archived

1. Describe the Problem For all copy geom, merge or inheritance features there should be a way to do an update for features set to "manual update"   Perplexing, there is an "update inheritance" right click context menu option when inheritance models are set to "automatic". If its "automatic" you shouldn't need a context menu to update it.   There is no such menu or button for updating it when it is set to a "manual update" though.  2. Are you using a workaround?Yes, I change the feature to "automatic update", click ok and then I have to go back in and redefine it again as a manual update. This is defined as the procedure in this support article: https://www.ptc.com/en/support/article/CS2630613. What is the use case for your organization?The naming of "manual update" implies that there is a way to update it manually. There is no such option and it is confusing to new users which means we have to train people for something that the GUI should have built in.4. What impact does this problem currently have on your organization?All new users need to be trained on this which costs money. Users taking time to find the button that doesn't exist costs money.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 all the details required in the form.Thank you for your participation.

Include Creo Platform Updates in enterprise automated patching providers like PatchMyPCAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?  All versions and MORs of Creo Parametric and Windchill Workgroup Manager that use Creo Platform Services with Chromium Embedded Framework (CEF).2. What is the problem? Per CS404101, regular patches to Creo Platform Services will be made available from PTC.   IT departments use tools to automate deployment of countless patches for operating systems and dozens of applications.  Any patches that do not participate in automated patch management and deployment tools adds to the workload for IT departments or application owners.3. Are you using a workaround? If yes, please describe it.  Manually search for updates on PTC support site, then download the patches, then create deployment for SCCM, then test it, then deploy it.4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.  Make the option to include all Creo Platform updates in enterprise automated patching or patch management products such as Ivanti, PatchMyPC, Adaptiva, etc.  5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.) All CAD users are affected when the latest patches are not available because IT Security forces updates on users at inconvenient times, or they don't deploy correctly.  Also engineering administrators do not have the bandwidth to develop patch deployments at the rate that patches are provided.  

Sketch Stability ImprovementsAcknowledged

1. Describe the ProblemThe stability of sketches should be improved.   I would like to use this sketch to create a series of tabs around my part.   I want to use the pattern table capability to place the tabs at specific angles.   However, I can't use pattern the feature because at specific angles the arch jumps acrost the part.   Which causes the feature to fail.(function() { var wrapper = document.getElementById('lia-vid-6368763508112w962h540r518'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})();(view in My Videos)2. Are you using a workaround?I will have a to make compromises to the sketch to get a consistent behavior. Or, maybe use the direct modeling capabilities.3. What is the use case for your organization?Doing modeling of parametric parts. This has been a problem in Creo for many versions going back to Pro/E 2001.4. What impact does this problem currently have on your organization?It discourages using the more advanced features of Creo. Reduces trust in the software. Causes another pain point with Creo and another reason the folks coming from Solid Works keep begging to change software.

Rename the Show option for "Components with explicit statuses" to accurately reflect its functionArchived

1. Describe the Problem When defining a simplified rep, the SHOW menu has the following options: Components with Explicit Statuses: HIDES components that do not have explicit statuses Active: SHOWS components that are Active Inactive: SHOWS components that are Inactive Envelopes: SHOWS envelopes The Hiding behavior of the Explicit Status setting is inconsistent with the name of the menu ("Show"), the tooltip on the setting ("Show components with explicit statuses"), and the other settings which show and do not hide, yet it is lumped in with them, even under a "Check All" option which everyone I've spoken with about it assumes will show everything due to it being in the Show menu.   There needs to be a Show All option, which does not have this hiding option selected. The Explicit hiding option needs to be reworded to tell the user it will hide things. Perhaps change the name of the menu to Filter to be consistent with every other application. 2. Are you using a workaround?N/A3. What is the use case for your organization?N/A4. What impact does this problem currently have on your organization?User confusion, unnecessary calls to tech support because things are "missing" after they clicked all the options in the Show menu.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 all the details required in the form.Thank you for your participation.