Recently active
Very confusing interface.Needs lot of learning and practice to use.Improvement needed is : It should be as simple as Excel or equivalent.1. What product and version are you running?I use Creo 9 and Creo 10 both. Have used all ProE and Creo versions starting from ProE WF-32. What is the problem?Creating and editing BOM Table takes lot of time. Being an old Pro user, we can manage it.But new Users does not like the old school method of adding and editing tables in Creo. New Users are more familiar with the new intuitive UI based and dropdown based editing rather than selecting options through Menu manager. They always compare it with Solidworks BOM table.Even Autocad now has improved the table creation. In Creo it is still the same older method and no improvement after this many years. BOM is something where engineers spend most of their time and it should be easy and fast, mostly for new beginners. Because Pro-users are not immortal 😁. They will be repla
1. Describe the ProblemShared models are the same models. So it is impossible to display them in different configurations. Also if 2 shared assemblies are contained in a main assembly, it is impossible to display them in different configurations. Like displayed below: The main assembly "Layout" contains 2 shared assemblies: "Bgr_1" and "Bgr_1.1". Both shared models have 2 configurations.Konfig_1_mitte:Konfig_2_oben_rechts:The main assembly cannot display "Bgr_1" and "Bgr_1.1" with different configurations. By merging or activating configurations both sub assemblies "Bgr_1" and "Bgr_1.1" can be displayed either in configuration "Konfig_1_mitte" or "Konfig_2_oben_rechts". The product idea is the possibiliy to merge different configurations of shared assemblies. So you are able to display the main assembly "Layout" like: 2. Are you using a workaround?There is no workaround.3. What is the use case for your organization?We develop configurable machines with automati
1. Description of the ProblemFor surface finish annotations, we are currently using the ProSurffinishValueGet() function to retrieve the associated property.However, we have observed that depending on the symbol type (e.g., ASME or ISO), the function does not return the expected values. Specifically, the roughness_height field is not available in some cases, and other fields such as surface_texture_requirement may contain only text values.Would it be possible to obtain the roughness height value (as a double) directly from surface finish annotations, such as those shown in the attached image?Additionally, we would prefer an API that is specifically designed to access this data, rather than extracting it from general symbol instance properties.Below is an example of a surface finish symbol where the function fails to return the expected value. 2. Are you using a workaround?No, we are not using any workaround at the moment.3. What is the use case for your organization?We need to val
1. Describe the Problem I would like the ability to change the light blue display color when selecting "Model" in the results display.There is no color scheme, so the color cannot be changed, making it difficult to see. I can change the other display colors, but I cannot change this color. 2. Are you using a workaround?Checking the shade box makes it a little easier to see, but I'd like to see it in wireframe as well.3. What is the use case for your organization?Use this when you want to check the deformation state.4. What impact does this problem currently have on your organization?Inconvenient for some users
1. Describe the ProblemWhile merging Harness Part2 with Harness Part1, the network from Harness Part2 to Harness Part1 moved, but the network continuity is not established.ASM 1 Harness Part 1ASM2 Harness Part2We expect to have network continuity while merging the Harness parts,2. Are you using a workaround?Currently, the network location is manually merged.3. What is the use case for your organization?Due to the diversity of products, we will create multiple harness assemblies and merge them later to calculate the overall length of the cable. In this case harness part should have Network continuity.4. What impact does this problem currently have on your organization?Our objective was to have a single harness assembly component for the vehicle product.
1. Describe the ProblemMerge harness, when connectors are in the Group, is not moved to the Active Hereness ASM.ASM 1 Harness Part 1ASM2 Harness Part2 Group (Connectors are in the Group)For example:- With the above Test DATA Structure, while merging the Harness Part2 with Harness Part1, the connectors from ASM2 Group are not moved to ASM1. 2. Are you using a workaround?Manually user must move all the connectors from AMS2 to ASM1 in this scenario.3. What is the use case for your organization?Due to the diversity of products, we will create multiple harness assemblies and merge them later to calculate the overall length of the cable.4. What impact does this problem currently have on your organization?Our objective was to have a single harness assembly component for the vehicle product.
Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?CREO 8.02. What is the problem?Our company is in the early phases of implementing MBD. One of the issues we are finding is that we can not change the "start part" template for already existing parts and assemblies, which means we have to create all the combination states (following MIL-STD-31000) for each existing part. For new parts, it should not be an issue if we change the company "start part" template to match the MBD "start part" template, but for older parts it is a pain to have to recreate all the combination states, unattached notes, title block, etc.... Can we please create a way to either:1. Copy a part (Save as) and give the option to change the start part. OR2. Be able to import combination states with all the notes, title blocks, etc.Both options seem better that recreating all the combination states from scratch for existing parts.3. Are you using a work
1. Describe the ProblemThe annotations are important for mold manufacturing team. And the parts are assembled using the coordinate system form the mold not the default. It is important to be possible unable the annotations option on the export step and an the same time, using a non-default coordinate system. 2. Are you using a workaround?Export to pvz and install creo view on the others departments to see the annotations and export also to step withot annotations to choose the coordinate system.3. What is the use case for your organization?Turn the non-default coordiante system when exporting the 3D file with note to step.4. What impact does this problem currently have on your organization?Do not export a second file and install the creo view to others departments. Only the step file is created and send to others departments.
Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Windchill pdmlink 12.0.2.7Workgroup Manager 13.0.0.1Creo Elements Direct Drafting 20.4.12. What is the problem?Creo View Adapter does not support the creation of TIFF from Creo Elements Direct DraftingThus we can´t create TIFF on a PTC Standard Worker.TIFF is currently used as the long term archive format.TIFF is also used to view and occasionally to print.3. Are you using a workaround? If yes, please describe it.To create TIFF we set up an on premise custom worker.From a strategic point of view we would like to focus on a SAAS solution.Operating a custom worker is only a fallback solution because TIFF is not supported by Creo view adapter.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.TIFF is necessary as it is used as the long term archive format.5. What impact does this probl
1. What version of the software are you running?Creo11 2. What is the problem? An offer to the CREO developers to add a search function to the menu of playing the toolpath by NCL-file (Manufacturing). This function is very useful for postprocessor developers and search for specific strings of NCL-file in the play menu. The problem is in the analysis of the postprocessing result.After postprocessing the ncl file and subsequent analysis of the *.lst file, it is sometimes extremely difficult to find the problematic CL record found in the *.lst file in the toolpath playback interface (graphical representation of the trajectory). For example: It is necessary to examine the CL-record in the *.lst-file after postprocessing2321>GOTO /-24.61144,20,-75.18996,0,1,0which is presented by the postprocessor as a sequence of blocks:2321 2322 2301 CC X12.632 Y108.216$2321 2322 2302 C X-24.611 Y75.19 DR-$ It is necessary to find this CL-record2321>GOTO /-24.61144,20,-75.18996,0,1,0when play
Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Illustrate 11.02. What is the problem?We need more information in the model tree, like description, material, treatment, etc...3. Are you using a workaround? If yes, please describe it.I need to customize General / Navigation with the "Use alternate part name" option to see attributes in the model tree. It's not easy to read.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.OOTB version shows file names, that in our environment are progressive numbers, not useful. We changed the "Use alternate part name" to add information but it's not very easy to use, for alignment, for some level without values, etc. In creo view instead there are "tree columns", I'ts very useful!We would like to see this feature also in Creo Illustrate.5. What impact does this problem currently h
Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo illustrate 11.1 Abillity to Save your illustrate company standard to Windchill as a *.pvsf file 2. What is the problem?When adding Windchill Attribute information to e.g. Callotuts, this information is not in your ADMINtool. So you will have to use Import. The problem is that you must delete the current standard, from WIndchill (!!), import the updated standard from the latest c3di file and save it back to Windchill. This will start a comple te new Version (A.1) instead of promoting to a new itteration or Version! 3. Are you using a workaround? If yes, please describe it.Workaround is to use revision Management in the file naming, Wouw.... just as not using PLM! Or just not use the Windchill system but stay with the current method for ci 1 - 10.1 Shared_Prefs in EV4. What is the use case for your organization? Describe how your idea
1. Describe the Problem Creo Relations IF statements are missing ELSEIF or ELSE IF ability: https://support.ptc.com/help/creo/creo_pma/r11.0/usascii/index.html#page/fundamentals/fundamentals/Conditional_Statements_in_Relations.html Most languages have ELSE IF (ex: C# https://www.w3schools.com/cs/cs_conditions_elseif.php or C++ https://www.w3schools.com/cpp/cpp_conditions_elseif.asp) ELSEIF provides: Less verbose relations that are easier to read and write (see example below). Clear intent that only one of these IF, ELSEIF, or ELSE statements should be evaluated. Potentially faster evaluation of the relations. If one of the IF or ELSEIF statements are met, none of the remaining ELSEIF or ELSE statements need to be evaluated. Presumably Creo would use ELSEIF (without a space) to match the lack of space in the current ENDIF. Current workaround 1 (lots of separate IF statements): Not always clear if only 1 of the IF statements should be evaluated
1. Describe the ProblemModelCHECK is used to check for spelling errors in 2D drawings in Creo Parametric. However, the settings for ModelCHECK are controlled by administrative rights. Creo Parametric drawing mode needs to have a bult-in spell checker other than ModelCHECK or allow the end user to configure ModelCHECK for spelling without admin rights. 2. Are you using a workaround?No. There is no workaround to the admin rights.3. What is the use case for your organization?Giving the end user control over the spell checker will greatly enhance the overall quality of 2D drawings.4. What impact does this problem currently have on your organization?Cannot spell check drawings. IT department is understaffed to resolve the problem.
1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.Design systems / assemblies to address client challenges - from initial concept to delivering final product. 2. What version of Creo Parametric are you currently running?83. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. Unused models in drawings can only be deleted one-at-a-time from within the drawing and are only accessible from an old antiquated DOS-like menu. Unused models can accumulate from drawing revisions and if a drawing is copied and views are edited. You may not even know you have unused models that are taking up memory. And if you do know there are unused models in your drawing, it takes an inefficient use of effort and time to remove them. Modelcheck can be used to strip unused models from a drawing, but that's another step that shouldn't be necessary
Family table, "Copy instance to Generic" behavior is wrong. It prompts for "delete" action on feature If in a generic model i have a suppressed feature, in instance it is necessary to use * because creo will delete the feature in the family table and directly in the generic model tree. And if i have an active feature in the generic, using N on instance will delete features in the family table and directly in the generic model tree.Is it possible to activate boolean operation feature with family table when you want to use the feature copy instance to generic.If you want reproduce it : Open Part > Family tableSelect a feature as columnInsert Row > select "N" for feature Select instance row > Edit > Copy to genericThis fonctionnality is not working well and it is necessary to improve it.
Currently it is not possible to copy and paste special entire annotation features (with multiple elements) between different models, if there are surface references (for semantic relationship). Deleting the surface references enables the paste special functionality. It is possible to copy and paste annotation features with surface references within the same model. Proposal is to 1) Add a notification or prompt to user that CREO will automatically delete surface references upon pasting into a different model, or 2) Provide functionality to redefine references to surfaces (all solid surfaces for parts, discrete surfaces or quilts, discerete part surfaces etc).
It is necessary to provide the possibility of placing datum feature symbols on dimensional auxiliary lines of angular dimensions.This placement is already possible for linear dimensions. This is important for a reasonable use of the MDB and a fast and error-free generation of a drawing.
Currently you can not use a parameter in the additional text fields of a GTOL. If you try you will just get the text as you typed it and not the parameter value. See attached image for an example. This should work like notes, and virtually every other place within Creo. My main focus for this request if for model annotations but the same could apply to drawing annotations. This does not work in Creo 3 or 4.
Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Parametric (7.0.9.0, applies to all versions)2. What is the problem?I can open this model in an empty simp rep, open the simp rep manager, and create or edit a simp rep--all without loading any 3D CAD. But if I want to get past this screen, my only choices are to Open (saves the simp rep definition and opens it to the graphics window), Cancel (undos any changes I made), or Apply (opens it to the graphics window but does not save the edited simp rep definition). This feels like what was most likely an oversight in the original UI design and was just never properly addressed, I should be able to just press something like "OK" and return to the previous screen without being forced to load all those models.3. Are you using a workaround? If yes, please describe it.A full workaround is not possible. While you can modify simp reps from the model tree to avoid the dialog
Currently, the only way to edit a simp rep, and then save those edits, is to make the simp rep active. When a simp rep contains a large number of items in a large assembly, the entire model must be loaded into memory before the simp rep can be edited. Enabling users to edit a simp rep without activating it would save time and resources in cases where 1 item needs to be added to the simp rep of a large assembly. Then next time the assy file is opened to that simp rep the edits will become evident.
1. Describe the Problem User's must log in again when launching Creo View from an already signed in session of Windchill. The second login was not required with Internet Explorer. This is very frustrating for users to log in twice. 2. Are you using a workaround?There is no work around to making the user waste time log in to open Creo View from an already logged in session of Windchill. We have entered Case C17831347 with Tech Support for reference. 3. What is the use case for your organization?This applies to all organizations that launch Creo View from Windchill. In Internet Explorer version of Windchill and Creo View Interaction, User launches IE, goes to Windchill address and logs in. Finds a representation and uses open in Creo View and Creo View opens WITHOUT additional login. In Chromium Browser(Edge, Mozilla, Chrome), user launches browser, goes to Windchill address and logs in. Finds a representation and uses open in Creo View and is AGAIN presented with the same po
1. Describe the ProblemThe current capabilities of Creo Parametric support only the export of filled welds to XML, which can be utilized for programming welding robots. This functionality ensures that the filled welds are accurately represented and can be effectively used in automated welding processes. However, non-filled welds are not included in the export process. As a result, these non-filled welds cannot be utilized for programming welding robots, which may limit their applicability in certain automated manufacturing scenarios. This distinction is important for users to understand, as it impacts the overall efficiency and flexibility of the welding automation process.2. Are you using a workaround?Manual effort for the weld path generation, which requires physical components.3. What is the use case for your organization?Extending the XML export capability to include a comprehensive range of weld types would significantly enhance our efficiency in robot weld path generation. Curren
1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.My company is a manufacturing company, I am a "Project Engineer for PLM & design services". My stakeholders are Windchill and CAD users in the design department.2. What product and version are you currently running?Creo Elements Direct Modeling 20.4.1, Creo Elements Direct Drafting 20.3.2, Windchill PDM Link 12.1, Windchill 12.0.2 and other PTC products3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.When creating a sheet metal part in Creo Elements Direct Modeling with several bends and lips there is currently no warning for overlapping contours in the „Unfold 2D“ command in Sheet Metal or the „Create Flat“ in Annotation. Unfold 2D command in Sheet Metal module, sample of simple overlapping bends:Create flat command in Annotation, sample of simple overlapping bends:Users in the design
Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Elements Direct Modeling 20.6.0.0, Creo Elements Direct Drafting 20.6.0.0, and other PTC products2. What is the problem?In all modeling versions, options for standard-compliant representation according to DIN EN ISO 21920-1 are missing3. Are you using a workaround? If yes, please describe 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.You cannot work according to the norm5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
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.