Ptc Creo Version
Jarrell Campbell
PTC is proud to announce Creo 11, the latest version of our award-winning, powerful, yet easy-to-use CAD system. Creo helps you deliver your best designs in less time, with a wide range of enhancements for electrification, composites, model-based definition, simulation-driven design, and advanced manufacturing.
Creo simplifies your workflows and provides an unbroken chain of design, with no export/import needed. So, when your design requirements change, you can easily update your model to reflect the new conditions.
Updated Creo functionality includes innovative CAD tools for designing composites, conducting real-time simulation, and streamlining manufacturing. Creo also continues to expand electrification and model-based definition capabilities.
Design engineers are finding applications of composite materials in more products than ever, and Creo 11 continues to expand composites design, simulation, and manufacturing capabilities. Creo has expanded functionality for transitions, laminate sections, and draping simulations. You can even use zone-based design to define and automatically build plies from zones. Manufacturing has been enhanced with extended ply boundaries, core sampling and the ability to export to leading laser projection systems.
Creo now gives you even more powerful model-based definition tools to provide greater clarity with less effort. Now you can easily organize your design data in simple tables that can be read by humans and machines, with both user-defined text, parameter callouts, and semantic references.
Creating MBD annotations for cylindrical features is quicker, and semantic query is now available for inheritance models. GD&T Advisor has been updated to support ISO 22081 standard for general tolerances, for combined simplified hole callouts and enriched definition for slab and slot features.
As always, Creo has improvements for both additive and subtractive manufacturing. For additive manufacturing, you can now connect two or more lattices with different cell types on a single continuous lattice structure and adjust pore size control for stochastic lattices. In addition, Creo has also expanded 3MF STL export options.
Creo+ has cloud-based desktop tools for license management, deployment, and telemetry services, now including engineering notebook. You can even monitor and provide feedback on network connectivity. There are also usability enhancements for defining shortcuts and launching Creo+.
I'm wondering what folks have found to be the most stable release between 5.0, 6.0, and 7.0. I'm not really that interested in multibody functionality - I see that as another way for horrible model management to expand to heretofore unseen levels of disorganization. I'm more interested in whether a particular "version" is more stable, has less bugs, maybe handles the tedium of drawing generation better, etc. Maybe Simulate is better in one version than another?
Given that you indicated you want a supported release I would suggest 7.0.3 which is the latest build that just came out. It will have the most bug fixes out of anything. Our organization is upgrading to that release this week.
I put "support" in quotes because to be honest, it's never been much of a concern. Even when I've found and reported bad behavior I'm told it "functions according to specification". A release being supported just means there will be periodic new builds provided that we can download if desired.
What I' really interested in is the day to day usage. For example, when we moved from Creo 2.0 to Creo 4.0, we found that the methodology necessary to do drawings became much more tedious. Every time an older drawing is brought up, if it uses datums, we get this annoying "warning" about legacy data. Which is a real pain to "correct". But mainly the workflow needed to do the same things we used to increased, in terms of the massive number of mouse clicks and menu perusals.
On a lesser level, is the Manufacturing module improved significantly in any of the later releases? I'm actually quite afraid that they will eliminate the Custom Trajectory path type, which I use immensely for roughing operations and particularly tricky finishing, too. The "canned" cycles are okay if you just want to chop out a volume and don't particularly care how it's done, but for efficiency on complex 3D contours I can define paths that give better results and are faster.
We are making the jump from 4 to 7. PTC spent a lot of R&D on the multibody thing and only minor improvements on other things. From an admin point of view this is great because very few of the mapkeys got broken and there isn't a lot of new code that could introduce new errors. If you stay away from mutibody then 7 is very similar to 4.
The last part of that statement is actually not correct. PTC released a statement yesterday that said Creo 8.0 and following will all be supported for 4 years. It seems like the concept of 'enterprise release' is going away.
These changes do not affect any current releases of Creo.
Visit eSupport here to learn more about the Creo support changes and who you can contact if you have any specific questions.
Thank you,
PTC Customer Success
I am having Creo 4.0 M030. I would like to know version of CAD file opened in Creo. For example, I have opened a.prt.2 into Creo, how can I come to know that it's 2 version file opened in Creo? On Creo title menu, it just displays a.prt.
Note : Please do not get confuse with config option "save_file_iteration". This is to decide whether to create new version on each save or not for part file. What I need is to know version (.31 or .32 for example ) for an opened part file in Creo.
I am wondering why this version (.32 or .33) is not displayed on Creo title bar as abc.prt.32 ? It shows only as abc omitting extension (.prt) and version (.32) details... Earlier I have seen title of Creo model window showing abc.prt.32. Am I missing some config option or setting for this?
Some other causes are Windows system setting for hiding file extensions of known types, not saving file iterations (config option), manually removing the iteration number, and working in Windchill session.
Creo+ is Creo at its core, with additional collaboration functionality along with branching/merging and other features. It is a superset of the functionality that Creo offers, not a partial subset. So, by definition, it is compatible with Creo design files, Windchill, and all the other products a Creo customer might use in their ecosystem.
The way this is accomplished is by using a SaaS enabling technology platform called Atlas, which is derived from Onshape technology. Indeed, Atlas is the foundation to several of the "Plus" products that have been launched in the past years such as Vuforia Expert Capture, Creo Generative Design Extension (GDX), and now Creo+. More here: -transformation
Onshape, as everyone in this forum is aware, is (and has been from day 1) a cloud-native CAD system with integrated PDM. One may even argue Onshape is a cloud-native PDM system with built-in CAD... So all the benefits that come with Onshape - no files, seamless and secure sharing, versioning, branching/merging, task management, real-time collaboration, no data loss, automatic updates (every 3 weeks!), no installs, no drivers etc. continue to exist.
There will always be overlap between the products, just like you can extrude and fillet in Creo and you can extrude and fillet in Onshape as well. And now some of the additional Onshape features have made their way over into Creo+. Onshape similarly has benefited by other Creo/PTC technology - for example the built-in Simulation and Generative Design (see post by PTC CEO Jim Heppelmann here: -23).
I am very impressed with how PTC has evolved over the past 25 years. Your company's breadth of services surpasses just the design phase, and it is mind-boggling to try to take it all in. I enjoyed LiveWorx.
I am a fan of the cloud and have been programming in it for some time. I was shocked to learn that these guy were going to bring us the first cloud-based CAD software, and I was even more surprised when I was allowed to be involved in the very beginning. The team did a great job.
I still think that the cloud has a ways to go. Why aren't vendors supplying geometry in Onshape? They could publish it for the price of a license. Why do I have to build assemblies that work? Step has to go, it's a terrible solid model translator. Give me native assemblies containing all the metadata so that my BOMs are correct. Vendors should want to do this because they could see that 500 linear motors are currently in engineering designs around the world. What a great forecasting tool, why isn't it happening? Collaboration is more than two engineers moving holes around on a plate.
This seems to be a tired topic from my searches, but I'm getting desperate. I've opened a case with PTC support, and reached out to an account support rep, but I'm still not getting a clear answer. Here's the use case:
If I modify -.35 in Creo to remove the reference to the child, then -.36 will get created, Sure, now I can purge/delete -.35, but now I've just kicked the can down the road as I have the same situation, just now with -.36.
Windchill will not allow you under any scenario to delete the latest version (revision.iteration) of an object when there is a newer revision in the system. Your ONLY choice is to delete all iterations of Rev A, which will also delete revision A in total. Then you can modify the version -.35 of the drawing, remove your rogue part, check it in and then revise to revision A again.
It has always been coded that once an object is referenced by another object in Windchill, the only way to delete things is to delete ALL references that an object has. With a drawing of an assembly, it becomes a bit more complicated. You have to delete the drawings first, then the assemblies to get to that one part created and added to an assembly. When all objects that the rogue object reference have been deleted, the rogue object itself can be deleted. If you use promotion request or change requests/notices, these also must be deleted as they will hold a reference to that 1 rogue object.
c80f0f1006