Running FFXIV with Synapse 3.0 major issues

Discussion in 'Razer Support' started by Xumo992, Mar 13, 2020.

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

    Xumo992 New Member


    So this started happening a bit ago but I stopped playing ffxiv so I didnt report it. Since then I have started playing again and now this issue is becoming a major problem.

    I have my Naga trinity mouse side buttons bound to 'ctrl+1 to =' respectively and when I use these too frequently synapase completely starts to bog down and lag out my entire PC, not just the game, to the point where the keyboard/mouse both completely stop responding(Worse case scenario, there is many other weird stutters it causes more frequently) when it doesnt screw up my entire PC it does stop using the hotkeys, instead of pressing ctrl+1 itll just press 1 or else take about 5seconds to actually do the button press

    I've tried completely reinstalling synapse with no luck, I have made sure not to have any other programs running when testing this issue and it still happens... previously I was using the old naga mouse and synapse 2.0 and I never had anything close to any issues like this, but now since I bought the new trinity mouse I am forced to use 3.0 so I am running into all these issues.

    Windows 10 Home 64-bit
    16GB DDR4 Vengeance Pro Corsair
    Ryzen 7 2700X
    Nvidia RTX 2070
    Asus ROG Strix b450-F
    Western Digital Black sn270 1TB

    Razer Blackwidow Chroma
    Razer Naga Trinity

    Spoke with razer support and they suggested going into device manager deleteing all drivers as well as razer folders in program files etc

    After reinstalling, there was no change, in fact its worse now it keeps locking me into windows and I cant click out of them unless I ctrl+alt+delete and open task manager
    Last edited by a moderator: Mar 19, 2020
  2. Razer.Caziel

    Razer.Caziel I am the Lightbringer Staff Member

    Does this happen only when running it with FFXIV? Do you mind testing it with other games? Judging from your initial description of the issue, it would appear to me as though the game is actively blocking the app for executing hardware macros.
Thread Status:
Not open for further replies.
Sign In with Razer ID >

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