Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Retain feature settings for use within same model or session.Current Functionality

1. Describe the ProblemWe spend a lot of time selecting the same settings within the Creo due to the fact they revert back to the default when the feature is closed.  In most, if not all cases the default is not used which forces us to re-pick all settings for the next use of that feature. If all settings, you modify were to be retained until you change them or at the least until the file is closed, we would be able to reuse that feature as intended.  This would eliminate many clicks throughout the day. This is a common approach with other software and actually is sometimes the case within Creo (Round dimension is saved until changed).   One example would be the steps below to create a hole for an insert. Once the hole tool is closed these settings are reverted back to default. Often, we reuse the size or one close with most settings the same. 1. Select hole button,2. Select standard,3. Select countersink,4. Select hole type using hole template,5. Select screw size,6. Select depth,7. Select shape pulldown,8. Modify countersink angle,9. Modify drill tip angle,10. Modify thread depth. 2. Are you using a workaround?If I know there is an existing hole, I will often use copy and paste special. This helps but even then, I have to 1. pick hole, 2. select paste special, 3 de-select dependent, 4, Select OK, 5. constrain hole.  With paste special the de-selection of dependent would be another example of the setting not sticking. Also, if I use any other tool the paste special then grays out and I have to find the hole again and repeat the process to copy/paste. I know there are patterns and other ways to reduce the creation of new holes but there are a lot of instances where that is not feasible and retaining settings would save a lot of time modeling time.3. What is the use case for your organization?In discussion within my organization this enhancement would be used by all every day to reduce time spent setting up features.4. What impact does this problem currently have on your organization?All users that create features requiring setting changes are impacted. In a lot of cases this would reduce hours of work per week for everyone using Creo for part/assembly modeling.

Enhancing Creo Toolkit APIs to Support Drag and Drop Event Handling.Acknowledged

1. Describe the ProblemCreo Toolkit/Pro Toolkit does not provide APIs to capture the drag and drop event of Creo design files into the Creo Parametric session.Creo Toolkit currently does not expose APIs or event hooks that allow developers to monitor or intercept drag-and-drop activities in the UI.The lack of drag/drop event handling creates a gap for advanced customization, particularly in workflows requiring file tracking, validation, or dynamic behavior based on the dropped content.Article CS230497 confirms that Toolkit support for these events does not exist at this time.2. Are you using a workaround?No.3. What is the use case for your organization?The Creo Parametric CAD application currently offers built-in support for drag-and-drop functionality—allowing users to open design files directly by dragging them into the session’s view area. While this behavior is useful for end users, it presents a limitation for developers working with the Creo Toolkit who wish to implement custom logic tied to drag-and-drop events.4. What impact does this problem currently have on your organization?As part of a customization using the Creo Toolkit, I am looking for a Creo Toolkit API to intercept and handle the following aspects of drag-and-drop behavior within Creo Parametric: - capture the drag initiation: Detect when a file drag event begins and which file is being moved. - identify the target location: the target location can be model tree or view area where the file will be dropped. - Perform conditional logic: Based on file type or context, allow or restrict drops, trigger automated actions. - to perform specific validations: run validations before the file is opened in Creo.

Creo View MCAD to 'Compare' Models that include BodiesAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We design and manufacture high-end electronics. I am the CAD Manager / PTC SME. Stakeholders for this idea include our Creo Parametric, Windchill and Creo View user community; a big part of our organization. 2. What product and version are you currently running?Creo View 9.1 with Creo Parametric 8.0.6.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.Refer to case 16669999   For those who are unaware, there is additional functionality, on top of Creo View Lite, that requires extra licenses. One of this functionality we feel bring a lot of value is the 'COMPARE' tool within the Creo View MCAD license. It allows for an easy way to view changes between drawings, parts and assemblies.    However, it has come to our attention that Creo View 9.1 (and under) can't compare models that include bodies from Creo Parametric 7. This caught us off guard, since Creo View should support new functionality with Creo Parametric. Creo View 7 should support Creo Parametric 7, Creo View 8 should support Creo Parametric 8... and so on. Here, we have Creo View 9.1 (just released) still not supporting functionality with Creo Parametric 7!   It gets even worse. If we have 2 versions of a product, and we would like to see what changed, the comparison won't work as long as 1 part, inside the product, has more than one body. This can be even a resistor! Furthermore, it still won't work if you don't ask for any geometry or mass data analysis. All we want to know is what got added, removed or moved. We don't care about bodies!   We now have two options moving forward: 1 - Not to renew these licenses and explain to leadership and our sales rep why this amazing tool no longer works with 3 year old files 2 - Go to the PLM team and convince them to change their recipe settings to publish for Creo View 6.1! Then, they need to republish ALL visualizations from the last 3 years!   I'm not liking any of those 2 options. If PTC product management could commit to a Creo View 10 release, then we could most likely hold out; since most 'Comparisons' happen at the part or drawing level; not necessarily at the product level.     4. What is the use case for your organization?We have use-cases where bodies are being used (although rarely) and now we loose the main functionality within Creo View MCAD that we bought it for. We can't go back as we have data (especially library data) already within Windchill that includes bodies.5. What business value would your suggestion represent for your organization?I consider this a 'regression'. Therefore, if this doesn't get 'fixed', we would loose business value as we can no longer compare cad data from Windchill using Creo View. It would definitely cause concern during our renewal period whether these licenses should be renewed if Creo View can't even work with 3 year old Creo files.

