Synapese 2.0 (Legacy) vs Synapese 3.0 confusion | Razer Insider
Skip to main content

Synapese 2.0 (Legacy) vs Synapese 3.0 confusion


I can install Synapese 2.0 (Legacy) stand alone for my Razer Kraken 7.1 CHROMA USB Gaming Headset. It works great.
Then I can install Cortex Game Booster and when I am in the install process, it gives me the option of installing Synapese 3.0 which seems to be a completely different program from 2.0. not offering me the setup options for my headset. Why allow both of these to be installed? Please explain this.
Did this topic help you find an answer to your question?
This topic has been closed for comments

4 Replies

Jenjar
Vanguard
  • Vanguard
  • 483 replies
  • January 8, 2019
Cortex and Synapse are a part of Razer Central, so when you install either Synapse 3 or Cortex it would give you the option to install the one you do not have (synapse 3 in your situation) as well, but you do not need to.

The Kraken 7.1 Chroma (V1 or V2) are only supported on Synapse 2.0 for the time being, but they may be moved over to Synapse 3 in the future as older products get support over time. If you do not have any other Razer products that would use Synapse 3, you can just delete it.

ZiCott
  • Insider Mini
  • 35 replies
  • January 9, 2019
Well my RBS-H2 only works with Synapse 2, and Having both 2/3 installed causes all the lighting and profiles confused, and doesn't work as advertised. Its a bit annoying cause I love my Cynosa KB & Lancehead Mice.

  • 144 replies
  • January 9, 2019
Jenjar
..., but they may be moved over to Synapse 3 in the future as older products get support over time.


HaHaHa, nice joke !

It seems VERY odd that I can install Cortex and in the install process, it asks me if I want to install Synapese (no mention if it is 2.0 or 3.0). This when I already have Synapese 2.0 installed and Synapese 3.0 doesn't support my device.
This is VERY confusing for a user and seems sloppy to me.

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings