Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Updating objects in your workspace shouldn't flag an object as modified in Design ExplorationAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Parametric 8.0.8.0 2. What is the problem?Reference:  Case - 16406179 SPR - 13945104 Article - 373237   If we are working in design exploration, and update objects in our workspace that are in the current checkpoint, a new checkpoint is created which flags those items as modified. If you are not in session, updates to the workspace do not cause this problem. However, once the problem occurs, there is no way to undo it. This was noticed too late by our users and now when they try to push a checkpoint out, it includes hundreds of instances from family tables that are also getting pushed out.... because they were in the DEX modified session. Cleaning up these issues are very difficult. Please enhance this capability, as we can't use DEX if it has such large gaps in workflow.3. Are you using a workaround? If yes, please describe it.No. We have stopped using DEX. In theory it is a great tool. In practice, it needs much improvement, specifically regarding Windchill.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.Idea: Any time an object is updated in the workspace, while DEX is opened, it loads the object and does NOT flag it as modified. Maybe even a prompt asking the user whether they want it modified is sufficient.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)~50 users. HUNDREDS of hours. Maybe thousands. We were trying to use DEX as a way to jump-start designs, but we can't jump start designs if workspaces can't be managed with thousands of hardware parts (screws...) getting pushed out from DEX that shouldn't be.

Dependent Sketches with Varied Items - Name OverrideAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo 9.0.3.02. What is the problem?We draw kinematic skeleton assemblies to describe a linkage system with fixed pivot points, constant member lengths, and one actuator. This skeleton pushes data forward into downstream component models. The length of the actuating member changes, and during development, so do the fixed points and lengths. I use copied dependent sketches with varied items and vary the actuator member length to show the system in various states of travel- this is quicker and much more efficient than drawing a new system and constraining it to parent members. When you modify the parent (copied) sketch creo automatically changes the name of the children sketches to "Copied Sketch ##" This makes the model tree cluttered and disorganized as the children sketches should have names describing the system's state.  How I would like my model tree to look: How it looks after updating parent sketch "MASTER_KINEMATIC"  3. Are you using a workaround? If yes, please describe it.I am currently adding a note to the sketch to keep it organized in the model tree  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.Don't automatically rename or override the manually inputted name of dependent copied sketches when the parent is updated. 5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)This problem causes confusion among team members sharing skeleton files. Not knowing the state of the linkage system represented in the sketch makes collaboration difficult,  

Display Pipeline Reports (e.g. Bend Tables) in Creo ViewAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Parametric 7.0.9.0Creo View 8.1.0.02. What is the problem?Pipeline reports (e.g. bend tables) can only be accessed from within Creo Parametric. Existing support article CS378897 suggestion to manually input bend table information in comments is unsatisfactory for handling this type of information in Creo MBD.Creo MBD releases are handled via PVZ exports opened in Creo View, so this type of data should be preserved and viewable from the released PVZ.Ideally, the various reports would be published within the PVZ and accessible in a convenient location when selected a pipe model. The Lower Data Panel seems like an ideal location for just such metadata, where additional tabs could be implemented. A mockup of this idea is shown below:3. Are you using a workaround? If yes, please describe it.The workaround as it stands is to manually input bend table information into callouts, or simply give up trying to use MBD for piping assemblies and revert to 2D drawings with tables.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 would not only allow MBD to be used for piping assemblies, but also reduce the burden of creating additional bend tables when the metadata is already present and accessible.

Use Explode Assigned to Combined StatesAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Parametric 7.0.9.0Creo View 8.1.0.0Creo Illustrate 8.1.0.02. What is the problem?Creo Parametric authored combined states can be assigned a particular Explode. However, when published as a PVZ, the resulting file retains no knowledge of which Explodes were assigned to which Combined State Viewable. Any user navigating the PVZ in Creo View or Illustrate must manually choose the correct Explode to use.Creo View and Illustrate should provide a mechanism that allows the user to toggle the Explode assigned to that Viewable (Combined State) separate from choosing from the entire list of Preset Explodes.3. Are you using a workaround? If yes, please describe it.The workaround currently employed is to carefully name explodes and combined states so that the user can intuit which explode is intended to be used with a given viewable. 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.When consuming MBD or authoring MBI work instructions, it would take a lot of the guesswork out of the process if the PVZ retained knowledge of which explodes were assigned in a given state.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Hundreds of users at our organization could benefit from this.

Creo Illustrate light scenes issue with object color vs. shadow appearanceAcknowledged

