Overwatch Lighting Not Working

[secastles]

Expected Behaviour

When launching Overwatch the keyboard color scheme should be controlled by the game.

Actual Behaviour

Keyboard lights all go out. Logitech software switches mouse (g502) color to Overwatch profile (I have a profile setup). I tested this with Factorio and Factorio/Aurora correctly controls both keyboard and mouse. For me at least this only seems to be an issue with Overwatch. I can alt+tab out of Overwatch and the desktop keyboard lights come back on. But as soon as I go back into Overwatch the lights go out. I'm not using Aurora for a desktop light scheme (I'm using wootility and Logitech for that).

Reproduction steps

Launch Overwatch - Keyboard lights go out

Frequency

Every time

Aurora Version:

0.7.0-rc2 Overwatch: 1.40.1.0 Wooting Two FW: 1.26.1

Previously an Issue?

No, but I'm new to Aurora ever since picking up the Wooting Two 2019-09-30 21.35.44.log

[Wibble199]

Are you using the new Razer Chroma Layer for this? Due to changes in how Overwatch loads and verifies the lighting code library, we are no longer able to replace the DLL without our own "wrapper" because Overwatch detects that it is not an official one and refuses to load it. Not all Razer Chroma-supported games check the DLL, which likely explains why Factorio is working.

Please try the following instructions to use the new method of getting the Razer lighting, which should be compatible with Overwatch.

1. Make sure you're running build v0.7.0 or above
2. Open settings, go to the Devices and wrappers tab
3. Click the sub-tab Razer
4. Check if the supported version of the chroma sdk is installed and connected successfully 4a: If it is, the text should be green and you can proceed, 4b: If it's not, click the Install button, wait for it to finish and then restart Aurora 4c: When Aurora starts up again, the Connection text should now say Success and turn Green.
5. Click the profile of the game you want chroma lighting to be visible on (icons on the left side of the window)
6. Add a "Razer Chroma Layer" to the top of the layer list
7. Open the game, and make sure it's working!

Troubleshooting:

1. Aurora shows the sdk as being Connected (in devices and settings) and the razer layer still doesn't work! A: If you've patched the game using aurora's "Apply wrapper patch" button, you need to delete the two dll's Aurora places in the game directory:
   • RzChromaSDK.dll and RzChromaSDK64.dll
2. The colors are too dim A: Open the Razer Chroma Layer of the profile you want to change, then tick the "Enable Color Post Process" checkbox and adjust the sliders as you want.
3. I can't find some of the options or menus mentioned A: You most likely don't have the correct build from step 1.

[Seawolf159]

I'm running beta v0.7.0rc2 and i did all the things you said and it still doesn't work. Are these (RzChromaSDK.dll and RzChromaSDK64.dll) really not needed anymore?

[diogotr7]

Those are definitely not needed anymore. If they're present you need to remove them or it won't work .

[Seawolf159]

I had removed them. Still doesn't work.

[secastles]

Ditto. I did have to install the chroma sdk and now that is green. I did not press the "install aurora wrapper patch for razer" so I hope that's cool. I don't have any Razer software installed otherwise. I also checked for any lingering razer DLLs in the OW directory. All that said, it doesn't work (for me). 2019-10-07 20.36.15.log

[diogotr7]

Your logs tell me aurora is detecting the overwatch lighting successfully ( or at least it detects overwatch being picked up by the chroma sdk). The one problem I'm noticing is every device is initializing and shutting down immediately after. If you have the desktop profile disabled in Aurora, try enabling it and see if that helps. Keeping device integration problems and Razer layer problems separate is important if we want to diagnose the problem properly.

[secastles]

Today I actually got it to work by changing... nothing. I came out of sleep and loaded up OW and it worked. But now I have a different problem. I exited OW to do some more testing and Aurora crashed. So I killed it in task manager. But, it never released control back to the Wooting utility. The keys were like forever mapped to the OW profile. I had to reboot to get control back to Wootility. I'm attaching the log from the crash (3705408). After that I rebooted to do some more testing and... now it doesn't work again. So I'm attaching that log too (3705446). So it was working after changing nothing, then it wasn't again. Odd. I'll continue to work at it to see what the culprit might be. 2019-10-08 23.04.04.log 2019-10-08 23.04.04.log

[diogotr7]

The lighting o wooting keyboards gets stuck if aurora closes unexpectedly because the communication is direct with the hardware. Unplugging it solves the issue, no need to reboot.

[secastles]

Cool. Let's keep this thread open if you want to see if I can consistently reproduce the problem. As if last night the OW profile wasn't working but today is a new day.

