Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Better support for 3D ECAD Context Data in Creo ViewAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo View 11.1 2. What is the problem?Reference Article: CS444532 When ecad context data is published from Creo using convECADConductors = 1, it has some issues in Creo View: 1 - The quality of the generated graphics is extremely subpar.     2 - You can't turn on/off the visualization of the data 3 - The file size is drastically increased over a file without the context data. We had a full PCB, with components at about 800kb. The ECAD context data, which just added some poorly generated quilts, brought it to 2mb!3. Are you using a workaround? If yes, please describe it. No. We are not going to generate the data as it is 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.Our company makes many products, all with PCBs. Our processes and workflows are built around PCBs. We would like to leverage as much of the CAD data for the downstream teams as possible, including the ECAD Context data. Unfortunately, we can't.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)We won't be able to review and leverage this information, which has led to design issues in the past.

Creo Illustrate Windchill Connection - true Windchill search in Import dialogAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Illustrate 11.0 2. What is the problem?In the Import dialog, when accessing Illustration Source objects in Windchill, there is no option to search for objects by name or number in Windchill. The misleading "Search" field in the Import dialog doesn't actually search, it merely filters items in the current folder. It would be extremely helpful to be able to enter a part number (or partial part number with an asterisk) and return the results of a true Windchill search to find the desired Illustration Source3. Are you using a workaround? If yes, please describe it. Just have to know where to look, drill down to the appropriate context and folder manually and then locate the desired Illustration Source4. 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 is self-evident. User wants to find an Illustration Source for a part or assembly, but maybe doesn't know exactly where it's stored. They should be able to put in the name or number and find it via search.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Varies, but can make it difficult to find Illustration Source when you don't know where to look to begin with

Allow Drawing Views to be assigned to Layers for visibility control and PDF exportAcknowledged

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. The user wants to generate two PDF outputs: one with only the main view and another with the exploded view. If drawing views could be controlled by layers, this would be a simple toggle of layer visibility before export or in PDF, instead of creating duplicate drawings or using complex workarounds.4. What impact does this problem currently have on your organization?No

Use of a suitable icon for message dialogs of the "Question" typeAcknowledged

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 this as the optimal solution. Since the ProUIMessageType enumeration has explicitly defined the "Question" type (PROUIMESSAGE_QUESTION), it is reasonable to assume that the use of a suitable icon has simply been forgotten.3. What is the use case for your organization?As previously mentioned, the great advantage of the ProUIMessageDialogDisplay function is that it can be used quickly and easily. This is why we use it very frequently for simple message dialogs.4. What impact does this problem currently have on your organization?At the moment, the disadvantage is simply that question dialogs cannot be immediately recognized as such, as the info icon is somewhat misleading. This problem was previously reported to PTC Technical Support (C17680840), but was not recognized as a bug, but classified as a wish for improvement. However, I think it is also in PTC's interest to have a clean UI concept for Creo and Toolkit and it should be out of the question that a suitable icon is implemented for question dialogs.

Creo View to open Adobe Illustrator (.ai) filesAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo View 11.1 2. What is the problem?Creo View can not open Adobe Illustrator files. What is interesting about Adobe Illustrator files, is that Adobe Acrobat & Adobe Reader can open them. Which means, if someone without Adobe Illustrator would take a .ai file and rename it to .pdf, it can be opened easily! Therefore, I believe Creo View could easily be updated in the future to open these files, if they use the same viewer technology as a PDF. No real development work would be needed!3. Are you using a workaround? If yes, please describe it.Renaming it to .pdf - which most users don't know about or forget because they don't do it often.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 use adobe illustrator files for our artwork. We would like to use Creo View MCAD Compare to help determine what changed with each revision. This would then enable downstream teams to determine what work they would be required to do.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.) We would be unable to see the exact changes from revision to revision in a clean, easy to read and understand method. Users: ~100  

