Skip to main content

Filtrer par statut de l'idée

Filtrer par produit

6851 Idées

Option to set the character to be used as decimal separator (point or comma)Acknowledged

1. What product and version are you running?   We are currently working with Creo Parametric 7.0.12.0. 2. What is the problem?   When working with Creo Parametric, (decimal) numbers are entered very frequently.Most users use the numeric keypad on the keyboard for this.This has a key for the decimal separator, but since according to our regional settings (which is German, as I am in Austria) the decimal separator is a comma and not a point, the numeric keypad key is of course used to type in a comma.And since Creo does not accept the comma as a decimal separator, it has to be corrected by a point.3. Are you using a workaround? If yes, please describe it.   The simplest workaround is to use the comma key next to the letters instead of the key on the numeric keypad. However, this requires you to reach over from the numeric keypad and you are forced to look at the keyboard briefly to catch the right key.Another workaround is to change the region scheme in the operating system settings to one where the point and comma are reversed. However, this also changes other keys and, for example, special characters are then suddenly no longer where you would expect them to be.This leaves the use of special additional software, which always outputs the point when the decimal separator on the numeric keypad is pressed. But then you only need additional software for this tiny requirement. In addition, although it then works in Creo, it no longer works in almost any other software because it expects the comma as a separator again according to the region settings.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.   From our point of view, the best solution would be to be able to set in Creo Parametric which character should be used as the decimal separator.Alternatively, Creo Parametric could read the region settings automatically so that nothing would have to be changed explicitly.And best of all would be a config.pro setting that combines the two previous suggestions: E.g. named decimal_separator with the three possible values auto, point and comma. Logically, auto should then be the default value and use the decimal separator according to the region settings.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)The number of users affected in my company is about 300.But if you look at the worldwide conventions in the corresponding Wikipedia article, you can assume that a massively large number of PTC customers would benefit from this enhancement!

Datum Axis and Datum Reference Frame display behavior improvement.Acknowledged

