🛈 Announcement
Greetings! Ubisoft Connect forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game
  1. #1

    Overlay - Shift +F2 does not work

    Uplay overlay shift +F2 does not work in steam FC3 game.
    It was working now and then but hasn't worked in a while.
    I have the settings for Uplay overlay enabled. I tried to disable steams overlay, but still not working..

    I uninstalled both steam and Uplay and reinstalled, still does not work....
    The Uplay button in game does not work either.
    Any one else have the problem or suggestions on how to fix ???
    Share this post

  2. #2
    UbiHawk1ns's Avatar Ubisoft Support Staff NCSA
    Join Date
    Dec 2012
    Posts
    211
    Hey jmcu, hope all is well this evening. Make sure that you are running minimal background applications and processes. Prior to launching the game, make sure to close down any unnecessary programs which can cause a drain in system resources. Also, make sure that you are running the latest drivers for your Video Card. Since you have uninstalled and reinstalled both, it would seem that this is system related - not client related. Let me know if this works for you.
    Share this post

  3. #3
    Hi,
    Thanks for the reply.

    I have checked the system resources and do not believe that is the issue.
    I am running I7 3930k and the game only utilizes 9% of cpu and 10% 3GB of 32GB of memory installed
    I am running 3 - 680's with the latest drivers. ( only 1 card can be used in MP because of crashing in SLI )
    while in the menu screen trying to open the overlay.

    I would think the Uplay button in game would work.
    Share this post

  4. #4
    UbiHawk1ns's Avatar Ubisoft Support Staff NCSA
    Join Date
    Dec 2012
    Posts
    211
    The overlay should work. I am going to look into this for you, and will get back to you with any information that I can find. I cannot think of an immediate resolution, as you are running on a system that is more than capable us supporting the game and client processes.
    Share this post

  5. #5
    I'm having the same issue. Only had the game 2 weeks and have only ever got the overlay to come up once. Restarts do nothing and disable and enabling of the overlay dont work. I am not about to uninstall steam to get it to work. I have tried removing and reinstalling Uplay but again nothing. My steam overlay will also not come up which makes me think its a game issue. Drivers are up to date. No idea what to do.
    Share this post

  6. #6
    same issue here, playing on an i5 ivy so not sure whats going on. steam nor uplay overlay displays in game.
    Share this post

  7. #7
    Ubi-Lhainiev's Avatar Moderator
    Join Date
    Jul 2012
    Location
    Ontario, Canada
    Posts
    1,712
    Hi All,

    Pain_elemental - What game are you playing while trying to open the overlay?

    We will forward this on to the Support Team to have it looked into.

    In the meantime, please create a ticket to support by clicking on the “Ask a Question” tab on the top of the page at http://support.ubi.com/ so they can investigate and assist you on an individual basis.
    Share this post

  8. #8
    OK Just wanted to respond back again. It is Farcry 3 I am playing. I found out my particular problem. It seems the Mumble overlay causes issues and will actually stop both the Steam and Uplay overlay from working. After turning the Mumble overlay off the ingame ones started working again.
    Share this post

  9. #9

    UPLAY_OVERLAY didnt locate

    Hello all, I have a problem also with Uplay_overlay. I play the game Splinter cell blacklist. I install it by disc. Almost 4 hours for me to install it. But it's was make me sad when I can't launch that game. It was say UPLAY_OVERLAY_Show didn't located. Please help me to fix it
    Share this post

  10. #10
    try closing all apps, most importantly the ones with overlay. I closed them all and it worked. then i tried lunching game with 1 app at the time. Found out that MSI afterburner's Rivia Tuner statistics was causing the issue.
    Share this post