Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Enable license logging with date/timestamp for each lineAcknowledged

1. Describe the ProblemEvery customer should be able to activate full logging by command line option in any version of FLEXLM.  In the standard ptc_d log files you have log entries that say:      :20:03 (ptc_d) (@ptc_d-SLOG@) Start date: Tue Jan 28 2025 17:20:03 W. Europe Standard Timeand then you have SEVERAL DAYS  of log entries that only state:      16:40:06 (ptc_d) OUT: "Creo_EngineerIII" USER123@WORKSTATION324This makes it impossible to pin the exact checkout and checkin dates/times per user without using a tool.There was however a version of FLEXLM where full logging was activated (Text from the PTC Case):"11.19.6.0 was build with full debug mode because, from 11.19.1 till 11.19.6.0 , there was a crash issue when someone want to borrow as well as license gets TIMEED OUT. To figure out the root cause we enabled full logging mode. But after the crash issue is resolved and server is stable, we changed debug level. As log will will grow faster and can consume disk space we have reduced the log level. But even thought, there was no version , where date was part of each log line. We asked this to flexera but we didn't get a positive response."2. Are you using a workaround?3rd party License Monitoring - but this is only taking snapshots - so sometimes users are being missed.3. What is the use case for your organization?Keep track EXACTLY of how many licenses are used throughout the day/month/year.4. What impact does this problem currently have on your organization?Sometimes users are missed as having used a certain license and this is bad if you want to have an ACCURATE overview.

Possibility to adjust boundaries of drawing view depends only on visible geometryAcknowledged

1. Describe the ProblemIf we use in part or assembly for example copy geometry, skeleton model or multibody technigues and in final drawings this objects are hidden they are still affect the boundaries and size of the drawing view. This make comlicated work and drawings are often unclear. Possible solution:1) Allow the user to manually adjust boundaries of drawing view2) By default or configuration option, have the ability to adjust the view boundary size according to the visible solid geometry ( do not take hidden geometry )2. Are you using a workaround?Only workarounds are using Partial View or Simplified Representations. But if we use Partial view then we don´t have possibility to use others settings of views ( Broken View, Half View... )3. What is the use case for your organization?We frequently create drawing views that display only a portion of the overall model, such as detailed cutouts of complex assemblies or views with filtered components. Currently, we have to manually adjust the drawing view boundaries, which is time-consuming and can lead to inaccuracies. The proposed feature – the ability to automatically set drawing view boundaries based on the visible geometry – would significantly speed up the drawing creation process, improve readability, and reduce the need for manual adjustments. This would result in higher productivity and more efficient use of Creo Parametric when preparing drawing documentation.4. What impact does this problem currently have on your organization?Currently, manually adjusting drawing view boundaries slows down the drawing documentation process, especially for complex assemblies and detailed views. This approach not only increases the time required for engineers but also raises the risk of errors, such as unintentionally cropping important parts of the model or needing repeated adjustments when design changes occur. Implementing this feature would eliminate these manual steps, leading to a more efficient workflow, reduced error rate, and overall acceleration of the drawing documentation process.

