Wallpaper Engine

Wallpaper Engine

View Stats:
SolidVault Apr 11, 2020 @ 11:20am
Razer chroma lighting going crazy
Hey guys so i have an issue with the lighting with wallpaper engine and it seems that the lighting goes crazy and colors are light shades of blue yellow and pink, even though i have a normal wallpaper or the razer wallpaper,
< >
Showing 46-60 of 65 comments
RedAsKetchum Apr 30, 2020 @ 4:45pm 
Originally posted by Jarod:
i get the same issue (crazy lights) on keyboard an mouse. its since the last synapse update. Reinstall didnt work for me.

It also happens in Apex Legends, which is using the keyboard effects.
and DOOM ! Razer totally broke their software. I reinstalled windows and nothing so it definitely cant be my peripherals. Lucky the people that somehow got their stuff working again, but for me its been broken since April 9 or so. So annoying...
RedAsKetchum Apr 30, 2020 @ 4:49pm 
Originally posted by Biohazard:
Originally posted by RedAsKetchum:
Even more awesome now. All peripheral lights go crazy, not just the speakers. That includes my mouse, tartatus V2, keyboard and speakers. It cant be hardware related at this point :/

Everything worked before Razer's update, right? And then you had numerous problems out of nowhere?

I don't think it's hardware related either, but it's definitely not something we can fix in Wallpaper Engine right now. There was nothing changed by Razer that we are supposed to 'update' or anything - they updated something internally which we have no access to.

Someone else said that they only have this problem because Wallpaper Engine simply starts more quickly than Razer Synapse. That makes sense, Wallpaper Engine is supposed to start quickly, but it always did. So maybe that's why you don't notice this with any other program, because other programs don't start before Synapse does.

If Razer responds to us with any more information or if they make it possible in their Chroma SDK for us to work around whatever they changed, then we will do that and we will inform you. But Razer hasn't responded to us yet with any more infos about these various problems.
Im 100% confident its not the hardware. I another chroma connect enabled app (Bethesdas videogame DOOM) and the lights are crazy as well. It flashes through every supported color by the games chroma profile. In wallpaper engine it happens as well but at least less crazy (my speakers). So I guess its not just because Wallpaper engine starts before Synapse does. Appreciate the follow up! I honestly want to get this solved for Wallpaper Engine alone. I bought the software and after 3 days of use the update broke its support :/
Bilgediver May 7, 2020 @ 7:38pm 
This literally just happened to me, and its because I just reloaded the Wallpaper engine app. What's annoying to me is the wallpaper engine website ONLY advertises ICUE support which is Corsair, so they don't really technically support Razer integration yet it somehow works in the app (in the meantime it made my lights on my ornata keyboard, goliathus mat and Razer Blade laptop keys go absolutely bonkers). I just disabled it in Chroma.
Bilgediver May 7, 2020 @ 8:13pm 
Ok Somehow I got it working. 1st thing I did was after the Workshop update, I closed and reopened Synapse. That didn't get it working right away, but right now I'm on a multi-monitor setup and My Laptop (Monitor 2) wasn't anything but a picture. Trying to change it on Monitor #1 (external) kept getting flickers then shutoff. I switched to changing the wallpaper for Monitor #2 (Laptop screen) and somehow it worked. Now it works for every wallpaper I try.
Biohazard  [developer] May 8, 2020 @ 4:38am 
Originally posted by Bilgediver:
This literally just happened to me, and its because I just reloaded the Wallpaper engine app. What's annoying to me is the wallpaper engine website ONLY advertises ICUE support which is Corsair, so they don't really technically support Razer integration yet it somehow works in the app (in the meantime it made my lights on my ornata keyboard, goliathus mat and Razer Blade laptop keys go absolutely bonkers). I just disabled it in Chroma.

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.
RedAsKetchum May 10, 2020 @ 8:41pm 
Originally posted by Biohazard:
Originally posted by Bilgediver:
This literally just happened to me, and its because I just reloaded the Wallpaper engine app. What's annoying to me is the wallpaper engine website ONLY advertises ICUE support which is Corsair, so they don't really technically support Razer integration yet it somehow works in the app (in the meantime it made my lights on my ornata keyboard, goliathus mat and Razer Blade laptop keys go absolutely bonkers). I just disabled it in Chroma.

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.
Yeah in my case I could never fix it. I was told they are working on it like 2 weeks ago and thats as much as they wanted to tell me.
GasmisenFeik May 10, 2020 @ 11:34pm 
Heyo! Decided to solidify Biohazard's way to fix it, and say that it 100% worked, the real issue "generally" is that Wallpaper Engine DOES in fact Launch too quickly, as Uninstalling it and THEN launching it after Razer Synapse installed again fixed the problem, only suggestion is adding a secondary priority for Razer users to only launch Wallpaper Engine AFTER Synapse is launched as well to circumvent this problem?
Biohazard  [developer] May 11, 2020 @ 4:25am 
Originally posted by Gamingfiker678:
only suggestion is adding a secondary priority for Razer users to only launch Wallpaper Engine AFTER Synapse is launched as well to circumvent this problem?

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.
Last edited by Biohazard; May 11, 2020 @ 4:26am
GasmisenFeik May 11, 2020 @ 10:23pm 
Originally posted by Biohazard:
Originally posted by Gamingfiker678:
only suggestion is adding a secondary priority for Razer users to only launch Wallpaper Engine AFTER Synapse is launched as well to circumvent this problem?

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.
Alright! Thanks for telling me! I wish you the best of luck in this kurfuffle!
Bilgediver Jun 27, 2020 @ 6:09pm 
btw, it works for me. it takes a reboot of wallpaper engine or rechanging the wallpaper once or twice. The first time you set it it doesn't work, but the second time it does.
Hi there,

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.
Tim  [developer] Jun 28, 2020 @ 4:42am 
We think it's actually due to the way that Razer updates Synapse that causes problems. You can probably fix this issue by turning off Wallpaper Engine, then reinstalling Synapse and then both the 64 and 32 Bit version will work fine again on your system.
Mr Audit Jun 28, 2020 @ 6:21am 
My Nommo Chroma speakers still don't sync with wallpaper engine. I've tried installing/uninstalling wallpaper engine and synapse in various sequences. I just gave up trying at his point waiting for a fix
Biohazard  [developer] Jun 28, 2020 @ 6:26am 
Originally posted by Mr Audit:
My Nommo Chroma speakers still don't sync with wallpaper engine. I've tried installing/uninstalling wallpaper engine and synapse in various sequences. I just gave up trying at his point waiting for a fix

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?
RedAsKetchum Jun 28, 2020 @ 4:25pm 
Originally posted by Mr Audit:
My Nommo Chroma speakers still don't sync with wallpaper engine. I've tried installing/uninstalling wallpaper engine and synapse in various sequences. I just gave up trying at his point waiting for a fix
Its important you contact razer with this issue. Ive been contacting them for a while now. They need your logs to find whats the error. At the moment it seems only Ive been bugging them for a while with the issue. Maybe more logs can point to some error in common. Today they releaseda new update to attemp to fix it, but still didnt work for me.
< >
Showing 46-60 of 65 comments
Per page: 1530 50

Date Posted: Apr 11, 2020 @ 11:20am
Posts: 65