Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Need Auto Exploded functionality in Creo IllustrateAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Illustrate 9.0 -11.1 2. What is the problem?Creating exploded views in Creo Illustrate is currently a manual and time-consuming process. Although it's referred to as "Smart Explode," a lot of manual effort is still required to resolve interferences between exploded items.We need to carefully select parts so that those exploding in the X direction are handled first, followed by those in the Y and Z directions. If we use the coupling option, all items are grouped together and moved in a single direction, leaving no control over interferences between parts.This step alone accounts for roughly 60% of the total effort involved in producing technical illustrations. For every assembly, illustrators must manually drag and align parts, which not only consumes time but also causes delays.This manual process:Increases illustration costs and time.Limits scalability as products grow in complexity.Wastes expert time on repetitive tasks.Introducing an logic driven auto-explode feature would drastically reduce manual effort, accelerate the creation process, and enhance consistency and overall quality in technical documentation. 3. Are you using a workaround? If yes, please describe it.Recently i come across a 3D illustration tool Lattice 3D Studio, The Explode view Capability is outstanding. Here is the Demo video https://www.youtube.com/watch?v=6c9TuyjFAXQ&t=2s4. 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 create thousands of service and operator manuals every month, many of which include exploded views. In the attached demo video, you can see that based on the selected disassembly nodes, everything is exploded around the selected item without interference, following internal logic. After creating the auto-explode view, it’s also possible to change the direction of individual items as needed.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)It is impacting the business heavily since 60% of resources are spent on Exploded views.

ENABLE MBD TABLE DISPLAY IN CREO VIEWCurrent Functionality

What product and version are you running?Creo View 11 and Creo Parametric 11 2. What is the problem? Creo Parametric 11 supports the creation of simple tables in Model-Based Definition (MBD), but currently Creo View does not support the display of these tables in a pvz file published by Creo Parametric.   See article CS420247:  “Unable to view Table Annotation features in .pvz file when viewing the created pvz in Creo View” https://www.ptc.com/en/support/article/CS420247 3. Are you using a workaround? If yes, please describe it.No.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. This improvement would benefit all companies that include information in 3D tables (MBD Tables), as they will be able to display it via Creo View.Take this example of a table in Creo Parametric 11:   A user without Creo Parametric should be able to access the information in Creo View, just like with 3D dimensions and other 3D annotations. The model would become much more understandable. 5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)MBD tables offer significant advantages in information transfer, but without being viewable in Creo View they are of limited use for communication outside the technical department.

Allow setting accuracy in a motion skeletonUnder Consideration

Please include detailed documentation such as screenshots, images or video. 1. What version of the software are you running?CREO 10.0.0.02. What is the problem?Setting accuracy is not allowed for Motion Skeletons ,ASM files3. Are you using a workaround? If yes, please describe it.None, Accuracy value is inherited from the template (I hope, but I'm not sure because I don't know how to verify 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. We are interested in introducing the use of motion skeleton; for instance we 'd like to use mechanism motion skeleton to: Perform a cam synthesisMake a PID controller setupRead external data into a servomotor composed by numbers with many figures (and you need the motion skel reads them)…5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)If you change only mechanism accuracy (possible for Motion Skeletons) without changing model and assembly accuracy, often it leads to errors.Skeletons, speaking in general, should be used in complex assemblies to achieve a most robust model.If you are forced to use Motion skeletons only for simple mechanism, then in my opinion they’re completely useless:Finally, I don’t understand the reason for such a limitation (it’s an assembly file !).

Retain Long Imported Part Names using ParametersAcknowledged

1. Describe the Problem It is a well known problem about the 31 character limit for Creo file names. When importing files with assembly and part names lager than 31 characters, the names are truncated to the first 31 characters. However, naming conventions for longer file names near 80 characters often include more specific details like part number or hand within the truncated text. This makes identification of parts by name impossible. This is particularly problematic in large assembly imports.   This feature suggestion should not involve resizing of any data types in Creo. What is needed is the option to automatically create a string parameter like "Imported Name" for each part/assembly name in an import file that captures the name up to the string parameter limit (80 char) or beyond. Then, showing the parameter column resolves the identification issue at least up to 80 characters. This could even be extended to place additional characters in another parameter like "Imported_Name_cont_1 if necessary to retain all characters to whatever maximum limit is desired.      2. Are you using a workaround?Manual re-naming of parts based on the 3d appearance vs. the engineering BOM views and product knowledge.3. What is the use case for your organization?We import medium sized assemblies from CATIA in either .catx or Step files for use in Creo. The name information is lost and must be recreated manually.4. What impact does this problem currently have on your organization?1. Lost time of several hundred hours per year. 2. Risks to end product quality if parts are wrongly identified. 3. Lost traceability creating risk of audit findings at PTC customers. How does just truncating this critical information pass PTC internal audits?