DEX - Model HistoryAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo 9.0.7.0 - Using DEX (Design Exploration Xtension)2. What is the problem?A limitation of DEX is that it applies to the session, not the parts / assembly. I see that as an advantage for most things (DEX is designed as an ad-hoc, trial-and-error environment to explore design options as you guys describe it - and having everthing save within the .tmu session is great at doing that). But a downside is that you may commit to a design option and then work away on your parts and assemblies for weeks after that, only to realize that one of your other concepts from DEX is now of interest. I can open an old .tmu no problem, but it is a snapshot of what the model looked like back then (hasn't accounted for the weeks of work I've done post-DEX. If there was a way to open a newer version of a model and an old DEX session and tell it to try and reapply those features to your new model, that would be very cool. Obviously references may break, but something similar to the re-referencing tools when copying features between different .prt files would be a great solution to this I'd imagine.3. Are you using a workaround? If yes, please describe it.Nope - not possible today.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 do a lot of early-stage cncept development work for consumer electronics products.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Tedious workarounds, making copies of files, suppressing groups, and heavy / slow model trees as a result of that, vs. being able to extract more value out of DEX to avoid these things.

Enable Hatch Editing on 3D (Zone) SectionsAcknowledged

** Duplicate of (https://community.ptc.com/t5/Creo-Parametric-Ideas/Enable-Hatch-Editing-on-3D-Zone-Sections/idi-p/452695) as that thread was archived, despite being the only sensible ""solution"" (in the biggest air-quotes I can muster) on the following support article about the lack of functionality in which PTC believe including the most basic of features not part of their job (https://www.ptc.com/en/support/article/CS203613) Maybe this time they will actually consider fixing this ropey mess of a program. 1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.Sustainable Electricity and Power distribution2. What version of Creo Parametric are you currently running?8.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.Read title. Changing cross hatching is a basic feature when working with a section view. When employing a zone section (a requirement given the lack of functionality offered by the Offset Section feature (https://community.ptc.com/t5/3D-Part-Assembly-Design/Offset-section-leads-to-hollow-parts-BUG/td-p/815031)) there is no option to alter the cross hatching display, leading to parts being too densely or sparsely populated with hatches.4. What is the use case for your organization?Not suppling important customers with embarrassing poorly formatted drawings, then having to explain that it's down to our modelling software and it's inability to show a sectional view properly.5. What business value would your suggestion represent for your organization?Not losing out on important and valuable work contracts due to poor drawing quality beyond our control.

Officially support standards C++17 and C++20 for Object TOOLKIT C++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? According to the PTC article CS323813, the C++ standards C++17 and C++20 are currently not officially supported, only C++14. Here's a list of some C++ features that can't be used today:   C++17 Features Structured Bindings: Allows the decomposition of objects into their components, simplifying variable declarations. std::optional: For representing optional values, similar to "Nullable" types in other languages. Inline Variables: Solve the issue of multiple definitions across different translation units. std::variant and std::any: Type-safe unions for storing values of different types. If and Switch with Initializers: Enables the declaration of a variable within the condition of if and switch statements. Fold Expressions: For more elegant handling of variadic templates. Filesystem Library: Introduction of a standardized API for working with file systems. C++20 Features Concepts: Provide a way to express template requirements more clearly and understandably. Ranges Library: Extends the capabilities of STL algorithms by introducing range operations. Coroutines: Support for coroutines, enabling more efficient and simpler handling of asynchronous code. Modules: Reduce the need for headers and preprocessor directives, improve compile times and code modularity. Lambdas with Default Constructor: Allow the use of capture-less lambdas as regular functions. Constant Evaluation for Certain Functions: Allows more code to be executed at compile time, which can improve runtime efficiency. std::format: A safer and more flexible alternative to printf for string formatting.   3. Are you using a workaround? If yes, please describe it. The restriction to C++ features of a maximum of C++14 and the use of various 3rd party libraries.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.   The new features introduced in C++17 and C++20 bring several significant advantages to C++ development, enhancing both the language's capabilities and the developer experience. Here's an overview of the major advantages:   Advantages of C++17 Features Simpler and More Readable Code: Structured bindings and if/switch with initializers contribute to more concise and readable code. Improved Type Safety and Expressiveness: std::optional, std::variant, and std::any enhance type safety and expressiveness, allowing for more robust and clear code. Better Resource Management: Features like std::optional reduce the need for raw pointers, thereby improving memory safety. Enhanced Compile-Time Processing: Inline variables and constexpr if improve template metaprogramming and reduce compile-time dependencies. Standardized Filesystem Handling: The filesystem library standardizes file operations, making code more portable and reducing reliance on third-party libraries. Modern Template Features: Fold expressions and other template improvements simplify complex template programming. Advantages of C++20 Features More Efficient and Readable Templates: Concepts significantly improve template readability and debugging, making templates easier to use and understand. Enhanced Range-Based Operations: The Ranges library provides more powerful and intuitive ways to process sequences of data. Support for Asynchronous Programming: Coroutines facilitate asynchronous and concurrent programming, allowing for more efficient handling of tasks that involve waiting or polling. Improved Compilation and Module Management: Modules enhance compilation speed and improve code organization, reducing header dependencies and compile times. Advanced Lambda Expressions: Extended lambda capabilities, including lambdas with default constructors, allow for more flexible and powerful functional programming patterns. More Runtime Efficiency: Constant evaluation features allow for more computations to be moved to compile time, potentially improving runtime performance. Safe and Flexible String Formatting: std::format provides a type-safe and more flexible alternative to traditional C-style string formatting functions. Overall, these advancements in C++17 and C++20 contribute to making C++ a more modern, efficient, and user-friendly programming language. They address many of the historical pain points in C++ programming, such as complex template syntax, inefficient string handling, and cumbersome file operations, thereby enhancing both the performance of C++ applications and the productivity of developers.   5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.) About a dozen people who use the TOOLKIT interface at our company are affected.

Need a mechanism in Creo to 'update' a custom corporate symbol on a drawing to the latest iterationAcknowledged

1. Describe the Problem Reference: Ticket: C17727367  Articles: CS439490 and CS36275   There is no method within Creo to simply select a custom symbol and have it 'update' to the latest standard. The issue is that once a symbol is loaded into a drawing, it stores that symbol internally, without a link to allow it to be updated. Once an update to a company standard symbol is deployed, there isn't an easy solution to updating the current ones, or any drawing created from a save-as. 2. Are you using a workaround?The two articles list a very convoluted workaround. The watered down version, is that the admin needs to make sure the .# extension of the updated symbol is higher than the old one. The user then needs to manually browse to the symbols folder and 'add' the symbol to the drawing. At that point, it will prompt the user to update the other symbols and then the user can select yes and delete the new symbol. This even includes custom bom balloon symbols. The good news is that the code to update symbols is already there. PTC just needs to copy if from the 'add symbol' command, to a new command for 'update symbol'.3. What is the use case for your organization?The admin updates a standard custom symbol or BOM balloon. Current drawings and those which will be created via a saved-as could then be updated, as needed.4. What impact does this problem currently have on your organization?Some new drawings will lack the functionality of fixes that was built into the updated custom symbols, creating inconsistencies and miscommunication.

Dual dimensions (or multiple dimensions) in Measure toolAcknowledged

1. Describe the ProblemI would like the Measurement tool to be able to display multiple units at the same time. For me this almost exclusively applies to IN & mm, but some people like to work in IN & FT, or IN & CM, etc. As shown in the picture below, I suggest augmenting the current Units option with check marks to generate a list of measurements. In my case, that would be 2 measurements, but it could be more depending on the use case. Being able to specify precision (# of decimal places) is also useful for reducing visual clutter. Suggested Measure Tool Improvement2. Are you using a workaround?Currently I take a measurement, then click Options, then click Units, then scroll & click on mm, then click Okay. This isn't a workaround, but it is 4 extra clicks and some visual searching that has to be done multiple times in a given part. Depending on the number of metric parts in the assembly, sometimes I change the units of the assembly to metric, work on those parts, then change the units back to inches. Neither of these are good workflows.3. What is the use case for your organization?We work frequently with COTS parts within a custom enclosure. This necessitates using Imperial and Metric measurements within an assembly. Checking measurements from multiple files means doing a lot of switching back & forth. This happens on nearly every assembly we make.4. What impact does this problem currently have on your organization?We have almost 40,000 employees, and probably 5,000 of them are CREO users. Saving 10 seconds per model thousands of times per day is significant savings.