If you have the luxury of two monitors, and wish to dedicate the full size of your monitor to the graphics window, enabling your model tree to "Float" may be right up your alley.

If you find this grayed out "Display as separate window" check box as frustrating as I did; you will be pleased to hear this simple solution.

This check box is only available to toggle when you have closed all windows except the base window.

When preparing to go from ProE WF4 to Creo 3 a PTC rep said that there were hundreds (I think he said over 400) enhancements going from WF4 to Creo 2 'while no features have been removed' (paraphrased).  For those who are using Creo2, we all know that is simply not true.

Purpose of this Document is to provide a one-stop-place to get the following

1. Make information available to others so they can account for specific losses in functionality
2. Give sanity to people who have been looking in vain for features that have been removed,
3. Perhaps people know workarounds, or simply new ways to do the same thing that they can share.
4. Increase awareness with PTC that they will bring back features that perhaps were overlooked during the upgrade.

Anyone has permission to modify this document.  Please Add/modify/or cross out anything below this line and discuss everything else below the thread:

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Functionality Removed:

1. Tabs for open objects
   1. Tabs for open objects in Creo (like was in ProE)
   2. Use Tabs for open models/drawings in Creo (like in ProE, IE, Firefox, Chrome, FoxIt pdf viewer, etc)?
      .
2. Show Erase Model Annotations
   • You can show only model annotations that have been DELETED
     • "Delete" deletes any/all reference to dwg:
       • Dwg dimensions/notes are permanently deleted
       • Model dims/notes lose any reference to the dwg (like locations, leaders, jogs/breaks, etc)
     • "Erase" Only hides from view, just like in WF, however now only viewable through the dwg tree, and hidden from the show model annotations dialog.
   • You cannot show model dimensions that have been ERASED.
   • The erased dimensions get buried in the dwg tree forcing the user to go through the model tree to verify (one-by-one) all necessary dims are shown rather than just use the show/erase dialog as it was in ProE WF.  This adds much confusion by spreading out information while also adding many extra steps (how many extra steps depends on the number of dimensions/notes/datums on a drawing).
   • Add a Search for Drawing Dimensions
     .
3. Simultaneously Adjust the length of Multiple Leader lines for Multiple Dimensions on a single view
   • In WF if you select a view and then hold down ctrl and select dimensions and leader lines you could simultaneously align all of them to the same location. 
   • This facilitated a fast and clean way to align leader length ending point locations (E.g. As for a view boundary).
   • Now there seems to be no way to align more than one leader end at any given time.
     .
4. Automatic selection filter using the Find dialog (especially while assembling components)
   • When Assembling components in ProE, the user could select an axis (or plane, etc), open the find window and ProE would automatically be on Axis.  Now Creo remembers the last choice regardless if you already selected axis and it is looking for an axis.  The same worked for Planes, points, etc
   • This was an incredibly fast, accurate, and intelligent way to assemble components, especially when the company uses standard datum features and orientations.
   • Now it only works the first time you do it and then it prioritizes the last choice above what Creo is looking for in the feature/component definition, thus requiring the user to click several times to change it to what ProE used to automatically (which mitigates a lot of the speed and reduced clicks of assembling using this method).
5. ?

.

.

.

.

---------

Although available through customizing the ribbon or using the new command search, the following features have been removed from the default UI, giving concern to some that PTC is contemplating removing the features altogether.  PTC, the following features are still used and appreciated:

