Recently active
Creo Parametric comes with a library of ISO weld symbols, based on the ISO 2553 from 1983, as detailed in the following help page :https://support.ptc.com/help/creo/creo_pma/r9.0/usascii/index.html#page/detail/User_Defined_Parametric_Weld_Symbols.html This standard has been updated in 2019 with new symbols that my company need to use.According to this article, this update is not planned : https://www.ptc.com/en/support/article/cs303110 We need the default Creo weld symbols library to be updated to the 2019 ISO 2553 standard.
1. Describe the ProblemHow can I load a Creo Elements Direct Modeling file into Creo Parametric or integrate it into an assembly if the file has been moved from the zero point in Creo Elements Direct Modeling?The zoom function “Fit new” is used to zoom to the entire model including the auxiliary KEs such as plane and axis. This is why it is not possible to find the model in 3D space in this way; it would make more sense to limit this zoom area to the actual surface or solid model. How does PTC imagine how to work with such CED models in Creo Parametric, because there are an unlimited number of these CED models with moved zero points? For us in the company, this is already a UNITE showstopper before we can really get started. INFO: The video was filmed in Creo Parametric 7.x, but also detected in Crep Parametric 10.x. 2. Are you using a workaround?No workaround at the moment3. What is the use case for your organization?Usecase see in the attached video. Creo Parametr
1. Describe the ProblemCreo can specify jogs on Dimension line, but ProToolkit API is missing to retrieve those points. Please add API, so we can get those points.2. Are you using a workaround?No. I have contacted PTC support and they confirm API is missing to retrieve them.3. What is the use case for your organization?We develop app as third party, and we cannot identify dimension line direction.4. What impact does this problem currently have on your organization?It is considered as our application's bug.
In the model threads are currently shown as cosmetics. Currently in shaded view the difference between a Thread hole and Through hole can't be seen. Enhance so that the actual thread is shown in the shaded view, for instance by projecting a picture/decal of the correct thread type into the bore of the hole (Inventor does this and also all video game engines add detail to their models by doing so). The picture/decal keeps the models light (so that no helical sweep feature is needed for this), but makes it clear in shaded view and pictures of the shaded view that a thread hole is inside the model or a thread is at the outer diameter of a shaft.
Hello everyone,If you like below thing that should be available in Creo Part modelling multibody THERE SHOULD BE A WAY TO CREATE MULTIPLE SHEETMETAL BODY IN SAME PARTYour reply is very valuable for me
1. Describe the Problem We are slowly going through our current libraries and adding them to the Intelligent Fastener Extension (IFX). We can not add our SEM screws, as they have been built as an assembly and IFX can not manage assembly hardware. 2. Are you using a workaround?No. We are not using IFX for this type of hardware.3. What is the use case for your organization?We use SEM screws in most of our products. Having some hardware in IFX and others not, does not make for a robust library and process.4. What impact does this problem currently have on your organization?It creates confusion with process, implementation and part searching.
1. Describe the ProblemNo way to add embedded datum references when assembling components together. There is the datum reference button present but the references get added to the model tree and they are not automatically hidden. 2. Are you using a workaround?Yes, just adding the references needed prior to assembling component.3. What is the use case for your organization?We create sheet metal assemblies with solid component fixtured at angles. The current process is to add a datum plane or axis, then constraining through points. all of which require opening up multiple components and adding duplicated references to allow this to work in the assembly.4. What impact does this problem currently have on your organization?Risk due to added references, and wasted time due to working in independent parts.
1. Describe the Problem We would like to be able to use the find tool to search for component constraints in assemblies. Right now, we can only search for sets. However, we can't search for the constraints themselves (default, offset, coincident...) 2. Are you using a workaround?We have to expand all the full model tree and then export it, and use a script to analyze the constraints3. What is the use case for your organization?We would like to know if the first constraint of the assembly is default.4. What impact does this problem currently have on your organization?The process to expand all can take minutes on very large assemblies, which slows the mapkey and script.
1. Describe the ProblemThe problem is that there is no method with Toolkit API's to set a table display name in the model tree, or test if a specific table name exists, and get a handle to that table by model tree name if it does exist. 2. Are you using a workaround?Yes. One workaround I will consider is to record the ID number of the ProDwgtable object (pro_model_item) created by ProDrawingTableCreate(). To check if that table exists from a previous use of the Toolkit, I will look through the array of tables returned by ProDrawingTablesCollect() for that saved ID number.3. What is the use case for your organization?I am using Toolkit to create a new drawing table in a drawing. This new table has specific data. If the user re-runs the toolkit, I want to delete the old table that was previously created by the toolkit, if it exists, and recreate it with updated data.4. What impact does this problem currently have on your organization?This affects the organization by requiring the bu
1. Describe the ProblemI use combined states to create visual configurations of my sub-assemblies (appearances linked with simple reps). Instead of creating multiple sub-assemblies with multiple names, I create one sub-assembly and assembly it into multiple top-level assemblies, each requiring a different combined state to represent the correct configuration. Unfortunately one cannot select the desired combined state of the sub-assembly when assembling into a top level assembly, which makes it such that I need to create multiple save-as copies of the sub-assembly, just to vary the appearance (simplified reps can be selected during assembly but not combined states). In an environment where my sub-assembly frequently changes, it's not acceptable to modify each save-as copy. 2. Are you using a workaround?I am bypassing the ability to change appearance, which is a severe bottleneck.3. What is the use case for your organization?We use colors to represent configurations and locations of
1. Describe the ProblemRefer to C17731747, because of 3D file data broken possibility, it has chance to still include the "AF*" character information in the outputted STP file. We want to add two functions below:1. When user outputting the STP from Creo, it can show the message to hint user when the data is broken.2. When using toolkit to output STP, there is added argument of the API to show if the outputted data has "AF*" character information or not.2. Are you using a workaround?No3. What is the use case for your organization?We need to output STP to another CAD program for design check.4. What impact does this problem currently have on your organization?Can't perform some check items.
1. Describe the Problem Just like there is a config to point to the GD&T options file (gdt_advisor_app_options_file), there should also be one for Intelligent Fastener Extension (IFX) file (ifx_options.xml). Currently, the only way to set this non-default location is with an environmental variable IFX_USER_CONFIG_PATH - NOT a creo Config. We shouldn't be overcomplicating this process for the admins. It should be a simple config.pro/sup options that admins can manage. 2. Are you using a workaround?Yes. We are using our startup script to copy our custom ifx_options.xml to the default text folder location.3. What is the use case for your organization?We are setting up IFX to use our custom hardware, requiring a custom ifx_options.xml. 4. What impact does this problem currently have on your organization?This approach is non-standard with most other methods of pointing to custom configuration files. Having other team members aware of this method and how to control it is very d
1. Describe the ProblemIt's not possible to add combined state appearances to various drawing views in Creo Parametric.Detailed Description:The appearance of model in drawing views will be changed according to the active appearance state in 3D.See also SPR 6392371See also CS255181 & CS3419802. Are you using a workaround?There is no workaround available.3. What is the use case for your organization?Using different color appearances to show different states of the Model on various drawing view. For Example: Differernt coatings on different surfaces or different machining operations.4. What impact does this problem currently have on your organization?Desired conditions, such as coating definition, cannot be shown on the drawing. Additional Documents have to be created.
1. Describe the Problem Request to include the countersunk name in the IFX hole definition window for easier accessibility and user-friendly navigation. 2. Are you using a workaround?No3. What is the use case for your organization?easy to navigate4. What impact does this problem currently have on your organization?users seeking this options to have on UI
1. Describe the ProblemCurrently, in Creo Parametric, it is not possible to assign entire drawing views to layers. This limitation makes it difficult to control the visibility of specific views, especially for purposes such as exporting to PDF, where we may want to include or exclude certain views dynamically I propose that Creo Parametric should support the ability to assign drawing views (general, projection, detailed, etc.) to layers, similarly to how annotations, symbols, or datum features can be managed. This would allow users to hide or show entire views through layer visibility settings, simplifying the process of preparing customized drawing outputs ( simplified versions for customers, different configurations for internal documentation ) and managed views in exported PDF ( show, hide,...)2. Are you using a workaround?No. it is not possible.3. What is the use case for your organization?A drawing contains multiple views, including a main assembly view and an exploded view.
Please vote if you want to have an option where Creo CAD objects could be easily displayed and manipulated in tabs like in web browsers, FoxIt, & WF4: More Details:ProE could display Tabs for all open objects, very similar to what Firefox and all web browsers do (and FoxIt pdf viewer). This way the user can see all objects open and click any one to activate. You could put tabs above (like in IE, Firefox, Chrome, etc) or to the left/right. Although a bit rough around the edges, ProE WF4 could do this yet Creo cannot. Reference Poll for more information:http://communities.ptc.com/polls/1252 Related Discussion:http://communities.ptc.com/thread/39944(if links do not work, manually copy/paste them to address bar)
1. Describe the ProblemThe hole tool uses shoulder depth as the default way to dimension the depth of the holes.In our case, we want to always define the depth by the tip of the drill but there is no config setting or model detail option to choose which should be the default. Please add some way to select the default way of dimensioning hole depth.Currently there is no way:https://www.ptc.com/en/support/article/CS380562Old idea about the same feature request was rejected for some reason:https://community.ptc.com/t5/Creo-Parametric-Ideas/Pro-MFG-hole-drilling-ability-to-set-default-option-either-per/idi-p/465635 2. Are you using a workaround?Yes, manually selecting the tip options every time holes are created.3. What is the use case for your organization?We make holes that need to be as deep as possible without penetrating to other features. Using tip depth as a default and communicating to manufacturing that every hole is dimensioned to the tip would help in avoiding manufact
1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.ElectroMechanical Engineering2. What version of Creo Parametric are you currently running?7.0.2.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.IEC 81346-2 defines that electrical product designation shall start with a "-", while this is supported in Windchill for Reference Designators by including the name in [ ], Creo doesn't support this use case.4. What is the use case for your organization?Maintaining Reference Designators according to IEC 81346-2, in all the tools5. What business value would your suggestion represent for your organization?Better data quality, less manual work in WT-Part structures by adding a simple "-" to each and every electrical designation
1. Describe the Problem With the ProUIMessageDialogDisplay Toolkit function, message dialogs can be displayed easily and without much effort.There are four different types to choose from: typedef enum { PROUIMESSAGE_ERROR = 0, PROUIMESSAGE_WARNING = 1, PROUIMESSAGE_INFO = 2, PROUIMESSAGE_QUESTION= 3 } ProUIMessageType; Depending on the selection, a suitable icon is then displayed in the dialog so that you can quickly see what the message is about.Unfortunately, the same icon is displayed for info and question dialogs, which makes it difficult to recognize questions: For question dialogs, one would expect a question mark icon in a clean UI concept! 2. Are you using a workaround?Of course, you could create a suitable question dialog yourself using all the other UI components available in Toolkit. But due to the simplicity of using the ProUIMessageDialogDisplay function, I don't see
1. Describe the ProblemThere is no way to create a parametrically driven view note/label for an individual drawing view. No known way to get a manually-created note to display the parametric value of a specific view's name. No known way to prompt Creo to make a view note/label for an individual view [without having a config option set to create view notes/labels for all views of the same type - only for proj and aux views]. There is no way a user can have their system configured for views to be created without a view note/label and then choose individual views for which they should be created. Prior prompts by the customer base for the same/similar functionality.https://community.ptc.com/t5/Creo-Parametric-Ideas/Further-functionality-for-Creo-Parametric-DRAWING-View-Labels/idi-p/454335https://www.ptc.com/en/support/article/CS188310?source=searchhttps://community.ptc.com/t5/Creo-Parametric-Ideas/Always-enable-ability-to-Add-View-Label-in-a-drawing/idi-p/8376302. A
1. Describe the ProblemUnlike with an Auxiliary view, Creo does not offer the option for a user to display a single projection arrow for a Projection view in accordance with ASME Y14.3. The user can select between display double arrows, or not display any arrows. 2. Are you using a workaround?Yes. Users generally take one of two options. 1) switch view type to Auxiliary, redefine the projection reference, and use the available functionality to display a single projection arrow. 2) use a simple arrow symbol with variable text annotation note for the view name, and manually rotate the symbol to align with the orientation of the view.3. What is the use case for your organization?When creating needing to turn a projection view into a removed orthographic view, ASME Y14.3 requires a view note/label and projection arrows for Identifying Removed Orthographic Views. The standard provides the option of using a single reference arrow, or a double arrow viewing plane. Creo functionalit
1. Describe the ProblemCreo has the ability to rotate the orientation of General views; however, Projection and Auxiliary views do not have that same functionality. Creo makes it easy to remove the alignment of projection and auxiliary views and create correctly-oriented projection arrows which aligns with ASME Y14.3's expectations for Removed Orthographic Views. There is no way in Creo to rotate these projection and auxiliary views to create Rotated Orthographic Views described in ASME Y14.3. 2. Are you using a workaround?Yes. As described in Workaround 1 of PTC Article - CS18619, users have to switch the type of view to a General view which will allow rotation. They then need to manually recreate projection arrows used for Identifying Removed Orthographic Views as defined per ASME Y14.3. What is the use case for your organization?Efficiently meeting the expectations for Removed Orthographic Views, Identifying Removed Orthographic Views, and Rotated Orthographic View
1. Describe the ProblemWe would like the ability to add size tolerances to the notes generated by the Hole feature when applying standard hole types. Per ASME Y14.5 Specification for Dimensioning and Tolerancing, features of size must include a tolerance. For example, a counter-bored clearance hole for a 1/4"-20 fastener must include tolerances on both diameters but we can currently only produce variations of the following note:According to the spec, we need to provide a note similar to this:Notice how each dimension has a tolerance, there are no zeros before the decimal places, and a geometric tolerance is attached.2. Are you using a workaround?A work around is available by following these steps:Create desired hole using Creo's Hole FeatureSelect "OK" to apply the hole and exit the Hole featureRight-Click the hole feature in the model tree and select "Edit Dimensions"Add tolerances to each of the hole's dimensionsGather each dimension's respective d#Show the standard hole's diameter d
1. Describe the ProblemWhen looking to do Model Based Design in a model looking to have the ability to show Ordinate Driving Dimensions as we would with a Linear Dimension would be shown, or how could be done on a 2D Drawing. This was reported in 2013 with Creo 2 under CS1522042. Are you using a workaround?Workaround is to use Driven Dimension which is not desired process when Driving Dimensions are available. Another workaround is to continue using linear dimensions which can be difficult to display legibly on more complex designs3. What is the use case for your organization?Being able to use full Driving Dimensions with a 3D Annotated model without the need for a workaround to accurately illustrate complex designs4. What impact does this problem currently have on your organization?Either a cloud of linear dimensions, creating additional 3D combined states for clarity, or Driving Dimensions
1. Describe the Problem In Creo 8.0.4.0, which we used previously, you could use multiple TAB characters to separate the IFX specification values in the fastener .dat files.For some reason, in Creo 8.0.12.0 this is not possible anymore and IFX gives an error (pro_tk_e_not_found) if the IFX fastener catalogue .dat files use multiple TABs to separate the value fields. This makes maintenance of the .dat files more complicated and error prone as the values cannot be arranged in a human readable format.Our old .dat file format (which does not work anymore): And the format I have to now use to make IFX work: So you can see that in the lower picture it is incredibly hard to differentiate which value belongs to which column/parameter. 2. Are you using a workaround?Yes, file format with single TABs as separators.3. What is the use case for your organization?Ease of administration of IFX library.4. What impact does this problem currently have on your organization?It slows down our IFX mainten
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.