Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Creo 4.0 M010 - Make Extrude to Surface, then Offset available in SheetMetalArchived

Hi Everyone,I have been doing some testing on Creo 4.0 M010 this week, and really find that the Extrude to Surface, then Offset to be a very nice functionality that has been added (great job PTC).  We design many extruded parts that are typically extruded to a common plane, then depending on the usage, can have material added past that plane, or have material removed from that datum plane, and this is EXACTLY what we needed to accomplish this without using end cuts or having to use a Blind dimension instead of using the datum plane reference.  Again, for extruded parts, this is incredible.That said, we have many of our products designed in SheetMetal, and at times, we replace extruded parts with formed SheetMetal parts, and design similarly.  So after I had seen this functionality within Solid Part mode, I also wanted to see whether this worked in SheetMetal mode.  The basic end extrude is the same setup as solid mode, and if you are extruding a surface, this acts the exact same way as solid mode.  Now, once you toggle this over to be thickened (as you would expect to do in sheet metal parts), the offset option when extruding to surface is removed.  See attached images and below screenshots.Is there a reason that this would be removed from SheetMetal?  Or is this simply a bug?  Seems to me that it should be available, and we would really make great use of this functionality if it were also available in SheetMetal.I also captured the attached video if it helps explain and demonstrate a little more clearly.I submitted this as ticket C13693486 on PTC Support site, and they said that this would be added functionality on a future rollout of Creo Parametric, and recommended that I add this as a Product Idea.

Faster component highlighting method (Global Interference results)Archived

The current method of highlighting components by drawing the wireframe works well for small, simple parts but scales very poorly, and rapidly becomes extremely slow for larger parts, such as a cast gearbox casing for example.Perhaps it's time to throw away the existing highlighting method (which seems to be entirely CPU-bound) and look for a faster, more efficient routine, maybe using the GPU?A good use case is looking through the results of a Global Interference analysis.  If the pair of components highlighted is, say, a nut and a bolt (where the thread volumes overlap) I can spin and manipulate the entire assembly easily and smoothly (5-10 fps, I estimate) to identify the location of the interference.  If one of the components is the main gearbox casing, however, it can takes 6-10 seconds per redraw!  It also seems to deal badly with a highlighted component extending outside the viewable area - this seems to slow it down more as you zoom in.My system has a reasonably recent Xeon CPU with good single-thread performance, and a respectable NVidia Quadro graphics card - it should be more usable than this.I've just checked with our test installation of Creo 4 (normally using Creo 3) and this is still no better, specifically in Global Interference.  In both versions though, preselection highlighting and 'normal' selection highlighting is much faster...

Make the Creo Parametric Merge feature work like components in an assembly.Archived

Currently the Creo Parametric Merge (external Merge and Merge/Inheritance) feature is not fully compatible with Windchill/PDMLink (WC).  Please make it work correctly inside PDMLink.Like an assembly, a merge features reference other components.  However, unlike an assembly if these components are updated, Creo shows them as un-regenerated BECAUSE PDMLink locks the object containing the merge and doesn't allow it to show the latest.  There are some config options that attempt to address this but after extensive testing and Calls with PTC they do not work (or are inconsistent).This is NOT a Creo issue, because if you go offline (outside of WC), everything works perfectly because the object containing the merge is not locked.  It is the fact that apparently WC currently does not recognize when the merge feature is used and pulling in references from other models and therefore does not take the latest version, or if it does then it shows regeneration errors.  Windchill does not currently know which versions to pull into the WS and how to regenerate.  WC prevents objects from being modified or checked out if they are at a released state, so in order to fix this regeneration error there is a significant amount of work (WC and emailing back and forth) for the user and the admin to fix it without having to do a Change Notice (which would be worse).  E.g.User finds problem and emails the P/N and reason to change to the Admin who sets state from Production Released to in workAdmin searches in PDMLink finds object and sets state.  Admin emails user backUser regenerates and checks in.User creates Promo Req. with a description of what they didUser emails Promo Req name back to admin using the same email string.Admin reviews objects on Promo Req and the comments, then forwards email to the official WC approver.Approver receives email, Reviews and approves promo req and emails notification back to Admin.This is a whole lot of clicks, searches, and typing.  This happens every time a component which uses a Merge feature (whose base had been regenerated) is used in an assembly. Why don't we just update all the objects which contain a Merge reference in it when the base component is changed?  We do when the change is significant but most changes are not significant from a model perspective (could have been a drawing only change) and don't require where they are use to be updated.  Because of high Part Reuse this explodes very quickly from a maintenance perspective. Imagine if WC was not compatible with assemblies in the same way and every time you updated a component you had to change all the assemblies where that component is used in!  It would not be a usable system.  For Assemblies WC gives us the option when adding to the Workspace (WS) to add as stored, latest, Promo Req, etc and we can even set one of these as a system default.  Merges need to work in a similar way to be compatible with WC!Alternative options to merge features were previously discussed in the very long thread, but it really comes down to Creo Parametric not being fully supported.Regeneration errors in Merged Parts/Assemblies?I understand that the best place for this may not be in the Product Ideas section, but I really don't know where else to put it.  It really just needs to be fixed.  I did try putting this in the Windchill CAD Integration Product Idea but evidently there is no product idea area for it.