1. The Pipe Feature (used to be #Insert #Advanced #Pipe in WF5)
2. Open Systems Window (I use this to run a purge on my working dir)

Modelingのユーティリティグループ > Anno作成で作成した寸法や、

Mold Design>モールド集合体>プラスチック集合体で作成したモデルの寸法や、

PartLibraryのパラメトリックパーツに登録してある寸法を、モデルに属性として付加させたい。

例えば、ギヤなどの諸元表がある部品。

I downloaded the creo 2.0 stuTdent edition and I installed it, but when I try to open the "Thermal" and the "Structure", there is a problem of "unknown licensing error 26",and if I click "OK", it wil be closed. How can I solve that problem? Please!!!

There is a new config option is available:

show_axes_by_view_scope

With that option selecting axes in the datum tab of the "Show Model Annotiations" dialog (see below) can be configured to show only the axes of the top model, not all the axes of the e.g. 50000 submodels.

• all_sub_models (the default value)
  • All axes of all submodels are shown which is slow for comprehensive models
  • This is the default behavior in the datum tab in the Show Model Annotation dialog and leads to not responding sessions
  • Example of time consuming display of a lot of axes with that config setting:
    
    
    
    
• top_model_only
  • Only the axes of the top model are shown (which is fast)
  • This setting prevents not responding sessions on large drawings

This implements the idea 1314 with the solution suggestion "Idea A" described here:

Keep Creo Elements/Pro responsive when "Show Model Annotiations" for all datum features is selected on a comprehensive drawing view

There is still Idea B to improve the performance keeping the actual default behaviour:

Implement a stop button, to cancel that action if Creo Elements/Pro does not respond in that situation. Try to use the existing stop button which can be used e.g. during model retrieval.

Tested with Creo Elements/Pro 5.0 M230

If you want to get overall dimensions automaticly into your drawing tables here is a way to do it.

You can make relations in part template or assembly template that will handle asigned dimensions and convert them into parameter that drawing table raports. Any changes on those part dimensions with regen will reflect in raported parameter.

Attention:You will need to update your browsers Flash Player plugin to see videos on this site.

Update your Flash Player here. Its free and fast.

Ever have windows that are always in the way or hide? The following AutoIt program is a basis for creating a custom solution to your problem. You can start it up and leave it running while using Pro/E or Creo or any other programs you like. It isn't very smart, but it doesn't do very much, except be convenient.

It has three functions, based on window name: Move a window to a certain spot, ask the window to close, and activate the window (which should bring it out of hiding)

It has a variable, $delay, that sets how fast it runs through a list you create of window titles. By default it is once per second.

It has the ability to select whether you mean windows with a specific name or those based on a partial name

It can either just do the action once for each time you run the winmover program or to keep at it

I think it is commented well enough; others may differ on that, so ask questions if you like.

ConsoleWrite is a diagnostic. Those lines can be taken out if you don't need them, but leave them in to see how it works. Comment them if there's a chance of needing them in the future.

The ";", semicolon, is a comment introducer. From there to the end of the line is a comment.

AutoIT is a zero-based array language. Dimension an array with 3 elements and they are numbered 0, 1, and 2.

Note that there can be many windows that meet a poor match choice. It's best not to use the window-close function until you have some practice doing this, particularly when using 'repeat'.

To test it, copy and run it from AutoIt or open the attached file**. Then open Notepad; it should move the window a bit. Then save the Notepad file as winmover_test.txt. The program should close it.

** The attached file can be edited with Notepad. The AU3 suffix tells the AutoIt customized SciTE editor the file type.

If you hammer on this program hard enough, there's a chance it will fail trying to move or close a window that you manage to close first. It does check to see if the window exists at the start of the loop, but if the program is slower than you are, you could beat it. Nothing bad happens. AutoIT will stop the program and give an error message. The program could be three or four times longer to make it more bullet-resistant. Do not use it where loss of life is a concern. Do not base your business on it. It is provided as-is for amusement and educational purposes. Do not attempt high-wire acts involving rabid wild animals or fire.

******************************Start of program, does not include this line***********************************

;Takes a list of window names

;and matching list of coordinates and options

;and waits for windows

$delay = 1000 ;the amount of time to wait for the next sweep

$entries = 3

$winactive = 1 ;flag in win_select_opts to indicate option applies only when active

$i = 0

dim $win_names[$entries]

dim $win_select_opts[$entries][3]

;first opt is title match -exact names or partial, always, or only active?

;second is if it applies only when active

;third is action: 1 = move, 2 = close, 3 = bring to front

dim $win_coords[$entries][2] ; X, Y

dim $win_repeat[$entries] ; Should the window action repeat?

dim $win_done[$entries] ; if true and win_repeat is false, then don't do it again.

;If you want to write a file open/close/validate interface, then go ahead

;Otherwise you'll just have to enter all the data here.

;Besides, you should know what the code does before you use it.

$entry = 0

$win_names[$entry] = "winmover_test.txt - Notepad"

$win_select_opts[$entry][0] = 3; match entire title

$win_select_opts[$entry][1] = $winactive; when active

$win_select_opts[$entry][2] = 2; close the window

$win_coords[$entry][0] = 300

$win_coords[$entry][1] = 500

$win_repeat[$entry] = True

$win_done[$entry] = False

$entry = 1

$win_names[$entry] = "winmover_test.txt - Notepad"

$win_select_opts[$entry][0] = 3; match entire title

$win_select_opts[$entry][1] = 0; active or not active

$win_select_opts[$entry][2] = 1; move the window

$win_coords[$entry][0] = 300

$win_coords[$entry][1] = 500

$win_repeat[$entry] = False

$win_done[$entry] = False

$entry = 2

$win_names[$entry] = "Notepad"

$win_select_opts[$entry][0] = 2; match part of the title

$win_select_opts[$entry][1] = 0; active or not active

$win_select_opts[$entry][2] = 1; move the window

$win_coords[$entry][0] = 300

$win_coords[$entry][1] = 100

$win_repeat[$entry] = true

$win_done[$entry] = False

while 1=1

    for $i = 0 to $entries-1

        Opt("WinTitleMatchMode", $win_select_opts[$i][0])

        ;See help for more advanced match type 4

        ;1 = Match the title from the start (default)

        ;2 = Match any substring in the title

        ;3 = Exact title match

ConsoleWrite($win_names[$i]&@crlf)

        if (false = $win_repeat[$i] and true = $win_done[$i]) then

            ;this action is not supposed to repeat, and have already done this once.

ConsoleWrite("Skipped"&@crlf)

            ContinueLoop

        EndIf

        if WinExists($win_names[$i]) then

ConsoleWrite("Found it " & $i &" "&WinGetTitle($win_names[$i]) &@crlf)

            if $win_select_opts[$i][1] = $winactive Then ; only if the window is active

                if WinActive($win_names[$i]) Then

Consolewrite("It must be active and is"&@crlf)

                    Select

                        case 1 = $win_select_opts[$i][2] ; Move the window

                            WinMove($win_names[$i],"",$win_coords[$i][0],$win_coords[$i][1])

                        case 2 = $win_select_opts[$i][2] ; Close the window

                            WinClose($win_names[$i])

                        case 3 = $win_select_opts[$i][2] ;Bring window to front

                            WinActivate($win_names[$i])

                    endselect

                endif

            else ;don't care if window is active

Consolewrite("It's not active"&@crlf)

                Select

                    case 1 = $win_select_opts[$i][2] ; Move the window

                        WinMove($win_names[$i],"",$win_coords[$i][0],$win_coords[$i][1])

ConsoleWrite("Tried to move the window"&@crlf)

                    case 2 = $win_select_opts[$i][2] ; Close the window

                        WinClose($win_names[$i])

                    case 3 = $win_select_opts[$i][2] ;Bring window to front

                        WinActivate($win_names[$i])

                endselect

            endif

            if (false = $win_repeat[$i]) then

                $win_done[$i] = true

            EndIf

        endif

    Next

    sleep($delay)

wend

I want make the 2d dimension show as below, how to set up the config file let the basic dimension like this?

Have you ever need a larger population of manikins for a scene?

I downloaded DAZ Studio 4.7 Pro Beta which is free at the moment.

It is very much like Poser and has some very sophisticated capabilities for a free offering.

Of course, a lot of it is a teaser, but what you get is fully functional.

What I found useful is the ability to make some pretty realistic manikins with expressions and gestures with a relatively intelligent interface. 

You can pose them and morph them; dress them and manage them in countless ways.

And the great thing is, you can export them to an object file format and control how it scales and how how many features it creates in an intelligent manner!

Once you bring this into Creo, you have to save out each facet feature you want to assign a different color to.  You re-assemble your object in an assembly all using the default origin.  Now you have a color assigned to what DAZ 3D considers unique surfaces.

No texture mapping or color assignments come across in .obj files... and Creo won't let you do anything with facet files other than assign an overall color

But, you can open the file, be it a person or a full scene, and you can save out many copies to be re-assembled.  I included the child's head as a sample.

I included the model as it came in from the .obj format (childs_head.prt) and I turned off the cornea (needs to be translucent).

You can save this model as a .wrl (VRML) file and your new color assignment will remain, even if you import this as a new .prt file.  Unfortunately, transparency won't and that is why the cornea is hidden.

Anyway, if you've been searching for a nice manikin generation tool, this might not be th eonly one, but it is an option and for now, it's free.

If you have another candidate tool to do this or some tips for preserving colors, or even texture maps with the import, that would be excellent!

Kann mir jemand helfen?

Ich habe PTC Creo 3.0 auf meinem Computer installiert. Eine englische Version aber ich brauche deutsche.

Wie kann ich denn bitte die Sprache von Englisch auf Deutsch umstellen? Oder muss ich schon während der Installation Deutsche wählen?

I just wanted to post a a little helper file for creating internal and external threads based on the Unified Thread Standard (UTS) which covers both English and Metric.

I must give high kudos' to Wikipedia.  I borrowed their images and tables for the attached Creo 2.0 full version parametric file.  You will also find a linked link in the site if you turn on annotation.

See the relations to drive the pitch and diameter you are interested in.  The file is set up for English but you can change it to metric units, if that is your primary usage.  Most everything that can be driven by relations has been.  Only 3 variables are needed... and TPI (thread per inch) is set to zero if you want to define the pitch directly for metric threads.  See the "IF" statement in Relations.

I did have some troubles along the way.  I split up the helical sweep because it -did- fail if I did it in one go although it did not overlap anywhere.  This was customer support's "works as expected" Pro|WorkAround© for helical sweeps that fail otherwise.  This made the file more robust for changing threads on the fly through relations.

Of course, I suggest you make a library part of the two sketches in the file and use them liberally.  Otherwise, the file is a nice quick reference for many thread features.  And if you link into Wikipedia, you will find even more excellent information about this standard.

http://en.wikipedia.org/wiki/Unified_Thread_Standard

http://en.wikipedia.org/wiki/ISO_metric_screw_thread

Here are some of the highlight images from the file... turn off planes and CS' and turn on Annotation, Axes, and Points. 

The images should be saved in the file so no external reference issues should exist.

These are the actual "thread cutters"...

This is the structure of the file...

And I love intelligent parametric sketches...  yes, I have the rounding turned off on purpose.

If you find a serious bug, let me know.  Otherwise, enjoy!

Since Creo Parametric comes by default without fastener or standard parts library most of us had to download/make those by our self. Major problem is that you have to download different part for different standard and size so in the end you end up with huge pile of files. And every time you start new assembly you have to add those parts in given folder or use link to library via search.pro/config.pro. Last few years I`ve made lets say "compressed" fastener library made up of only 3 files/parts. Basicly you have screw,nut and washer part and each one is actualy one big family of parts.

So now you can just copy these 3 in working folder and you are done.

Supported standards and dimensions of fasteners are given in PDF file.

All fasteners are given with cosmetic thread by default but real thread can be turned on by unsuppresing "NAVOJ"(Bolt) or "FIZICKI NAVOJ"(Nut) in model tree.

Unfortunately I was too lazy to translate features or parameters from Serbian to English but then again I would have to do it every time I update these parts and enlarge family tables. Also versions of these fasteners I use myself have more standards(Luftnormen for example) in them  but i can`t give those.

Hope you find these usefull...

More standards have been added and some corrections of mistakes found in prior version.

6.7.2014 Update

I enlarged library last time for Creo 2.0 version. On 3.0 fasteners come by default so its a bit redundant except for maybe illustrations because of 3D thread.

4.8.2014 Update

Countersink bolts/screws had incorrect lenghts - corrected now. Placement interface works now for CS bolts and normal ones fine.

17.12.2014 Update

Corrected lenght for DIN97.

Hello everyone!

I am beginner hear so pleas be patient with me.

I would like to have set defaulty bend radius taken from my bend table. In previous ProE it was BY PARAMETER. In Creo2.0 option does not appear.

Pleas help!

Hallo!

I have to change my formats in to new version.

What is the quickest way to change it in all my old drawings? Now I have to open each one and change format.

Is there better way?

It will give you a more accurate insight into my ranting if I prologue this with the fact that Pro/E-Creo Parametric is the only PTC product I am addressing in this writing.  I don’t use Windchill or any other data management program with Pro/E-Creo.

I have used Pro/E since the early 90’s.  At the time it was so far ahead of AutoCad that there was no comparison.  Suddenly I was able to model and update drawings for pressure vessels and structures, calculate minimum thicknesses, accurately detail and dynamically (“parametrically”) represent geometry.  The amount of fabrication time and errors this saved is almost immeasurable.  For years, I found the challenge of fulfilling client’s design challenges easier with Pro/E than with anything else available in the CAD market.  I have even obtained patent’s based on designs with 3D geometry developed in Pro/E that (at the time) no other modeling program was capable of (except by archaic triangulation methods that were not as accurate as they needed to be).

As challenges increased (as they inevitably do) I was always running into limitations.  But I could always discuss issues with a US based knowledgeable PTC user/engineer and develop a process or number of steps to get to a workable solution.  This has changed.  This has been my first level of disillusionment  and my primary concern with PTC.  Although the Knowledge Base access and Help files have improved, other CAD providers have left Creo Parametric in the dust with their truly dynamic hint and usage pop-ups and windows, and complete and illustrative explanations of how to use each capability.

In college I took a class in Assembly Language Programming.  In terms of computer programs, I could eventually accomplish anything.  It was not intuitive, nor elegant, but it could always (one way or another) get the job done.  For years, Pro/E was the “Assembler Language Programming” of CAD… not intuitive, nor elegant, but it could always (with a little finesse) get the job done, and usually better than anything else.  Just as Assembler Language Programming has given way to many more intuitive and easier to implement methods of programming, Pro/E has been challenged by other more intuitive and (questionably ) capable CAD packages. The field of various 3D kernels (the 3D component underlying all CAD programs) has expanded and somewhat equalized, and each has their benefits (usually accuracy, methodology, and implementation)…and limitations (usually error recovery).  The real issue is the rate by which a design challenge can be met.  The real implementation of meeting that challenge is in the intuitive and efficient (efficient in this case means the clear knowledge of how accurate and appropriate the result is) interface of the user with the software.  If the software you are using does not have an intuitive, practical, efficient and useable interface…then you must customize it.

For as long as there have been computers with QWERTY keyboards for an interface, there has been an inherent limitation to interfacing with software.  The QWERTY key layout was supposedly developed specifically to slow down the typing process to account for the limitations in mechanical typewriters.  The Dvorak Simplified keyboard layout can potentially be much more efficient, quicker, and reduce strain.  Yet we are virtually stuck with the QWERTY keyboard – being supplied with every new computer.  Early word processors, spreadsheets, and CAD programs had various means (e.g. function keys F1-F12) of accessing menus (access to the series of steps needed to accomplish any given task).  Microsoft, as well as others, resorted to the “Ribbon” to provide a reasonable and more intuitive interface with word processing and spreadsheets.  For these programs, the Ribbon has served adequately…if not well.  It was inevitable that CAD programs would resort to the same attempt at an intuitive interface.  We are virtually stuck with the Ribbon interface, just like the arguably archaic QWERTY keyboard.

Well, you can customize your keyboard (if you really want to), and guess what, you can customize your interface with CAD software as well.  But doing this does not mean customizing (only) the Ribbon.  Macros bypass most of the need for Ribbons in CAD software.  In the case of Pro/E-Creo, the tool to do this is Mapkeys.  Getting proficient at creating Mapkeys is a skill, and is unfortunately underutilized by most.  My rule is…if I find myself doing the same series of steps 3 times each time I get into Creo…create a Mapkey.  Mapkeys are also the foundation of customizing the Ribbon.  For a series of steps I use once-in-a-while (assign a material, change number of decimal points, change between fractional and decimal dimensions, etc.) – create a button in the Ribbon to execute a Mapkey.  For a series of steps that I use frequently (view shaded, view hidden, etc.) – create a Mapkey for two or three button keyboard execution.  For those steps that I perform repeatedly (turn datum on or off, points on or off, change view orientation, save file, etc.) – create mapkeys that are triggered by a button on my multi-button mouse.  This is how you tap into the functionality of interfacing with your CAD software…and into real gains in productivity…by customizing the interface to be intuitive for YOU.

If you are going to complain about the Ribbon interface, and you have not really tried Mapkeys, you might as well go get a job that does not involve Pro/E-Creo.  You can complain about the trials of implementing mapkeys (and the lack of support for continuity of mapkeys between version upgrades).  But once you have properly incorporated Mapkeys into your routine use of Pro/E-Creo, the irritations of the Ribbon interface become inconsequential and not worth mentioning.

Yes…Mapkeys are the path to intuitive productivity in any version of Pro/E-Creo…but they are not without their quirks.  I have a list of over 100 Mapkeys .  I had occasion years ago to attend a presentation by James Heppelmann – who stated at the time that the transition from Wildfire to Creo was designed to be seamless and trouble-free.  I wanted to stand up and tell him it wasn’t quite so.  I had just spent over two (unanticipated) weeks re-creating about half of the Mapkeys I had developed and used for the previous two years.  They had become ‘functionless” as a result of the changes in some of the Mapkey commands.  Seamless…and trouble-free…bull----!  But once I had re-created and edited my collection of mapkeys, productivity was in fact, even better than before.

The path to increased productivity is not always without its hurdles.  There was a similar hurdle in transitioning from Creo 1 to Creo 2.  Sometimes it is best to get into Pro/E-Creo, execute the steps you want in your Mapkey, then exit the program.  Locate and extract the desired steps from the trail file and edit them into a Mapkey.  Even a “normally” created Mapkey will often have unnecessary commands – which can be edited out to speed it up.  And why (in this world, in its current level of technology) would anyone put Mapkeys (macros) in the same file that now contains hundreds of configuration setting? – Here’s a legitimate item to add to the list of “MOST ANNOYING THINGS WITH CREO”

Mapkey implementation needs work, but regardless of the irritations – it’s worth it.  Once you embrace this approach, for the first few days you will create 1 to 5 macros a day, then 1 to 5 macros a month, then 1 to 5 macros a year.  If I spend a whole day on one Mapkey (creating, editing, testing, refining), if well implemented, it always reaps benefits in the time it saves in the future (at least till the next version upgrade).  You will usually use a few minutes each time you create a Mapkey that will save you accumulated weeks over-all.  There are a few series of steps that are difficult to Mapkey, and even a few that are impossible.  My approach has always been to assume that it can be done until I prove that it can’t (as opposed to assuming it’s just too difficult to try).

So as I read (almost every day) the entries in MOST ANNOYING THINGS WITH CREO concerning the Ribbon and some other dysfunctional areas of Pro/E-Creo, I always fight the urge to respond with “either go use the other software – or create yourself a Mapkey!”

3D modeling can be the backbone of any project.  I have never seen the failure of a project (a client design challenge) based on too much accurate 3D modeling.  I have witnessed many times, broken (and failed) projects, as a result of inadequate or inaccurate 3D modeling.  However, the necessity of 3D modeling is no longer limited to geometry.  Customize your start part and start assemblies with the parameters you know you will need (remember I’m not using Windchill).  Create parameters that have an origin date, revision and revision date, drawing note(s), etc., that you will use at any stage (design, refinement, detailing, identification, fabrication, destination, etc.).

The curve is less and less diverse in terms of ease and accuracy of 3D model geometry among the various CAD packages.  Now that the challenges of 3D geometry has seemingly been met, everyone is addressing the fact that they already knew…there is a lot more than geometry that needs to be incorporated into the model.  Thus the attention has shifted…from the geometry of the 3D model…to all the information that can be incorporated into, and extracted from it.  There have been databases since before the inception of the electronic computer.  Nowadays 3D models are what relate all that numerical data to the real world (until the 80’s it was either the scale model or prototype).  They are what eventually becomes tangible and physically functional.  Much has been created in recent years that could not before, because it has been able to imagined, and then created with a mathematical model inside the computer.

PTC was once the most powerful and capable (compared to anything else) 3D modeler (let alone parametric) available (it possibly still is – it just lacks a competitive innovative interface).  Now that there has been a shift towards managing all the related data (PTC’s Windchill wishes to be the best example) there seems to be less motivation to further develop a truly innovative and intuitive interface for 3D modeling, or even to address issues with the existing interface and capabilities.  The number of entries and subjects under just one discussion “MOST ANNOYING THINGS WITH CREO “ reveals this.

It used to be that our sales people would impress clients with the fact that we use Pro-Engineer (and not even mention that we also use Autocad, SolidWorks, and Tekla).  Now, SolidWorks is mentioned – mostly because everyone at least knows of it.  We seldom mention that we use Creo – because we have to further explain that Creo used to be Pro/E…and what was Pro/E? – compared to Solidworks?

For us die-hards… I will continue to use Creo, endure the taunts of SolidWorks users, continue to refine my Mapkeys, and resist the urge to respond to many “MOST ANNOYING THINGS WITH CREO “ entries with “either go use the other software – or create yourself a Mapkey!”.

I finally quit submitting anything to PTC’s “Product Ideas”.  What’s the point when it takes years for PTC to even indicate if it is something they will or will not consider…how long should one be hopeful, or finally know that you will always have to do a “workaround”.  I subscribe to PTC Technical Support Subscriptions.  It is often a source of hints, cures and techniques to deal with software quirks, and sometimes to find helpful but otherwise “hidden” config.pro options.   It has also become a discouragement that as a line item in some articles addressing submitted issues, under “Resolution” there is the entry “Kindly log an idea at Product Ideas @ PTC Community”.  Why would you log an idea if it takes over a year to know if it is ever going to be considered (let alone knowing if it is not going to be considered, or when it might be available if it is).

In the early years, PTC seemed anxious to jump on and implement any reasonable ideas – it kept them ahead of their competitors.  Now it seems more important to PTC to simply offer workarounds, and submitted “Product Ideas” must apparently win a popularity contest (rather than be considered on merits as a productivity enhancement or practical aid).

There are also some very legitimate issues brought up in “MOST ANNOYING THINGS WITH CREO “.  For these issues, and the many good points suggested under “Product Ideas” that have been there for years without any indication from PTC as to their possible dispositions, I pray that PTC will not completely lose touch with the foundation that enabled them the opportunity for their clients to have a need for Windchill.  Creo is still at the top in the list under Product Families on PTC’s website, but it seems to have taken a back seat in terms of client fulfillment.

Respectfully,

Aaron Daniel

This is a quick rendering of a differential screw mechanism.

This is a M10x0.45 screw driven against a M8x0.4 thread.

This makes for 0.05mm motion/revolution.

Great for micro-manipulation projects.

Here's a little different perspective:

Attention:You will need to update your browsers Flash Player plugin to see videos on this site.

Update your Flash Player here. Its free and fast.

There is a new config option is available:

show_axes_by_view_scope

With that option selecting axes in the datum tab of the "Show Model Annotiations" dialog (see below) can be configured to show only the axes of the top model, not all the axes of the e.g. 50000 submodels.

• all_sub_models (the default value)
  • All axes of all submodels are shown which is slow for comprehensive models
  • This is the default behavior in the datum tab in the Show Model Annotation dialog and leads to not responding sessions
  • Example of time consuming display of a lot of axes with that config setting:
    
    
    
    
• top_model_only
  • Only the axes of the top model are shown (which is fast)
  • This setting prevents not responding sessions on large drawings

This implements the idea 1314 with the solution suggestion "Idea A" described here:

Not authorized to view the specified document 1314

There is still Idea B to improve the performance keeping the actual default behaviour:

Implement a stop button, to cancel that action if Creo Elements/Pro does not respond in that situation. Try to use the existing stop button which can be used e.g. during model retrieval.

Tested with Creo Elements/Pro 5.0 M230