Recently active
These ideas stem from discussions with the PTC users whom have attended my Creo Cabling courses, my experience with competitive products and industry / customer requirements for electrical documentation. Users are looking for more common simulation, analysis / evaluation of there documented designs in Schematics and Cabling environment.1. Load based, 1.a User enters the Simulation interface, selects Load type of simulation to run, enters in design requirements, analysis runs and Entities in both Schematic highlight with tool tips describing event at those entities. 1.b Example: A surge goes through a system would highlight input voltage cables and Disconnector only if the surge is beyond the capacity of the disconnector or run through the rest of the circuit as designed.1.c Results of simulation can be Quick, saved or Features for use in Report and Tables2. Logic based,2.a User enters the Simulation interface, selects Logic type of simulation to run, Here the system e
Why can't Schematics give option on Import to ask scale to fit sheet? Instead it says too large for sheet (x by y size) and does nothing. This is not productive nor helpful. Since it already knows it is too large it should easily ask to scale to fit.
Please enhance the visualization of the Offset Sections in CreoView. Offset section is OK in Creo. It is KO in CreoView When displaying published Offset Section of an Assembly in CreoView (from the Sectioning > Preset pulldown), some Parts are sectioned with missing surfaces (not capped/closed). For example (If they are same size or larger than the holes, the issue occurs😞 The Planar Sections are OK in CreoView (even if components are in contact). The Offset Sections can be OK in CreoView if there isn't any contact between parts:
In Creo View add the ability to hide a datum coordinate system|datum point|datum axis|datum plane on an individual as-selected basis, like you can in Creo Parametric.
Today in cabling application there is a well known limitation once trying to flatten a cable which the wires route to pins ( multiple entry ports ) rather than single entry port. as a workaround ptc suggest to use "sub assemblies". this workaround work reasonably, however cause, again, issues down the line in the flattering of the cable. a solution is needed to overcome this limitation. possible solution can be ignoring the "real" length in the mfg files ( for display purpose ONLY ) in case trying to solve the issue from the "roots" either create "partial flattering" between the sub assemblies. this will improve product usability and save the user considerable time & effort
You modernized the graphtool in Creo 6.0 but there is not any probe option on Creo 6.0 and Creo 7.0 for read the clicked point values on Graph Yes, you have to place your pointer on a data point to Show x and y coordinates, this behavior already same in Creo 5.0 and other older versions, not a new enhancement. But In Creo 5.0 we can also see the clicked values bottom the graph window. It was a very useful thing to see that permanent value on there. My opinion it's not a good enhancement and PTC really sometimes disrupts what is available when trying to do new things, I hope it come again. We’will very happy to see it again on next Creo updates.
The ability to change which spool was used to create a wire after the wire was created. Currently, if you wish to change the spool, you have to delete the wire and create a new wire.
If it takes a long time to execute the round command, an icon that can cancel the processing (red x icon displayed at the lower right of the screen, see attached)Creo itself is canceled to cancel the process in the middle because it is displayed just before the end of the process.Since the removal command is displayed immediately after the processing starts, it is requested that the removal command be displayed immediately after the processing starts even when the round command is executed.
This is a product idea conversion of case 12775204. New API required to access intersection attachment of annotations (now it is possible for dimensions only).
According to the article CS245975, currently there is no API available to retrieve the name of the exploded state set in the drawing view. Please, add the corresponding functionality.
This is a product idea conversion of case 13296591. API extension required to query references of an ordinate baseline dimension, because there is no standard way to do that.
This is a product idea conversion of case 13620263. API extension required to create a custom symbol with variable text which is embedded to a note without user interaction.
1. Describe the ProblemCurrently and according to this article from the help center the symbols tab is a contextual ribbon. "The Symbol tab is a contextual ribbon tab" This means that the symbols tab only appears when an already existing symbol is selected or a new one will be created. Also the buttons such as "Gallery", "Symbol Palette" and "Browse Symbols" are deactivated until the symbols ribbon tab was activated. To activate the symbols ribbon tab it is mandatory to first select the "Symbol" button in the annotate ribbon tab. Now the users are able to select the gallery, the symbol palette or the browse symbols button. Idea/Requested feature: Add config.pro that enables the usage of the buttons "gallery", "symbol palette" and "browse symbols" without having to activate the contextual symbols ribbon before hand. This way it would be possible to select symbols faster and in a clearer way for the users. 2. Are you u
This is a product idea conversion of case 13631162. New API required to 'control characteristic' property of an annotation.
This is a product idea conversion of case 14731183. New API required to query default tolerance of dimensions.
This is a product idea conversion of case 14796412. API extension required to set 'flip direction' of a custom symbol attachment, so it will be possible to create such symbol without user interaction.
This is a product idea conversion of case 14957488. API extension required to query tolerance text of dimension which are instantiated inside a note.
This is a product idea conversion of case 14514272. New API required to query information about 'style state' of a combined state.
This is a product idea conversion of case 12974199. API extension required to change color of a drawing symbol to the default color of the drawing.
This is a product idea conversion of case 15255035. New API required to access drawing datum targets.
This is a product idea conversion of case 15285337. API extension required to set number of decimal places for a reference dimension.
Please, improve the functionality of ProDtlattachGet so it would return the proper information for currently unimplemented attachments. Judging by our experience, the most used are attachments to axes, cosmetic features and surface silhouettes.
This is a product idea conversion of case 13988445. legacy datums accessibility
This is a product idea conversion of case 13591995. New API required to determine if a geometric tolerance annotation is 'draft' or 'model', because there is no standard way to do that.
This is a product idea conversion of case 15319307. New API required to query positions of a drawing table cells and positions of notes inside the cells.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.