1. Describe the ProblemIn a model based environment, the datum displays behavior is different than what I expect.    Its really easy to get in a condition where the user is like "WHY CAN'T I FIND THE DATUM I WANT.....oh, I'm in an annotation state instead Default All.   AAhhhh,...  Why don't we use Solid Works?!!" Desired behavior1) When Datum is added to Annotation State2) Datum gets the same color applied by default as is used for annotations.3) If datum display is off, then annotation instance of datum is toggled on and off by Annotation Display Toggle.4) If annotation display is off, then Datum Toggle shows all datums of that type which are in a visible layer.  (If the datum is in the annotation state it would toggle on and off with the annotation color, datums not in the state we retain default color) •Datum Reference Frames a sometimes toggled by the CSY display, they have more issues (Case Link)  For extra credit, the Default All state should be called "Modeling Mode" or something to separate it from the annotation modes. (function() { var wrapper = document.getElementById('lia-vid-6390990396112w992h540r769'); 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?If I want this behavior now, I would have to do a bunch of special layer over-rides for each MBD state that I want to force the axes to display.3. What is the use case for your organization?User acceptance of MBD is challenged when some features of the MBD design introduce unusual behaviors.4. What impact does this problem currently have on your organization?User acceptance and model consistency

AI‑Driven Conversion of MBD & GD&T Generated Dimensions to Tolerance Center / Min / Max in CreoAcknowledged

1. Describe the ProblemProblem StatementIn Creo, the conversion of geometry to tolerance center, minimum or maximum works reliably as long as driving dimensions are used. Driving dimensions do not automatically reference the resulting surfaces by default.However, with the increasing adoption of Model‑Based Definition (MBD) and the GD&T Advisor, a growing number of dimensions are generated (driven) dimensions.These generated dimensions are essential for downstream manufacturing, inspection and digital continuity, but currently cannot drive geometry. As a result:Geometry adjustments based on toleranced MBD dimensions require manual interpretation and reworkConsistency between design intent, tolerances and geometry state is harder to maintainAutomated workflows for manufacturing and validation are limitedWhy This Becomes a Growing IssueIn modern CAD workflows:Generated MBD dimensions often do not have a direct 1‑to‑1 relationship to individual sketch or feature dimensionsA single generated dimension may depend on multiple features, parameters or constraintsDesigners must manually identify and update the relevant driving dimensions to achieve center / min / max geometry statesThis becomes increasingly complex and time‑consuming as models grow and MBD adoption increases.Proposed Idea: AI‑Supported Geometry ConversionI propose an AI‑powered capability in Creo that enables:Conversion of geometry to tolerance center, minimum or maximumBased on both driving and generated (MBD/GD&T) dimensionsPossibility to automatically reference driving dimensions to created surfaces semantically.By intelligently identifying and updating the relevant underlying sketch and feature dimensionsInstead of relying on direct dimension mapping, AI could:Analyze geometric intent, feature relationships and constraintsUnderstand how generated dimensions are derived from the modelDetermine which driving dimensions must be adjusted—and how—to achieve the target geometry stateScopeThis capability would be required and highly valuable for:Normal geometryCopy Geometry (Copy‑Geo)MBD‑driven design, manufacturing, and inspection workflows 2. Are you using a workaround?At the moment, we are still primarily working with driving dimensions and are in the process of introducing MBD step by step. However, without an automated way to derive tolerance‑center / min / max geometry from generated MBD dimensions, the expected benefits of MBD are significantly reduced. The manual effort required to analyze the model, identify the relevant driving dimensions, and adjust them in order to provide a tolerance‑center model counteracts many of the efficiency gains we expect from MBD. As a result, there is a real risk that: MBD adoption increases documentation quality, but adds manual effort instead of reducing it Designers hesitate to fully rely on generated dimensions The transition from dimension‑driven models to MBD‑driven workflows is slowed down This is why an AI‑supported, intent‑aware solution becomes critical—not only for advanced MBD usage, but already during the transition phase from traditional dimension‑driven modeling to full MBD.3. What is the use case for your organization?The top use cases focus on enabling NC programming, fully realizing MBD as the single source of truth, improving design flexibility, supporting copy‑geometry workflows, and reducing risk during tolerance changes.1. Tolerance‑Center Geometry for NC Programming (Creo NC) NC programming requires nominal (tolerance‑center) geometry to create stable, reusable toolpaths. With MBD and GD&T‑generated dimensions, geometry can no longer be recalculated automatically, forcing manual rework. An automated, MBD‑driven conversion would significantly reduce effort, errors, and lead time in NC programming.2. Enabling MBD as the True Single Source of Truth MBD dimensions define functional and manufacturing intent, but today they cannot drive geometry. This creates a disconnect between tolerance definition and geometric realization. Automatically recalculating geometry from generated MBD dimensions would close this gap and fully enable MBD‑first workflows.3. Increased Design Flexibility and Model Robustness Designers currently need to preserve driving dimensions solely to support downstream geometry recalculation. This limits modeling freedom and leads to artificial or redundant dimensions. An AI‑supported solution would allow designers to model for design intent, while tolerances defined via MBD control geometry when needed.4. Copy Geometry (Copy‑Geo) and Downstream Model Consistency Copy‑Geometry workflows are widely used for tooling, fixtures, and downstream consumption. Since copy models do not retain access to original driving dimensions, geometry updates based on MBD tolerances are not possible today. Automatically deriving tolerance‑based geometry ensures consistent and reliable downstream models.5. Faster and Safer Reaction to Tolerance Changes Tolerance changes are common late in the development process. Today, these changes require manual analysis to identify affected driving dimensions, increasing risk and effort. An automated conversion allows geometry to be recalculated directly from updated MBD data, supporting robust change management.4. What impact does this problem currently have on your organization?The current limitation has a direct and measurable impact on our workflows, especially during the transition from dimension‑driven modeling to Model‑Based Definition (MBD).1. Increased Manual Effort Because generated MBD / GD&T dimensions cannot drive geometry, tolerance‑center, minimum, or maximum models must be created manually by identifying and adjusting the relevant driving dimensions. This requires detailed model knowledge and adds significant effort for design and NC programming teams. 2. Reduced Expected Benefits from MBD One of the main expectations of MBD is to reduce manual interpretation and downstream rework. Currently, the need to manually recreate geometry states based on MBD tolerances counteracts these benefits and reduces the overall ROI of introducing MBD.3. Slower Adoption of MBD Due to the additional effort required: Designers tend to keep traditional driving dimensions MBD is introduced cautiously rather than used as the primary method This slows down the transition to MBD‑first workflows.4. Impact on NC Programming (Creo NC) NC programming requires tolerance‑center geometry as a stable basis. Without automated recalculation from MBD data, NC‑relevant models must be prepared manually, increasing lead time and risk of inconsistency between design and manufacturing.5. Higher Dependency on Individual Expertise The correct interpretation of MBD dimensions and their translation back into driving dimensions depends heavily on individual experience and model knowledge, making the process harder to standardize and scale.

Fix 2d hole note behavior to comply with ASME Y14.5Acknowledged

1. Describe the ProblemWhen dimensioning a 2d drawing, notes for standard holes do not reference the center axis of the hole as required by ASME Y14.5.   To comply with ASME Y14.5, the note should behave as the dimension of a simple hole does (the note should rotate around the center axis of the hole, not around the point where the arrow attaches to the hole edge). I know I am not the first to ask for this, it can't be that hard to fix.  PLEASE PTC, make this software usable for those of us who have to comply with broadly used engineering standards such as ASME Y14.5.(function() { var wrapper = document.getElementById('lia-vid-6385584034112w1002h540r264'); 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)(function() { var wrapper = document.getElementById('lia-vid-6385584813112w996h540r920'); 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?Yes, I have to go to the 3d model, edit the attachment point of the note to the hole edge, then I can go back to 2d and the note will rotate around the hole axis. BUT, it only will rotate around halfway (only around the half of the circle that it is attached to. AND, if the hole size changes, or the thread depth changes (ie, from partial thread depth to full thread depth), the note resets back to the incorrect behavior and I have to go back to 3d, and repeat the whole process. There really shouldn't be a need for me to have a complex workaround to have software aimed at professional designers & engineers comply with the standards that are almost universally used across industry.3. What is the use case for your organization?Our drawings need to comply with ASME Y14.5, as is the case with a huge number of your customers. This is not an issue that is unique to our organization.4. What impact does this problem currently have on your organization?All of our designers, drafters, and engineers are wasting their time fixing the note behavior for every single hole, on every single drawing, every single time the drawing is created or the hole changes. This is also universal across all of your customers. It can't be that expensive for you to fix this problem.

Possibility to display tooltips on touchscreen devices using finger gesturesAcknowledged

1. What product and version are you running?   Creo View 12.1.0.0 2. What is the problem?   When you move the mouse pointer over a component in Creo View, a tooltip is displayed.By default, this only contains the component name, but it's possible to customize the tooltips.Creo View also supports use on touchscreen devices.But on these devices there's no finger gesture to display the tooltips.   Also see following Help Center links in this regards: About Customizing Tooltips Working with Touchscreens3. Are you using a workaround? If yes, please describe it.   The possible workarounds are to connect a mouse to the touchscreen device or to switch to a normal PC with a monitor, mouse and keyboard.However, both workarounds are inconvenient if you've a touchscreen device as your primary device.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.   We use tooltips very extensively for standard parts, for example, to display various parameters.For screws/bolts, these are parameters such as head shape, thread diameter, width across flats, etc.This helps workers in the assembly departments enormously to identify the required components in order to retrieve them from the warehouse and use the correct assembly tool.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)The amount of touchscreen devices is increasing rapidly in assembly departments to reduce reliance on printed design drawings.In addition, the three-dimensional view of Creo View visualizations is much easier to understand than the views on drawings.Of our current 1500 or so employees in the assembly departments, around 20% have a touchscreen device (so there are around 30 devices).As I said, the trend is rising and gesture control's therefore becoming increasingly important.

Import .emn and .emp files into a single part file and import the board and components as featuresAcknowledged

1. Describe the ProblemWhen .emn and .emp files are imported while connected to the Windchill server, incorrect components with the same filenames as imported components are pulled into the imported ECAD assembly. Being able to import the .emn and .emp files into a single part file with individual solid features for the board and components would be the perfect way to circumvent this issue. The ECAD parameters for each component can be added to each feature.2. Are you using a workaround?The workaround is to import the .emn and .emp files while disconnected from the Windchill server. I made a program using the Creo Object Toolkit C++ that runs a macro to perform the .emn and .emp import and then copies the geometry of the board and components into a single part file. This can take a while for large assemblies since my solution requires two regenerations for each copy geometry feature. One regeneration is required to produce each copied geometry feature and another regeneration is required to modify the feature and break the link between the copied geometry and the part file that the geometry was copied from.3. What is the use case for your organization?Reviewing the final layout of a circuit board before it goes into production and making sure it works with overall mechanical assembly.4. What impact does this problem currently have on your organization?Additional time and effort is required to review circuit board layouts.