UniLight logiled inactive

Hi HunterZ, first, thank you for the nice software for RGB freaks.

Can you please guide me? I've got Alienware 17 R4 + Logitech G910 Orion Spectrum keyboard + Logitech G933 Artemis Spectrum Snow.

For Alienware, Unilight works nicely and shows "Active" in tray. For Logitech, though, it's showing "Inactive" and doesn't work. Can you please show where should I search? I'm a .NET developer, so my C++ skill is low.

Thanks again!

Feb 14 '18 04:02 Bassist067

Odd, I use it with an Alienware 17R3 and Logitech G502 Proteus Spectrum.

Do you have the latest Logitech Gaming Software installed and running? I'm currently using 8.96.88.

Feb 14 '18 06:02 HunterZ

oh yes, LGS is running with the latest version. I thought maybe it's about the headphones, but it's not. I guess I need to compile and debug the thing, but under VS2017 it's difficult to compile

Feb 17 '18 08:02 Bassist067

Do you have a C:\Program Files\Logitech Gaming Software\SDK\LED\x86\LogitechLed.dll file on your system? What version does it show if you right-click it in Explorer and open its properties?

Do you have the following Windows Registry entries with default values containing the above path: HKEY_CLASSES_ROOT\CLSID{a6519e67-7632-4375-afdf-caa889744403}\ServerBinary HKEY_CLASSES_ROOT\Wow6432Node\CLSID{a6519e67-7632-4375-afdf-caa889744403}\ServerBinary HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{a6519e67-7632-4375-afdf-caa889744403}\ServerBinary HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID{a6519e67-7632-4375-afdf-caa889744403}\ServerBinary HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID{a6519e67-7632-4375-afdf-caa889744403}\ServerBinary

If you get it compiling, you may want to try messing with this line in LLEDUtil.cpp to see if it makes a difference:

if (!LogiLedSetTargetDevice(LOGI_DEVICETYPE_PERKEY_RGB | LOGI_DEVICETYPE_RGB)) return false;

In particular, this might be worth trying:

if (!LogiLedSetTargetDevice(LOGI_DEVICETYPE_ALL)) return false;

I put that in to have it leave monochrome devices alone, but it's possible that Logitech messed up their categorization of your device(s).

Looking at LLEDUtil.cpp again after not having touched it for several months, I see some slightly goofy stuff in there, but I don't see anything that would cause your issue.

Looking at the SDK documentation again (https://www.logitechg.com/en-us/developers), another application initializing the RGB SDK after UniLight is launched may cause it to lose control. I don't aggressively try to take back control but maybe I should? Part of the reason I didn't make it aggressive is because Logitech mentions some stupid stuff about needing to wait some undefined amount of time between initializing the SDK and trying to do anything with it, so I was worried that trying to (re)init every time I want to set the colors would end up not working.

Edit: I probably ought to put a timer back into UniLight to have it try to re-set the color every so often, which I could then use to do Logitech (re)inits+delays as well. This might also help with the fact that UniLight seems to lose its AlienFX/LightFX connection after a while for some reason. I used to run UniLight exclusively on a timer, but then I found some Windows events I could drive it from instead, which is better for performance reasons.

Feb 17 '18 16:02 HunterZ

Hello there.

So, i also have a problem which looks a bit like this one. When i open UniLight, my keyboard and my mouse ( They're both Logitech, g810 and g403 wireless ) lights in blue. When i mouseover UniLight in the Windows system tray, i can read : "UniLight status: Current color: 0x00c76f00 Previous color: 0x00000000 CorsCUE: inactive LightFX: inactive LogiLED: active" When i use "Synchronize manually", the color remains the same. When i open UniLight, even with a red picture on my screen, the color is always "0x00c76f00".

My LogitechLed.dll version is 8.96.88, i checked all the Windows registry entries, and they all have the default values.

I tried to be as precise as possible, tell me if something is missing. :)

Feb 27 '18 10:02 RetroL

RetroL: Your issue may be slightly different, as you get "active" for LogiLED.

Your DLL is 8.96.88, or is that your LGS version? My LGS version is 8.96.88, but my C:\Program Files\Logitech Gaming Software\SDK\LED\x86\LogitechLed.dll is 8.96.81.0.

What version of Windows are you running?

Feb 28 '18 02:02 HunterZ

My DLL version is 8.96.88.0 and my LGS version is 8.96.88. I run Windows 10 Family, the version is 1709, and the operating system version is 16299.248 windows version logitech capture ( The screenshots are in french, but it should be understandable )

Feb 28 '18 17:02 RetroL

LGS said I have the latest version installed, but my DLL version was lower than yours.

I shut down UniLight and re-downloaded and reinstalled the latest LGS from Logitech's web site, and now I have LogitechLed.dll 8.96.88.0. UniLight still works for me, so the problem must be something else.

Maybe try closing any apps that have LED support and then reinstall the latest LGS from Logitech's web site? http://support.logitech.com/en_us/software/lgs

In the meantime, I'm writing an email to Logitech's developer support to see if they have any ideas.

Edit: I also double-checked that I have the latest Logitech gaming SDK, so I don't think it's an issue of building against old stuff.

Feb 28 '18 23:02 HunterZ

Update:

Logitech got back to me. The main thing they wanted me to check on is that you guys have "Allow games to control illumination" enabled in LGS:

They also pointed out some minor issues with my code that they don't expect are causing the issue, but I'll try to get them fixed anyway just in case.

Mar 13 '18 02:03 HunterZ

OK, I've released v1.3 with some cleanups to the Logitech support. Let me know how things go for you.

Mar 13 '18 03:03 HunterZ

I just tried the new version 1.3, and the problem is still there, with the same color ( 0x00c76f00 ) "Allow games to control illumination" was already checked for me, i tried to turn it off and on, but it didn't do anything.

Mar 13 '18 09:03 RetroL

I've released a version 1.4 that adds a right-click menu to open a popup with detailed status. Can you try running this and posting a screenshot?

Mar 18 '18 17:03 HunterZ

How can I download the release version? Or how can I compile the solution - it looks like you didn't include the SDKs DLLs and headers. Thanks in advance - you're doing a great job!

Mar 26 '18 16:03 Bassist067

Releases are here: https://github.com/HunterZ/UniLight/releases

The file you want is UniLight_v1.4.zip

I'll create an issue to add links in the readme to where the SDKs are provided by their respective companies.

Mar 26 '18 16:03 HunterZ

Hey, here is the screenshot i took : 00000screenshot unilight

Mar 26 '18 17:03 RetroL

Mar 26 '18 17:03 Bassist067

RetroL: It looks like the Logitech API is reporting success at setting the colors for you, so it seems that there must be something outside of UniLight that is overriding it.

Bassist067: UniLight is reporting that its call to the Logitech API to initialize Logitech LED support is failing. This is the first thing that UniLight does when it starts up, so something fundamental is wrong. Are you able to control your device colors from the Logitech Gaming Software app?

Mar 27 '18 01:03 HunterZ

The Logitech software works nice for me - I can easily sync my L gear or use all the G910 different light modes. I'll try to install all the SDK and compile the project

Mar 28 '18 04:03 Bassist067

I've updated README.md with tool/SDK links.

You probably already have the AlienFX SDK because I think it comes with Alienware Command Center or whatever.

Mar 28 '18 15:03 HunterZ