New Structure Model Tree Search Filters for Creo View 10.1 need Included as PreferencesAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo View 11.1.0.0 2. What is the problem?There are no preferences for managing the new search filter functionality in Creo View.  In the image below, Bodies and Parts are checked by default when Creo View is launched.  I want this same functionality with the "Columns" options.  I'm sure others will want stickyness to these settings with the newly developed Search Model Tree function.  Through PTC Case 17886356, we identified that it is not possible to set it.    Note: I also wasted 4 hours trying to apply this to the user_prefs.xml file in Creo View because almost all settings like this are sticky in Creo View already. You resize the screen and close Creo View and this gets set in the user_prefs.xml file!  I'm sure other admins will be surprised to see that these setting are not capable of being set.3. Are you using a workaround? If yes, please describe it.The user must MANUALLY click the applicable box (in our case it is Columns) to attain functionality on every launch.  We want to make this default as we put a lot of information in the feature name column.  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. I manage a server preference file for Creo View users, so they get a "master model" user interface with a ribbon and settings already applied.  This setting to include columns in the search would be very valuable for us as we put a lot of good searchable information in the feature name attribute(column).  I want to have the columns always checked to provide an improved search for users working in our master models in Creo View.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)50 users looking at large master models in Creo View. Lost Productivity Use Case 1 - Manually clicking the box on every launch (2 clicks) - Assume 10 users every day for 250 working days in a year.  5000 unnecessary mouse clicks per year. Lost Productivity Use Case 2 - Not finding items in the large assembly structure because the column is not included in search.  User's have to know to go click the checkbox to find objects in the feature name column. There will be user's that get frustrated that items are not found.    

MDB Annotation Dimensions should stay a set distance from Edge/SurfaceAcknowledged

1. Describe the ProblemWe are interested in using Model Based Definition and putting our Annotations on our models for use in downstream processes in an effort to remove 2-D Drawings. We make use of Family tables on our parts as they parametrically grow/shrink in size by a set distance for each instance. When we place a dimension on our part to show the overall height or length of the part on the generic instance, the dimension is placed a distance from the edge that looks good, and works great in our combination state. In this case, our part is 4 Units High and 4 Units Wide. However, when we go to get the output for our next instance (in this case, a 2 Unit High by 4 Unit Wide option), the width dimension does not follow the edge distance (stays the same distance from the UCS it seems) and gets lost off the screen as the part shrinks.  So, if we adjust our generic part to be a 2x4 Unit size, and dimension off of that size.  Easy enough, right? BUT when we go back to the 4x4 Unit size, now the dimension ends up within the part as the part grows, and overlaps with Geometry. And now we go back and forth chasing this. Ideally, if we set a dimension a distance from an edge on the model, can that distance remain constant no matter the size of the part?  Is there a setting that can be applied for this?   Again, this is a huge disruptor for our organization to help sell the benefits of MBD and moving forward with the new practices. Please Vote this up!2. Are you using a workaround?None found other than accepting that dimensions will be accurate for only one size in the family.3. What is the use case for your organization?We want to make use of MBD/MBE in our organization, but this is a challenge in presentation to our downstream teams and doesn't help us sell the benefits of MDB. If they cannot read the dimensions that they need for inspection in our current processes, they will push back on moving forward with this. We are trying to replicate the same dimensioning schema that we would do in 2D drawings to help with the transition and not being able to do this on these part families is certainly causing some disruption.4. What impact does this problem currently have on your organization?Prevents us from fully moving to MBD into a drawing-less environment.