Dear PTC and community1. What product and version are you running?Creo Illustrate 9.12. What is the problem?We facing the issue in Creo Illustrate that caused by OOTB Light scenes the object color appear grey due to shadow effects.For getting an adequate Image we would to get rid of the lights (creating the shadow) and/or adjust a adopted Lights scene to have best result acc. appearance.E.g. even that the left figure is not identical acc. part arrangement - the grey colored fridge frame is white, but appear due to light sceene grey. The right figure showing the expected result we want to achieve. 3. Are you using a workaround? If yes, please describe it.Not at Creo Illustrate - manual rework in other graphic applications possible but time consuming and inefficient.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.Many illustrations should have an adequate appearance of the objects displayed.Many documentations are created over the whole enterprise.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Impact - rework with other graphics application Time and license cost)The whole enterprise creating a lot of figures used in customers dicumentation. They might be several hundreds of documentation engineers which beed affected every day.

Solidworks Converter from Creo View can't generate any corners and edgesAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo View 10.0.0.02. What is the problem?There is an functionality in Creo View Converter to convert Solidworks data / model to pvs data using command line, but the generated data has no corners or edges. This make measuring in Creo View difficult.3. Are you using a workaround? If yes, please describe it.If we are using the same converter from Creo View to convert the Solidworks data into iges, then using the same functionality to convert from iges to pvs, it's working fine. Corners and edges are generated.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 would like to convert Solidworks data to pvs using converter sw2pvdirect.exe with corners and edges generated. PTC advised to use Creo View Adapters to do this, but this is not available on our organization (PTC Case already opened).5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Users can't measure in Creo View properly for the data generated using sw2pvdirect.exe - For now we have to convert the Solidworks data into iges first, then from iges to pvs.From our point of view, it should be possible for the converter sw2pvdirect.exe to convert Solidworks data with corners and edges, since it's possible for the Solidworks - Iges converter.

Update Mass Properties when model units are changedAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Parametric 8.0.8.0 2. What is the problem?Reference:  Case: 15985425 SPR: 13172667  Article: 351209   When we convert a model from one unit to another, any regular "Real Number with units" parameter gets updated properly. Both the unit and the value changes. However, the mass properties units only get updated, the number stays the same as the old unit. For instance, if the value for PRO_MP_VOLUME is 1in^3 and then the model gets converted to metric, the parameter will now show 1mm^3. The value should be updated WITH the unit automatically, like a regular parameter. Having mismatched data like this, can cause serious issues downstream.3. Are you using a workaround? If yes, please describe it.We need to regenerate the model after the update, before we get the correct values. However, until a manual regeneration is done, there is a significant error in the parameters.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 mass properties and there is a risk that the incorrect data could be sent to Windchill due to this issue. The idea is simple. When the model unit is converted, the mass properties value should be updated with the unit.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Incorrect data in Windchill can cause countless downstream errors, including supply chain, legal, purchasing, etc. Hundreds of users, and hours could be affected. In addition, there could be contractual issues where we assume a certain amount of material is being procured, but the truth is very different.

MBD - 2D Detailing - future visionAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Parametrics, 8.0.4.02. What is the problem?Missing options to define links and relations between: Saved Orientation / Annotation Plane / Combination State, and force Annotations more automated to take on definitions without loosing them again. Currently I'm working out a MBD Process (or try to do so) for our RD&E team. The aim is, that all Annotations are created in 3D by deriving dimensions from 3D features and enhance them by additional Annotations e.g. GTOL, text, Symbols and so on. All this is proper sorted in Combination States, using Sections if necessary, or datum planes in case the Annotations need a specific offset from the geometry. The intension (my future vison) is, that the Combination States shall represent the views in 3D and they shall be used in 2D drafting to create the views there (because this will remain a mayor requirement of the method). This without doing additional work on. Not only because we are lazy people, but as well because between 3D and 2D no difference shall exist. Such a method finally should not cause a bigger effort than doing it "conventionally" as, leave the method free to the Engineers to do the drawings as they like, creating the drawings mainly in 2D drafting. What I'm looking for to get closer to "future vision", I'm trying to describe it here.If the Pre-condition is like:a Combination State N is activated  The behavior as desired:Per definition assigned Annotation Plane N becomes automatically activePer definition assigned Saved Orientation N becomes automatically activeThe assigned Annotation Plane (Plane or Face) should become visible and/or highlighted. If now a dimension is derived via "Show Annotation" or features are added as" text", "geometrical tolerances", "datum features", "datum targets", "surface symbols" or any "symbol" is inserted or if any Annotation is "Assigned to State" it should automatically get the (or let's say a), pre-set size (scale), oriented according the assigned "Saved Orientation" N, be placed on the assigned "Annotation Plane". Any Annotation assigned to Combination States with per definition assigned Annotation Plane and Saved Orientation should receive the definitions of "Plane" and "Orientation", unless a manually modification is done. If an Annotation is added by "Assign to State", the user shall be informed that the annotation is moved and no more available on the previously assigned state. In case the user needs to show a dimension on more time e.g. on an second Combination State he shall be forced to create it manually. 3. Are you using a workaround? If yes, please describe it.Doing all the work manually:each time first selecting the annotation plane, than selecting the Combination State, than derive dimension from features, moving them to a offset plane, applying them the Saved Orientation, sort the Annotations manually to get a proper layout.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.In first step:The drawing will remain the document which will be referenced to. It will be part of contracts (supplier or customer).The 3D views shall be internally used for viewers in the Windchill data base or ERP System and for people involved in the manufacturing process to avoid the opening of the 3D data in Creo. The printout of drawings shall be avoided.  In second step:The MBD shall be used for NC programming.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)We currently maintain about 30 creo licenses, some of them are globally.The effect affects all the defining work, to bring the MBD proper to the right annotation plane with a matching orientation and size of the text and symbols.In addition, I read many ideas or questions in this forum describing parts of this "future vision" so the effect might be multiplied many times.Finally, if the effort remains the same, such methods will not be accepted by the users and may have no chance to establish in the company(s) and MBD remains a future vision.

