Corsair Employee Corsair CJ Posted June 29, 2018 Corsair Employee Share Posted June 29, 2018 CUE SDK has been updated to include DIY devices (Lighting Node PRO/Commander PRO). Supported Devices: Keyboards: CGK65 RGBK65 LUX RGBK65 RGB RAPIDFIREK70 RGBK70 LUXK70 RAPIDFIREK70 LUX RGBK70 RGB RAPIDFIREK95 RGBSTRAFESTRAFE RGBK63 (wired)K68K95 RGB PLATINUM Mice: M65M65 PRO RGBSABRESABRE RGBSABRE RGB OpticalSABRE RGB LaserScimitarGLAIVE RGBScimitar PRO RGBKATAR Headsets: VOID USBVOID WirelessVOID PRO USBVOID PRO Wireless Mouse Mat: MM800 RGB Headset Stand: ST100 RGB LED Controllers: Lighting Node PROCommander PRO Requirements: Windows 7, 8, 10 http://downloads.corsair.com/download?item=Files/CUE/CUESDK_3.0.171.zip Link to comment Share on other sites More sharing options...
hastegag Posted June 30, 2018 Share Posted June 30, 2018 Throw this in above commander pro case statement on the color pulse examples for a good time: case CDT_MouseMat: { LedColorsVector keys; keys.push_back(CorsairLedColor{ CLMM_Zone1, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone2, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone3, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone4, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone5, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone6, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone7, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone8, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone9, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone10, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone11, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone12, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone13, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone14, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone15, 0, 0, 0 }); availableKeys[deviceIndex] = keys; } break; case CDT_HeadsetStand: { LedColorsVector keys; keys.push_back(CorsairLedColor{ CLHSS_Zone1, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone2, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone3, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone4, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone5, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone6, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone7, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone8, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone9, 0, 0, 0 }); availableKeys[deviceIndex] = keys; } break; I have to get a commander pro and some fans to see the magic together... Link to comment Share on other sites More sharing options...
Corsair Employee Corsair CJ Posted June 30, 2018 Author Corsair Employee Share Posted June 30, 2018 Throw this in above commander pro case statement on the color pulse examples for a good time: case CDT_MouseMat: { LedColorsVector keys; keys.push_back(CorsairLedColor{ CLMM_Zone1, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone2, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone3, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone4, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone5, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone6, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone7, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone8, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone9, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone10, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone11, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone12, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone13, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone14, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLMM_Zone15, 0, 0, 0 }); availableKeys[deviceIndex] = keys; } break; case CDT_HeadsetStand: { LedColorsVector keys; keys.push_back(CorsairLedColor{ CLHSS_Zone1, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone2, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone3, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone4, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone5, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone6, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone7, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone8, 0, 0, 0 }); keys.push_back(CorsairLedColor{ CLHSS_Zone9, 0, 0, 0 }); availableKeys[deviceIndex] = keys; } break; I have to get a commander pro and some fans to see the magic together... Good catch. Not sure if leaving the HeadsetStand and MouseMat cases out of the example was intentional. That being said, wireless mice and keyboards (K63 wireless and Dark Core RGB) are not supported by the SDK currently. DRAM and AIO coolers are also absent for the time being. Link to comment Share on other sites More sharing options...
Darth Affe Posted July 8, 2018 Share Posted July 8, 2018 The data provided by CorsairGetLedPositionsByDeviceIndex (for keyboard, headset stand and mousemat) is completely wrong. I expect this to be not directly related to the new SDK but with iCUE since the old SDK does the same thing here. The position-data consists of by far to big values and width and height is always 0. Link to comment Share on other sites More sharing options...
MichaelXF Posted July 19, 2018 Share Posted July 19, 2018 Will the CUE SDK support Corsair Vengeance RGB PRO Ram? I need to know this Link to comment Share on other sites More sharing options...
saitei Posted July 25, 2018 Share Posted July 25, 2018 (edited) Any plans to upgrade your (Corsair's) dev environment? Current default project settings are based on VS2015 and really old build tools (v120 aka Visual C++ 2013). I don't see anything specified in the docs if upgrading the project settings will break anything, or recommended dev tool versions. Edit: Seems to work even after upgrading the <WindowsTargetPlatformVersion> to 10.0.17134.0 and the <PlatformToolset> to v141. Docs say that CUE acts as priority layer 127, but the 'progress' example project defaults to 128 (Screenshot) Had to enable the MS servers as well under 'Tools > Options > Debugging > Symbols' in case anyone else is getting a bunch of `Cannot find or open the PDB file.` errors. Edited July 25, 2018 by saitei more testing done Link to comment Share on other sites More sharing options...
drcmclow Posted July 25, 2018 Share Posted July 25, 2018 (edited) hey just was thinking about a ambilight feature under the node pro - led strip section shouldnt this be possible with a small screen grabber running in the background? for example ambibox ( it also supports plugins) asus is releasing extra hardwore for this feature... u could add this right away without any extra hardware, just a set of corsair led strips...... i talked to the ambibox developer and he will look at it ... :D Edited July 25, 2018 by drcmclow Link to comment Share on other sites More sharing options...
Profezzional Posted May 31, 2019 Share Posted May 31, 2019 (edited) I hate to be that guy, but there's a typo in the SDK documentation (as of the version 3.0.234 release), on page 39 in the fields of 'struct CorsairLedPositions'. In CUESDK.h, the field is called "numberOfLed", while the PDF calls it "numberOfLeds". Even though it's a minor error and a programmer's first instinct should be to use the header file, it may throw someone else for a loop, and the plural form of the name makes more sense. Edited May 31, 2019 by Profezzional Version update 1 Link to comment Share on other sites More sharing options...
Recommended Posts