search

CorsairOfficial / cue-sdk-python

Ctypes-based iCUE SDK binding for Python
MIT License
66 stars 13 forks source link

events.py example file glitch. #15

Closed TheTheoM closed 2 years ago

TheTheoM commented 2 years ago

events.py example file does not recognise K95 keyboard events after ICUE update. It recognises unplug/replug but no g key inputs.

intrueder commented 2 years ago

@TheTheoM may I know how many keyboards are connected to your PC? Can you share a list of devices displayed on the iCUE home tab?

TheTheoM commented 2 years ago

H100 plat. comman pro, LNC, LNP, k95P, glaive, vengeance. 1 keyb.

TheTheoM commented 2 years ago

When i run the py, it shows in icue as connected.

intrueder commented 2 years ago

Well, it's weird.. have you tried restarting iCUE (click "Quit" in the system tray icon menu, and start again)? Because there is nothing we can do on the SDK side. Example of output with the latest iCUE and SDK versions:

Working... Press any G/M key or connect/disconnect Corsair device to see events in action
Press 'q' to close program...
Event: CorsairEventId.KeyEvent
 Device id: 69c529e9ec734c3651beb9301850bbc8
    Key id: CorsairKeyId.Kb_G1
 Key state: pressed
Event: CorsairEventId.KeyEvent
 Device id: 69c529e9ec734c3651beb9301850bbc8
    Key id: CorsairKeyId.Kb_G1
 Key state: released
intrueder commented 2 years ago

Hi @TheTheoM, I can confirm now, that there is an issue in iCUE. It depends on a set of devices connected to a PC. The issue has been introduced in iCUE v4.24, and is not yet fixed. I think the best option, for now, is to downgrade iCUE to v4.23 and use it until the issue is fixed.

intrueder commented 2 years ago

Hi @TheTheoM , I'm closing this as iCUE v4.28 has fixed the issue