Creo Parametric support for Panzura CloudFS global file systemAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Parametric 7.0.10.0 using Panzura CloudFS global file system to access model content2. What is the problem?When using Panzura file system, new data and folders that are being created in Pazura are not immediately available in Creo Parametric File Open window.  Workaround to create a new folder to see the previous folder display is needed.  Seems Creo Parametric File/Open does not support the technology from Panzura to be able to use cloud file system to open data.3. Are you using a workaround? If yes, please describe it.When issue occurs, user currently has the following options:Manually type in the name of the new folder within Creo Parametric.Wait for the folder to become available; may need to select the Refresh button.Exit and Restart Creo Parametric.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.Panzura is a cloud file system management tool that allows metadata stored in cloud storage to be replicated across AWS s3 environments5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Creo Parametric usage with cloud solutions such as cloud compute for simulations are not able to be efficiently manages and automated.  Entire simulation organization at John Deere is asking for this to be supported by Creo Parametric to support Simulation process of Creo models using cloud storage to access and store reports.

Filter behavior improvement proposal while using GD&T AdvisorAcknowledged

1. What version of the software are you running?Creo 9.0.5.0GD&T Advisor 6.2.2.30 2. What is the problem?This is an improvement proposal for GD&T Advisor.To improve user experience, and to better select annotations (after tolerance features are created) the selection should automatically switch to "Annotations" and not to "Geometry" or "Surface".• Already existing behavior: Starting creating tolerance feature, it switches to “Surface” (this is correct).• Missing behavior: After creating a tolerance feature, it should be switched to “Annotation”.This is currently not the case. Annotations that are placed in front of the model cannot be selected. It is necessary to set the selection filter to "Annotations" manually each time. 3. Are you using a workaround? If yes, please describe it.No workaround available. 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.Standard designer's work, modifying and validating dimensions using GD&T Advisor. 5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Having to switch to “Annotations” every time, causes users to lose a small amount of time every day. With approximately 5000 users however, that lost time sums up to significant amount of worktime, causing company to waste money in effect.   

Creo View ECAD Cross-Probing should work when a component is an assembly and a subpart is selected.Acknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo View 10.0 2. What is the problem?Reference: Ticket: 16990778   Creo View ECAD allows cross-probing between the 3d model, schematic, 2d pcb drawings, etc. See https://youtu.be/ocWmVC4RnuY?si=ScnAWhVHPOhWyHh7 as a reference. This is great. However, the tool is under the assumption that every 3d component is modeled as a part. This is just not the case. In fact, over 90% of our components are modeled as assemblies, so we can manage different AML/AVL sourcing geometry within the component. Now, if a user selects a part from this assembly in the graphics window, cross-probing won't work. It needs to be selected from the model tree instead. However, the average user doesn't realize this limitation and believes there is an issue and the tool doesn't work. Some believe we shouldn't even use the tool if it can't do what it advertises with the cross-probing. Please allow cross-probing when a subpart of a component is selected. The part belongs to the component, so it should cross-probe to the same component in the schematic, 2d pcb drawing. etc.3. Are you using a workaround? If yes, please describe it.Selecting the component (assembly) from the model tree. However, most users don't know this workaround.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.A user selects a part from the graphics window. Creo View ECAD understands that this part belongs to an assembly that is a component. It would then cross-probe to the necessary components in the layout, schematic, 2D, etc.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Could impact a couple hundreds users. It is giving the impression that cross-probing doesn't work and some users don't feel the tool is doing what was advertised and they don't think it has value if it doesn't work.