Skip to main content
L
LawrenceS18-Opal
18-Opal
June 25, 2026
Question

Creo model layer tree and Function $F2 as a mapkey

  • June 25, 2026
  • 4 replies
  • 117 views

After recently upgradeing to Creo11 from Creo7, we came across a strnage conflict where our mapkey $F2 works in drawing mode but not in Modeling mode...sometimes.

 

As it turns out, if the layer tree is open in the model, the $F2 mapkey will not work but if it is collapsed or closed it will work.  Drawing mode is unaffected by the display of the layer tree.

 

I understnad that everywhere in Windows and many windows programs that $F2 is for rename.  I am not sure though why Creo does not unbind this, even after the Creo dialog pops up asking the user if they want to use the key for a mapkey or for a Creo Shortcut. Even after choosing mapkey, it still is depending on if the model layer tree is open, and if you click on a layer and press F2 it will rename that layer.  I opened Creo7 and verified that it did not work this way in Creo4, regardless of layer tree display status.

 

For a moment I thought it would be a workaround to add a collapse layer tree to the mapkey before running but of course if Creo never sees the key that won’t even run.  Any other ideas?  We may have to change the mapkey, but it is one of those that has been around as long as ProE (25+ years) and may not be easily changed in peoples minds.

 

I mention this here as a lesson learned for a rather challenging problem to solve, but also if anyone wants to add if they see this as a Creo bug or not, or add any other thoughts or workarounds to the discussion.

    4 replies

    T
    TrainStopper12-Amethyst
    12-Amethyst
    June 25, 2026

    We ran into problems when we historically (since WF2!) had $F2 mapped to the open file dialog.

    It would work in the beginning of a session, then not anymore. For some people it didn’t work at all.

    Changed to using $F3 and all is well.

      L
      LawrenceS18-OpalAuthor
      18-Opal
      June 25, 2026

      That’s interesting.  I have been working at this company since being on WF2 and this is the first we have had a problem with it! WF2, WF4, Creo2, Creo4 all worked fine for us using F2, F3.  Around Creo2 we also started using F4, F5 and F6 frequently without problems and then misc other function keys.  

      M
      Martin-H7-Bedrock
      7-Bedrock
      July 2, 2026

      I have a similar problem, but I have no mapkey bound to F2. I simply want to rename my features, thought I was going insane when it didn’t work. We recently upgraded from Creo 7 to Creo 12 never was any issues before.

      Thanks for pointing out that having the layer tree open blocks F2 for some reason. 

       

        L
        LawrenceS18-OpalAuthor
        18-Opal
        July 2, 2026

        I am glad you highlighted this. I recently tested Creo in a default environment with none of our settings and also found the same thing: F2 to rename features doesn’t work if the layer tree is open in the model (asm, prt, etc).

         

        Given that this was found not just to be mapkey related but also that the OOTB Creo functionality is not working, this should probably be reported to PTC as a bug.  I will try to do this when I get a chance but don’t anticipate I will have time for a couple of weeks.  That being said perhaps there will more success if more than 1 company reports this as a bug...

        M
        Martin-H7-Bedrock
        7-Bedrock
        July 3, 2026

        Did some digging. Apparently this has been addressed by PTC and resolved, see CS460521.

        We are currently running Creo 12.4.3.0 and this was fixed in 12.4.4.0. Released just a week after we finally upgraded…

        S
        scott_rockwell10-Marble
        10-Marble
        July 8, 2026

        I had the same mysterious behavior in drawing mode where $F2 mapkey wouldn’t function.  The “layer” sub-window was minimized in a corner of the main window and almost invisible.   After closing the layer window, $F2 (Regen/Save) worked as usual.  I never would have discovered this without your post. - many thanks!

        Terms & ConditionsAccessibility statement