[0.15.38] Razer Deathstalker unsupported

[glek]

Now, before people bring it up, I am aware that the Deathstalker Chroma support is much less complete than other Razer keyboards. Individual key lighting is not supported by the Deathstalker, instead this model of keyboard has three color "zones" (keypad, normal keys, and the directional/extra keys). With that in mind, though:

What did I do?

• Started Factorio after Chroma support was added in the last experimental update.

What happened?

• My mouse pad and mouse both changed over to orange for the loading screen, lighting up as expected as the loading bar progressed.
• My keyboard did nothing, keeping its old settings of the "wave" pattern.

What would I expect to have happen?

• My keyboard would at least function as my mouse and mouse pad would for loading bars (I know it supports this from another Chroma-enabled app I use)
• My keyboard would display some of the behaviors described in the Chroma support (flashing on damage or research complete) but not others that it clearly wouldn't support (health "bar" in the function keys).

Other Notes/Attachements

• Reproducible: 100% of the time.

Log File

0.000 2017-11-25 08:45:01; Factorio 0.15.38 (build 30936, win64, steam)
0.000 Operating system: Windows 10 (version 1607)
0.000 Program arguments: "E:\SteamLibrary\steamapps\common\Factorio\bin\x64\Factorio.exe"
0.000 Read data path: E:/SteamLibrary/steamapps/common/Factorio/data
0.000 Write data path: C:/Users/roblo/AppData/Roaming/Factorio
0.000 Binaries path: E:/SteamLibrary/steamapps/common/Factorio/bin
0.006 System info: [CPU: Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz, 4 cores, RAM: 16325MB]
0.007 Display options: [FullScreen: 1] [VSync: 1] [UIScale: 100%] [MultiSampling: OFF] [Screen: 255] [Lang: en]
0.008 Available display adapters: 1
0.008 [0]: \\.\DISPLAY1 - NVIDIA GeForce GTX 970 {0x05, [0,0], 1920x1080, 32bit, 60Hz}
0.009 Create display on adapter 0. Size 1280x720 at position [310, 162].
0.146 Initialised Direct3D:[0] NVIDIA GeForce GTX 970; driver: nvldumdx.dll 23.21.13.8813
0.148 Video memory size (dedicated video/dedicated system/shared system/available): 4058/0/8162/4088 MB
0.191 DSound: Starting _dsound_update thread
0.191 DSound: Enter _dsound_update; tid=14076
0.192 Device reset internal.
0.195 Desktop composition is active.
0.195 WARNING: You have vsync and desktop composition enabled on Direct3D. Consider disabling vsync to increase performance on some configurations.
0.195 Graphics settings preset: very-high
0.195 Graphics options: [Graphics quality: high] [Video memory usage: all] [Light scale: 100%] [DXT: false] [Shader: 1]
0.341 Razer Chroma Controller initialized.
0.452 Loading mod core 0.0.0 (data.lua)
0.459 Loading mod base 0.15.38 (data.lua)
0.557 Loading mod base 0.15.38 (data-updates.lua)
0.619 Checksum for core: 2924902677
0.619 Checksum of base: 1503927233
0.864 Info PlayerData.cpp:58: Local player-data.json available, timestamp 1511563903
0.864 Info PlayerData.cpp:65: Cloud player-data.json unavailable
1.011 Loaded shader file E:/SteamLibrary/steamapps/common/Factorio/data/core/graphics/shaders/game.cso
1.012 Loaded shader file E:/SteamLibrary/steamapps/common/Factorio/data/core/graphics/shaders/zoom-to-world.cso
1.023 Initial atlas bitmap size is 16384
1.044 Created atlas bitmap 16384x16381
1.538 Created atlas bitmap 16384x1262
1.568 Created atlas bitmap 16384x3181
1.637 Created atlas bitmap 16384x4758
1.744 Created atlas bitmap 8192x1912
1.766 Created atlas bitmap 8192x800
1.774 Created atlas bitmap 8192x2028
11.888 Sprites loaded
11.888 Convert atlas 8192x1912 to: mipmap
11.978 Convert atlas 8192x800 to: mipmap
12.100 Convert atlas 8192x2028 to: trilinear-filtering
12.748 Loading sounds...
14.548 Custom inputs active: 0
14.585 Factorio initialised
258.785 Device reset external.
6026.156 Device reset external.
6094.698 DSound: Stopping voice
6094.698 DSound: Joining thread
6094.703 DSound: Exit _dsound_update; tid=14076
6094.703 DSound: Waiting for voice to stop ... signaled
6094.703 DSound: Joined thread
6094.703 DSound: Destroying thread
6094.703 DSound: Thread destroyed
6094.703 DSound: Releasing buffer
6094.703 DSound: Voice stopped
6094.703 DSound: Deallocating voice
6094.703 DSound: Deallocated voice
6094.756 Steam API shutdown.
6094.785 Razer Chroma Controller un-initialized
6094.785 Goodbye

[Twinsen]

I use their generic keyboard API that is supposed to adapt for each keyboard.

If Deathstalker is not affected by that API, I will have to implement support for it manually, so this is more of a feature request.

[glek]

Might I suggest looking at this Github repository? In particular, this chunk of code which seems to be where the difference between the generic keyboards and the Deathstalker Chroma comes into play. It doesn't seem terribly complicated to support the Deathstalker, but it does prove that the Deathstalker is not supported by the generic Chroma APIs.