On Wed, Oct 9, 2019, 3:31 AM Diogo Trindade notifications@github.com wrote:

The lighting o wooting keyboards gets stuck if aurora closes unexpectedly because the communication is direct with the hardware. Unplugging it solves the issue, no need to reboot.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/antonpup/Aurora/issues/1730?email_source=notifications&email_token=ALJVZVVGNIVR5I7BSEI5PBDQNWCGLA5CNFSM4I4C6UEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAW55DA#issuecomment-539877004, or mute the thread https://github.com/notifications/unsubscribe-auth/ALJVZVQUTN66DHMDMXCM3HTQNWCGLANCNFSM4I4C6UEA .

[diogotr7]

Looking at your logs i found the following:

[INFO] 23:04:06: RazerManager loaded successfully! This line means the razer sdk core sdk is probably installed and running. [DEBUG] 23:05:49: RazerManager current app: Overwatch.exe [748] This means aurora detected Overwatch as taking control of the razer sdk.

From here the lighting should work as long as you have:

• The connection to the keyboard working properly
• The razer chroma layer in the overwatch profile.

Also, it would clean up the logs a lot if you could disable all the device types you don't use in Settings > Device Manager.

[secastles]

OK, did some more testing... or rather observing as I use my PC and play Overwatch. I'm attaching two log files. The one from 10-14 should capture Aurora not working. In fact, when I exited OW I found that it had crashed or was at least unresponsive. But over the last week I haven't seen Aurora work once so (1) not working with OW is typical in my case and (2) it may or may not be crashing often (I haven't been checking). Today I woke the PC from sleep and made sure Aurora was running then started OW. It worked! I exited OW, literally did nothing else but wait a little bit and then restarted OW. It didn't work! I'm attaching the log from today too to see if it captures any helpful information (10-16). So, in a nutshell, on my rig at least, it's been random but mostly it doesn't work with OW. Let me know if I can provide anymore help.

One more piece of info: I typically don't shutdown. I sleep the PC and wake it. I'll reboot every few weeks or so. 2019-10-14 14.54.30.log 2019-10-16 15.37.30.log

[shockthetoast]

I've been having the same issue. Sometimes the colors work in Overwatch, sometimes they don't. The interesting part is that if the keyboard is completely dark, but I alt+tab to Aurora and select the Overwatch profile, the keyboard lights up with the correct colors - including those of any in-use character, etc. Once I return to the game the colors are lost. This seems to be random, and sometimes restarting the game gets things working again. It seems like it's properly disabling the desktop profile when it detects the game, but sometimes fails to activate the Overwatch profile to replace it.

[secastles]

Over the past month or so I've been playing a lot of overwatch and have updated to each new release of Aurora. Oddly, it seems as though Aurora has just given up and just freezes/crashes when I play Overwatch now. I don't think I've seen Aurora take control of the Wooting lighting in well over three or four weeks.

[theomerman]

I had an issue with overwatch lighting that was not working on a corsair strafe rgb but in the settings/devices & wrappers/razer said unable to install I tried everithing until I realize I have a razer mouse too and the drivers from that mouse was causing a trouble with it, to solve it I uninstall the mouse driver and go back to aurora to try install the setting again and it did install, then install the mouse driver again and now is working, hope that helps someone.

[axe-murderer]

i'm also having an issue where overwatch lighting isn't working.

2020-04-02 22.32.48.log

you can see in the log that overwatch never takes over the lighting. does anyone know why?

[Magicrafter13]

My default overwatch profile has no overlay layers, and only one layer called Chroma lighting, and it doesn't even do anything. Is it possible to reinstall the profiles the program comes with, or is this just how the overwatch profile comes... empty?

[hho]

@Magicrafter13 Yes, that's how it comes.

Explanation: Overwatch uses the Razer API to control the lighting - so Aurora takes that in via the one Razer Chroma layer.

[Magicrafter13]

@Magicrafter13 Yes, that's how it comes.

Explanation: Overwatch uses the Razer API to control the lighting - so Aurora takes that in via the one Razer Chroma layer.

I don't understand what's up then, I played Overwatch with Aurora running, and not a single key on my keyboard did anything. And the keyboard is setup fine, as I've had other games work with Aurora out of the box.

[ikrowni]

im having the same issue others are having. When i start overwatch all the lights just go out.

[axe-murderer]

overwatch itself has disabled chroma integration for the time being as it was crashing overwatch

[ikrowni]

overwatch itself has disabled chroma integration for the time being as it was crashing overwatch

I found the article indicating the problem immediately after i posted this. thanks for the heads up though