Multi Fidelity used in Illustration Source need to be managed based on LOD (High, Medium, ...)Acknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?The Creo Illustrate Version used 12.0 (but all before showing same obstacle)2. What is the problem?If Multi Fidelity Representations are used in Windchill, the POST Publish do not respect or differentiatebetween the LOD coming from Multi Fidelity User Pref.View about content from Multi FidelityLooking to the ILS consumers and assuming the ILS Versions are fed from different Multi Fidelity levels.An user already started with HIGH Fidelity and consumed attributes and used measurements he had this:Simple Sample: If the next iteration fed from (just for visual identification used Bounding Box - but reacts same way with e.g. LOW). The C3DI Figures loosing all their already annotated information's or measurements w/o any notice.Result: 3. Are you using a workaround? If yes, please describe it.Unacceptable Workaround to view and Analyse each and every ILS.Unacceptable because the ILS may contain thousands of objects. with different LOD visible for an user.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.Use case ... the streamlined Multi Fidelity Stream is not working at all and user are not able to select a previous ILS, eighter when opening Illustrate nor when the Update is managed by "Info" and update Source.Two ideas:  5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Users affected > 150Hours lost if analysis done by hand - 1 to 2 h per user a week min.more critical: User not realized that some content are in other fidelity and information got lost on documentation and if safety critical, information's gone impact to safety and other critical areas likely.

Summarize Creo Regen Warning or Error MessagesAcknowledged

