CUE-SDK C# Wrapper (CUE.NET)

[Darth Affe]

I just published a new version (1.1.1)
https://github.com/DarthAffe/CUE.NET...ses/tag/v1.1.1

Nuget-packages are of course up2date.

[satukan]

I would like to ask, is this API allows to hook / capture the extra G buttons presses in a C# application?

[Darth Affe]

Well somehow. There is already a extension to do this (https://github.com/DarthAffe/CUE.NET.Input, but since I'm not sure if it works with all devices, I won't providing this as nuget or 'official' binary right now.

I attached you two zips:
The first is a demo application which allows you to test if the library works for you (I can't promise anything right now). Just run the keyboard test and you should get some sort of reactive typing.

The second is the current latest version.
To use it just reference CUE.NET.Input.dll and HidSharp.dll and install the CUE.NET nuget-package.
After adding the using "CUE.NET.Input" you should be able to register an input-handler by calling

CueSDK.KeyboardSDK.RegisterOnInput(MyKeyInputEventHandler);

the args passed to this provides the LedId and the Action (pressed or released).

You can also look at the example project - this is the code to the test-exe I attached.


If it works, it would be interesting to hear with which device you're using it!

[satukan]

Thanks Darth Affe, tried it out and looks like the SDK is initialized but there was no connection with the keyboard.
Probably cause of the targeted keyboard is a K95 vengeance (non RGB) type? Do you think the your shared SDK should work with it or another SDK belongs to it?

Meanwhile find a solution to set macros for the G buttons as "fake buttons" like F13 .. F24, but it's only 12 extra buttons and the rest of 6 still missing, so looking for something better.

[terabyte]

Originally Posted by satukan

Thanks Darth Affe, tried it out and looks like the SDK is initialized but there was no connection with the keyboard.
Probably cause of the targeted keyboard is a K95 vengeance (non RGB) type? Do you think the your shared SDK should work with it or another SDK belongs to it?

Meanwhile find a solution to set macros for the G buttons as "fake buttons" like F13 .. F24, but it's only 12 extra buttons and the rest of 6 still missing, so looking for something better.

The K95 non-RGB does not have any official SDK support. Not sure if there is an unofficial one around, but this wrapper for sure won't work with it.

[Darth Affe]

I just published a new version (1.1.2)
https://github.com/DarthAffe/CUE.NET...ses/tag/v1.1.2

Nuget-packages are of course up2date.

[DanteGrieco]

Hi, I just wanted to know if there was a way to integrate game detection and game variables to the SDK, such as getting the health of your player and making a health bar based off of that onto the keyboard?

[Darth Affe]

Originally Posted by DanteGrieco

Hi, I just wanted to know if there was a way to integrate game detection and game variables to the SDK, such as getting the health of your player and making a health bar based off of that onto the keyboard?

Well game detection/integration has nothing to do with the SDK.
Of course you can draw things like health bars with the SDK but you'd need to write your own game detection/integration to get the values you want to display.

[Darth Affe]

I just published a new version (1.1.3)
https://github.com/DarthAffe/CUE.NET...ses/tag/v1.1.3

Nuget-packages are of course up2date.

[yanhuayu]

what's this?

when i running

CueSDK.Initialize();

at CUE.NET.CueSDK.Throw(CorsairError error)
at CUE.NET.CueSDK.Initialize(Boolean exclusiveAccess)
at Corsair_Effects_Engine.Corsair_Effects_Engine.GetDevice() in c:\users\documents\visual studio 2017\Projects\Corsair Effects Engine\Corsair Effects Engine\Corsair Effects Engine.cs:line 22

my code:

public void GetDevice()
{
try
{
CueSDK.Initialize();
var keyboard = CueSDK.KeyboardSDK;
if (keyboard != null)
{

}
}
catch (Exception ex)
{

throw;
}

}

[Darth Affe]

Well the interesting line of the error (most likely the first) is missing but from what I can see it seems like there is a problem with your CUE.
Is CUE installed and running?
Is the SDK-support in CUE enabled?

[yanhuayu]

Originally Posted by Darth Affe

Well the interesting line of the error (most likely the first) is missing but from what I can see it seems like there is a problem with your CUE.
Is CUE installed and running?
Is the SDK-support in CUE enabled?

so i must install Corsair Utility Engine and running and enabled SDK-support in cue ?

[Darth Affe]

Originally Posted by yanhuayu

so i must install Corsair Utility Engine and running and enabled SDK-support in cue ?

Yes, otherwise you the SDK won't work.

[Apathy420]

Originally Posted by Darth Affe

Current version: 1.1.3

You'll always find the latest release on nuget https://www.nuget.org/packages/CUE.NET/ or (sometimes older) releases at https://github.com/DarthAffe/CUE.NET/releases/latest and the source at https://github.com/DarthAffe/CUE.NET

The documentation and examples still needs some work.
You can find the things I've done so far at https://github.com/DarthAffe/CUE.NET/wiki or the code-documentation at http://cue.wyrez.org.

Features:

• Full Control over the LEDs of your SDK-supported Corsair-Devices through a C#-API
  
• By-key-access to every supported led or grouping in regions/lists
  
• Comprehensive render-engine based on brushes to allow easy drawing over multiple leds.
  
• Effect-engine to animate brushes or groups of leds
  
• Currently in development: Input-module to capture all key-/button-presses (including G- and other special-keys)

Can I get an example on fading leds? I have tried setting a brush and adjusting the opacity of it. Doesn't work. I tried setting a color with different alphas and it doesnt fade. Help me out.

[Darth Affe]

Originally Posted by Apathy420

Can I get an example on fading leds? I have tried setting a brush and adjusting the opacity of it. Doesn't work. I tried setting a color with different alphas and it doesnt fade. Help me out.

The approach of changing the opacity is good, for me it sounds lie you didn't set a "background-color" so there is nothing to shine through that opacity.

CorsairKeyboard keyboard = CueSDK.KeyboardSDK;
keyboard.Brush = new SolidColorBrush(Color.Black); // Black background - this will allow the foreground to fade away
ILedGroup keyboardLeds = new ListLedGroup(device, device); // replace this if you don't want to fade all leds
keyboardLeds.Brush = // add your brush here and change it's opacity. Don't forget to call 'CueSDK.KeyboardSDK.Update()' afterwards or set the UpdateMode to Continuous to enable auto-updates