Hypershift Stopped Working After December 2020 Synapse Update.

Here's the fix for me: /hypershift-stopped-working-after-december-2020-synapse-update.67897/

Still not working. Razer, Anyone looking into this?

Hello Razer. Is anyone looking into this issue yet??

Hello, everyone. After a lot of email exchange with Razer since this problem appeared and I opened a support ticket, I would like to let you know that my hypershift functions are back to normal, after a Synapse update that was installed a few minutes ago this morning (7-Jan-2021). So this seems to resolve the issue. Can you people inform us if same applies in your case. Thanks.

Hey everyone! Razer is aware of this issue, and our devs worked on a fix. Please let me know if you've received an update from Razer Synapse 3.0. Feel free to update this thread or send me a PM should you need additional assistance.

Razer.SpeedCr0ss
Hey everyone! Razer is aware of this issue, and our devs worked on a fix. Please let me know if you've received an update from Razer Synapse 3.0. Feel free to update this thread or send me a PM should you need additional assistance.

SpeedCross please read previous post! Btw, I've been talking to razer support for more than a week, exchanging emails and instructing me to try various strategies to resolve the issue (some very involved and cumbersome), with no apparent solution till today. They were ready to issue an RMA for me! The new synapse version published today solved the issue. If they were aware of the issue, why did they follow all those irrelevant procedures? Very bad support and bad coordination from their part! Fortunately, issue was finally solved. :) Mind you, I had mentioned this forum thread to them since my first email when I opened the support ticket and also mentioned it was a driver problem in my opinion (I am a senior developer for more than 25 years). They never paid any attention I'm afraid!

I got the update today and things are back to working as normal. Glad they got it resolved. Thanks for the quick turn around!

OdyMihan
SpeedCross please read previous post! Btw, I've been talking to razer support for more than a week, exchanging emails and instructing me to try various strategies to resolve the issue (some very involved and cumbersome), with no apparent solution till today. They were ready to issue an RMA for me! The new synapse version published today solved the issue. If they were aware of the issue, why did they follow all those irrelevant procedures? Very bad support and bad coordination from their part! Fortunately, issue was finally solved. :) Mind you, I had mentioned this forum thread to them since my first email when I opened the support ticket and also mentioned it was a driver problem in my opinion (I am a senior developer for more than 25 years). They never paid any attention I'm afraid!

Thanks for confirming. The team is letting everyone to perform whichever steps that you help isolate/resolve the issue. Once exhausted, they are reporting it to our devs together with the Razer Synapse logs (if applicable) from each affected user's to help the investigation. I'll cascade your feedback to the team. Hi everyone! Feel free to send me a PM or visit our self-help options should you need additional assistance. I'll be locking this thread now as resolved.