Linked Games directory to .exe files can't be changed.

Discussion in 'Razer Synapse 3 Beta' started by LT_GamesTV, Jul 6, 2020.

Thread Status:
Not open for further replies.
  1. LT_GamesTV

    LT_GamesTV New Member

    Certain games, such as Fortnite for example, are "automatically detected" but the wrong directory/link to the .exe file is used. This should be easily remedied by changing the link to the correct file, however Synapse will not allow you to change the address to another .exe file.

    With fortnite the automatic address is:

    C:\Epic Games\Fortnite\FortniteGame\Binaries\Win64\FortniteClient-Win64-Shipping_BE.exe

    The correct address should be:

    C:\Epic Games\Fortnite\FortniteGame\Binaries\Win64\FortniteClient-Win64-Shipping.exe

    (In my case it's actually stored on my D drive but the address is the same. The point is that you should be able to change the .exe file that razer synapse points to. However you cannot. So I have to manually switch profiles to games it gets the .exe file incorrect on.

    I have attached an image showing the address and that change is not allowed.
     
    Thorgal_athman likes this.
  2. LT_GamesTV

    LT_GamesTV New Member

  3. javon27

    javon27 New Member

    I have the same issue, except for me it detects the "_EAC.exe". That means, when I first start Fortnite, and the anti-cheat software is doing its thing, my profiles change like they're supposed to. When it finishes and loads the Fortnite binary, it reverts back to my desktop profile.

    fortnite-synapse3.PNG
     
    Thorgal_athman likes this.
  4. Thorgal_athman

    Thorgal_athman New Member

    Hello everyone,
    Can you also point this out on the thread I put here:

    "Synapse, the choice of fortnite's exe not working" on "FORTNITE TALK" forum

    So that I can get Razer to understand the problem !

    Many Thanks
     
  5. Thorgal_athman

    Thorgal_athman New Member

  6. Thorgal_athman

    Thorgal_athman New Member

  7. Thorgal_athman

    Thorgal_athman New Member

    Good news:
    The dev team was able to reproduce this issue and we still have to wait, certainly, for a fix in a future synapse update.

    Wait and see :D
     
Thread Status:
Not open for further replies.
Sign In with Razer ID >


Don't have a Razer ID yet?
Get Razer ID >