Ability to generate view notes/labels for individual drawing views of all types.Acknowledged

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. Are you using a workaround?The historical practice has been to use a customized symbol that mimics what the system-generated view notes/labels look like. The symbol uses manually-populated text to show the view name, which is obviously not parametrically-driven from the actual view name, and therefore can potentially deviation from any other object that is driven from the actual view name (e.g.- generated projection arrows). A more recent workaround tries to leverage the config option for creating view notes/labels on all auxiliary views which are less commonly used than projection views [and so there's less impact to needing to delete all of the unnecessary view notes/labels for auxiliary views that remain aligned with their parent]. If a user needs to create a removed projection view, they can switch the view type to Auxiliary, redefine the projection reference, and then leverage the system-generate view label and corresponding projection arrows.3. What is the use case for your organization?View notes/labels (along with corresponding projection arrows) are most valuable when a projection or auxiliary view needs to be misaligned from its parent view (refer to Removed Orthographic Views in ASME Y14.3). The most common practice is for a drawing to have projected and auxiliary views that remain aligned to their parent view. For these aligned proj/aux views (which would be the vast majority of views), there is no need to have a view note/label [or the corresponding projection arrows]; the config options 'make_proj_view_notes' and 'make_aux_view_notes' would be best set to "No". It would then be most beneficial for a user to be able to select specific views and apply a view note/label as needed; for those less frequent scenarios where a proj/aux view needs to be removed/misaligned. Currently, view notes/labels can be added in Creo; however, this is available only for projection and auxiliary views when the above config options are set to "Yes" - seemingly to help a user add labels to views that already existed. The request is to simply make this functionality always available to users no matter what the config option values are and no matter what type of view. This could be provided in a view's properties similar to how projection arrows for projection and auxiliary views are provided today. Alternatively, the RMB>'Add View Label' on a view would also be sufficient provided it was always available (see attached image).4. What impact does this problem currently have on your organization?It is inefficient to use Creo to create product definition that is in accordance with this scope of ASME. In order to realize the benefit of parametric product definition (linked display of view name in view note/label), users have to unnecessarily switch the view type and redefine projection references. Even though it's more work, users are more commonly using the legacy CAD behavior of dropping in an annotation note and manually-typing-in a value for the view name. Desired functionality already exists with Projection and Auxiliary views when the two mentioned config options are set to "Yes", so this is thought to be a lower effort change with significant efficiency and quality gains.

Ability to select None, Single, or Double projection arrows for Projection views (as with Auxiliary)Acknowledged

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 functionality for Auxiliary views provide both Single and Double projection arrows nicely; however, Projection views do not provide the same ability to efficiently meet the expectations of ASME Y14.3.4. What impact does this problem currently have on your organization?It is inefficient to use Creo to create product definition that is in accordance with this scope of ASME. In order to realize the benefit of parametric product definition (auto-oriented projection arrow, linked display of view name in projection arrow and view note/label), users have to unnecessarily switch the view type and redefine projection references. Even though it's more work, users are more commonly using a legacy CAD behavior of a simple arrow symbol manually rotated to what looks close to the correct angle and using a manually-entered note to display the view letter. Desired functionality already exists with Auxiliary views, so this is thought to be a lower effort change with significant efficiency and quality gains.

Ability to rotate Projection and Auxiliary drawing views (same as General views).Acknowledged

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 documented within ASME Y14.3. Refer to attached image of Fig. 6-4 from ASME Y14.3.4. What impact does this problem currently have on your organization?It is extremely inefficient and error-prone to use the workaround described above. Turning a removed projection or auxiliary view into its own general view loses parametric connectivity to the parent view used for Identifying Removed Orthographic Views as defined per ASME Y14.3. Any generated projection arrows are lost and have to be replaced by a simple symbol that is placed on the drawing and manually oriented to display the correct angle of projection. Using a general view eliminates the ability to display a parametrically driven view note/label (unless one already existed for the projection or auxiliary view prior to changing it to general). There is also not a way to parametrically connect the display of view name in the projection arrow symbol to maintain connectivity with the name of the view, so a user has to try and manually keep the view name annotation and projection arrow symbol in sync during creation and future revisions. Desired functionality already exists with General views, so this is thought to be a lower effort change with significant efficiency and quality gains.

Add size tolerance to Hole Feature's standard hole notesAcknowledged

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 dimension using "Show Annotations" (Ø.281 in example above) Select the Ø.281 dimension and select "Dimension Text"Insert all the necessary d#s (also p#s for patterns). For the example at hand, enter as shown below:      9. Attach a Geometric Tolerance from the annotations tab NOTE: GD&T Advisor also provides for another workaround but does not work properly with hole patterns created by the "Sketched" type. GD&T Advisor doesn't recognize the pattern or hole feature when using "Sketched" type.3. What is the use case for your organization?We would use this fix for all standard type holes, including tapped, drilled, and clearance. I've seen this idea requested a few times but they have all been archived due to not providing enough information. Hopefully I have supplied enough.4. What impact does this problem currently have on your organization?This problem utilizes significant amounts of time for each design that could be much more efficient. It also leads to many mistakes from typos, error to include dimensions, and has to be re-done each time a hole's features are changed (add/remove countersink, counter-bore, etc.). It also requires a bit of a learning curve to complete the workaround, leading to repetitive issues by new employees. Essentially, the Hole Feature's Note generator is useless if any drawing must conform to the ASME Y14.5 specification.