Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Just FYI: we haven't updated the website because we're building a whole new website (note the year 2019 at the bottom of the current website). We absolutely support Razer officially, it's on the Steam store too, but Razer had a number of bugs in their most recent update and we cannot do much besides continuously asking Razer about progress on this - which we're doing.
There is no way for us to see if Synapse is "ready". We have been waiting for both Corsair and Razer to implement some kind of event at least to handle this and even sent some suggestion to Corsair on how this could work.
Before this Synapse update there was also no issue with Wallpaper Engine starting before Synapse. It actually worked out. But now it doesn't. There is also just no generally way to make a program launch after another specific program, we really need something from Razer/Corsair here to sync things up correctly.
This may have already been discovered, but I have found that this only occurs for me when running the 64-bit Wallpaper Engine.
When launching from Steam, the problem did not occur, however when Wallpaper Engine runs as a Windows service, it would happen.
Originally I thought it was the service causing the flickering behaviour, so began troubleshooting with procmon to see if the application start is any different - which made me notice my steam would launch the 32-bit version.
It did not matter whether I had Synapse open or not.
I've been able to replicate this by selecting the 64 bit version from Steam instead - straight away the problem occurs.
Swap back to 32-bit, problem goes away.
Hope this helps - will keep troubleshooting to see if I find anything else.
It's sad to hear Razer still hasn't fixed the Nommo speakers. But that's a completely different problem to the recurring update problem that Synapse appears to have, which Tim was talking about just now.
Have you contacted Razer about the Nommo speakers directly before and have they said anything?