1. Describe the Problem There's no quick way to summarize the Creo warning or error messages that occur during a regen. This problem gets multiplied when regenerating large assemblies which may generate 1000s of message lines during regeneration.   Current Problems: Regen warnings and errors stream by the message area quickly and are very easy to miss or ignore. Finding Message Log button or opening the Trail file in a text editor (ex: Notepad, Notepad++) to see all previous messages is not something that most new users know about. It's difficult to find where the last regen started on large assemblies in the Message Log or Trail file. There often are a TON duplicate warning or error messages. Many warning or error messages are hard to understand and often don't include the name(s) of the related model(s). Some messages that should be warnings or errors are not identified as such. Here's an example of the problems:   Possible Solution:   2. Are you using a workaround?Most users just ignore (or don't see) the regen warning or error messages. Those that attempt to review or resolve the regen warning or error messages with the Message Log or Trail file waste a lot of time.3. What is the use case for your organization?Quickly summarize warning or error message that occur during a regen that encourages users to resolve review or resolve. Creo the warning and error messages should be intuitive (ex: contain the related model name(s) when possible).4. What impact does this problem currently have on your organization?Assemblies can contain lots of models with warning or error messages. Wasted time trying to understand and summarize the warning or error messages.

Improve Update Behavior for UDFs in Creo – Enable Auto-Update in Referencing ModelsAcknowledged

1. What version of the software are you running?We are currently using Creo 7 and update to Creo 11 in August (Tests in Creo 11 have not shown any improvement)2. What is the problem?When a User Defined Feature (UDF) is updated (e.g. modified geometry, parameters, relations), the changes are not automatically reflected in models where the UDF has been previously inserted.As a result, designers must manually remove and reinsert the UDF in each affected part.This process:Is time-consuming.Breaks references in assemblies or downstream applications (e.g. CAM, metrology).Causes inconsistency in feature definitions across models.3. Are you using a workaround? If yes, please describe it.Yes, the only workaround is to manually delete and reinsert the UDF in every affected model.This approach:Requires manual redefinition of all references.Often leads to broken links in assemblies and drawings.Is error-prone and inefficient, especially when many parts use the same UDF.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 UDFs in a Model-Based Definition (MBD) process chain, especially for:Standardized port geometries.Thread features.Manufacturing annotations.These UDFs are used consistently across hundreds of parts. When one of these features is updated (e.g. tolerance change, geometry improvement), all instances should ideally update automatically.Our idea:Introduce a UDF update mechanism that detects if the UDF definition has changed.Give users the option to update UDFs in referencing models, preserving references where possible.Optionally, a notification or update prompt could be shown when opening the model.5. What impact does this problem currently have on your organization?Affects 20+ users in Design, CAM, QA, and Metrology.Leads to significant manual effort, especially for parts used in product families or variants.Causes data inconsistency when UDFs are not correctly updated across all parts.Risk of manufacturing or inspection errors due to outdated feature definitions.This limitation affects the overall efficiency of our digital process chain and slows down industrialization efforts.

Improved notification for Windchill Event Management errors inside Creo ParametricAcknowledged

1. Describe the ProblemToday when you receive a Windchill Event Management notification you get the red circle with the white line icon in the bottom of your Creo Parametric window. The error will show in the logging, but that only helps if it's the last error line. By clicking the icon you can get to the Event manager window, which then you have to often click the triangle or circle icons to figure out exactly why something failed.  The new-ish notification center allows for a small pop up notification along with controls to determine what items are flagged and which ones pop up. It would be beneficial if something similar happened for Windchill Events. The Notification Center server settings don't seem to capture things like upload failures which can be critical depending on your system setup.  Another option is to combine these two notifications into a single more powerful notification window allowing the small pop up banner windows with the options to fade or stay until dismissed based on the type of message. 2. Are you using a workaround?Workaround is to keep an eye out for the icon and in the running logs. Training to end users. I've also seen people make toolkit apps for critical errors like "unable to save" "upload failed" ... etc.3. What is the use case for your organization?Use case is system failing and users only know because of a relatively small icon that's easy to miss.4. What impact does this problem currently have on your organization?Users think their models are saved/uploaded and they are not, losing work.

ボルトの締結Acknowledged

2025.04.01PTC コミュニティへの提案   2025.02.10の貴方からのメールを受取り再度、技術的な疑問点についてチャレンジしたく本投稿をします 再投稿の内容については、機械系の規格関係の物であります具体的には、ねじの締結問題に絞りたいと思います。 例えば、日本国内では大型トラック・バスの車輪脱落事故は未だに解決されているとは云えない状況であると思います。 そこで、この状況を解決するためには、先ず、ホイールの取付方法と、ホイールを締結する方法の分析から始める必要があると考えた次第です。 但し、大型トラック・バスのホイール取付方式はISO規格に準拠しているので、今回はねじの締結問題だけに絞ります。 ねじの締結基準について Junkerの表と米谷レポートの概要説明 ・Junkerの表(ねじのゆるみ係数=締付け長さ/ボルト径:実験的に求めた表) 参考資料は添付資料1に示す ・米谷レポート(ねじ締結と摩擦係数の関係を実験的に求めたレポート) 参考資料は添付資料2に示す、 但し以下に概要説明のみ示す米谷実験とJunkerの表との統合一見、何の関係も見られない摩擦係数とJunkerの緩み係数L(ℓ/d )との関係とを同じグラフ上に表現する そこで、米谷の実験結果のグラフの横軸は軸力であり、縦軸は摩擦係数である一方、Junkerの表の(ℓf/d)はボルトサイズの標準化(ボルトサイズ無関係化)で(ℓf/d)値はボルトの伸び及び変異と同様である尚、米谷の実験結果は鉄鋼材料にも展開可能と仮定することでそこで、米谷の実験結果:図12の摩擦係数とJunkerの表との合体が可能になる 即ち、図12に新しく(ℓf/d)の横軸を設定することが可能になるこの手順で、摩擦係数とJunkersテーブルを統合するものですこの統合された図12のグラフから、Junkerの表の意味することが判明する 即ち、参照実験値から、論理的な繋がりが判明されていると思います。 3.私の最終目標:誰でもが安心して使用できるボルト締結マニュアルの作成 私が今迄、調査した範囲内ではJunkersの表が最も納得のいくものでした 但し、この表について、論理的な説明がないことを残念に思っていました そこで、論理的な私見を試みた訳ですが、更なるボルト締結の技術経験者は 多数存在するはずであり、その方々により、技術の承継が出来るようにして いただきたいと考えた次第です、何卒よろしくお願いします。 以上  

Allow column settings to be saved in Simplified Rep dialog boxAcknowledged

1. Describe the Problem I'm bringing this idea back to life!   Previous idea - https://community.ptc.com/t5/Creo-Parametric-Ideas/Allow-column-settings-to-be-saved-in-Simplified-Rep-dialog-box/idi-p/454844   The entire Creo Parametric interface has been updated to make settings sticky for the users with the tree.cfg being obsoleted.  The columns in the simplified rep ui have yet to be included.  Please vote for this idea to get the columns to be sticky after the user applies it.          2. Are you using a workaround?A mapkey can be created to enable the user to turn on the column but this works very flaky because the mapkey can only randomly select the row in the model tree columns. You can see in my picture above that if I run the mapkyey twice, it added "model size" which don't want! and the user has to remember to run this every time Creo is launched or use 6 button clicks to turn it on.3. What is the use case for your organization?Navigation of our large assemblies benefits from having feature name column included.(It's almost required). We need a way to have this column shown at all times whenever a user is navigating an assembly tree. We have configured Windchill structure tab to have this column along with Creo View in addition to the main window of Creo Parametric. I'm sure many customers have similar use case for columns to be included for navigation.4. What impact does this problem currently have on your organization?Difficult to navigate and find the correct assembly or part without the information in the column shown. It's 6 button clicks to make the user do this every time (or use mapkey everytime).