Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Creo View Doesn't "Do What It Says On The Tin" : Family Table Instance Can't Be ViewedAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders. We work in the scale model / toy industry. Our products range from high-detailed models to children’s toys which are sold worldwide across our brands. Our designers use Creo Parametric to develop products with a range of variations.   We aim to design as many variations as possible to enable us to manufacture as many versions of each product as possible – as a designer, the Family Table tool in Creo is essential to allow us to design parts with these variations: Parts are linked so changes to generic will update instances. Variant parts can easily be added to the Family Table if required. Key features can be designed once, then turned “on” or “off” as necessary. Family Table parts easily interchange them in assemblies as references are preserved. This design process has worked for many years, but a failure for Creo View to accommodate this standard Creo feature threatens to slow our efficiency and adopt a slower, more convoluted method of design which will adversely impact product release dates. 2. What product and version are you currently running?   Creo Parametric 8.0.4.0 , Creo View Express 8.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.   Creo View is used by members of our team without full licenses (managers, manufacturing / production, graphics, QC) to view the CAD of products. The issue with Creo View is that instance parts (parts created via Family Table) cannot be viewed – the generic part opens rather than the correct instance. However, in an assembly, the correct instance is shown.    Creo View cannot handle family tables which are a fundamental tool in Creo, and is therefore not fit for purpose in its current form.   To allow our Creo View users to see the correct data, we have to export the files as a STEP so it can be opened in another software.   Alternatively, we stop using Family Tables. This would require an alternative way of designing which will be more time-consuming and less efficient. Although this would fix the viewing issue going forward, it would still not allow products from the past 20 years to be viewed correctly. 4. What is the use case for your organization?   Making Creo View usable allows the company to use PTC products and not rely on other software to complete a task that should be achievable. 5. What business value would your suggestion represent for your organization? Creo View must have the functionality to correctly view Family Table instances. The alternatives are to export from Creo and open files in another programme or change the design process to not use Family Tables – both are time consuming and reduce efficiency.   Family tables have been a main feature of Creo going right back to its inception and the fact that Creo View does not let you view instances it incredulous.

Importing an EMN file can easily cause references and child of components to fail! Please fix!Acknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We design and manufacture high-end electronics. I am the CAD Manager / PTC SME. Stakeholders for this idea include our Creo user community. 2. What version of Creo Parametric are you currently running?8.0.8.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.Reference: Article: 387085Ticket: 16762640 SPR: 14468880   When collaborating with our ECAD team, we transfer EMN files back and forth. If we import an EMN file that suggests a slight movement for a component, it will be flagged as a placement change. Even if the user says to 'keep' the placement that was there before, Creo goes through an operation of removing the old component and placing it anew in the old location. By doing this, all references and children fail. This has drastic repercussions including connector cutouts in our chassis' are failing. If the user selects 'Keep',  Creo should not move or alter the component at all. It seems pretty obvious to us.    4. What is the use case for your organization?See above. This happens often as we are trying to build up our ECAD collaboration processes.5. What business value would your suggestion represent for your organization?Right now, users can either use the collaboration tool, and waste a lot of time fixing failures after an import OR not use ECAD collaboration and spend a lot of time manually checking changes. Either way, there is a lot of time wasted and a lot of negative energy regarding this functionality.   @Alex_Y 

Creo Toolkit Notification just before switching windowsAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.Industry: Tolerance AnalysisRole: DeveloperStakeholders: Anyone performing a tolerance analysis2. What version of Creo Parametric are you currently running?9.0.0.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.Our application puts Creo into new temporary states (e.g. temporarily moves the position of parts, etc). We need to know when the user switches models, enters new states, etc so we can revert our changes. We are using Creo events to detect this. The one event that is missing that we really need is PRO_WINDOW_CHANGE_PRE (currently only PRO_WINDOW_CHANGE_POST exists).4. What is the use case for your organization?Step 1: User loads model 1Step 2: User loads model 2Step 3: User uses our software to move parts in model 2 into temporary positionStep 4: User switches windows back to model 1 Expected: Model 2 reverts to its original state Actual: Model 2 stays in its temporary position. There is no way to detect the window change event before it happens. Why it's a problem: This can cause major issues if Model 1 is a part contained in assembly Model 2, which means the user can modify it and throw off the state of our software. We really need to reset everything when the user switches models to prevent this.5. What business value would your suggestion represent for your organization?Our application, as well as any other application using Creo Toolkit, would be aware of when the user switches model windows before it happens. This allows them to revert states, clear caches, or anything else needed to prevent issues from occurring.