Synapse Load Considerations | Razer Insider

Synapse Load Considerations

Good afternoon,

I had to break a Razer Blackwidow V3 out of storage to work on my BIOS after a CPU upgrade (long story) and remembered why I liked Razer’s hardware so much.  The keyboard had a really robust feel and, even though it’s years old at this point and been in disuse for some time, like all Razer’s peripherals I’ve owned, been excellent to use.  The lone exception was that the Orbweaver I used didn’t have an analog joystick and the palm pad slid off.  I did break it out for nostalgia’s sake and, lo and behold, still works like I bought it yesterday besides my hand resting on bare plastic.

Then I thought about why I switched to Steelseries peripherals given I’m probably a little less sure about their hardware (recently had to replace their rather expensive mouse because their scroll wheel started to fail), and I remembered that Synapse was very ungainly, ate a not-insignificant amount of my active system resources just by existing, and had a habit of asking me to restart my computer at inopportune moments (as in the asking me gave me a pop-up that became my active window; I still don’t know why a restart would be required).  I recall it using nearly twice the amount of system resources GG engine currently uses when idle and having an awful lot of features I had no use for and couldn’t remove.

However, GG is starting to also become more ungainly (I’m a little mad at them for loading me up with their Moments and 3d Aim Trainer, which I didn’t want and apparently can only disable, not remove), so I’m not as disappointed as I was before with Synapse.  I was a big fan of Razer’s hardware before their software turned me off, but it’s been quite literal years.  Has Synapse improved?  On the next round of peripheral purchase, would it be worth considering Razer again?  Or is the software still a major sticking point?

0 Replies

Be the first to reply!