6.4.0 (Basic support for Alienware AW410/510k)

[T-Troll]

Important! If you are using tools for the first time, please read Beginner's guide and AlienFX-GUI readme to configure out it's concept and operation principle.

Important! If you are migrating from version 5.x.x.x, open application folder and run alienfx-conv to convert registry configuration. In case you don't do so, you lost your color and effect settings (forever), as well as haptics and ambient settings (until converted).

Changes into this release:

AlienFX-GUI:

• New: Basic support for APIv9 (Alienware AW410/510k). Basic support includes:
  • Simple button color set
  • Full keyboard lights on/off/dimming (only 10 grades supported for dimming by hardware)
  • Per-key and global effects not implemented yet
  • Keyboard profiles not implemented yet
  • See "Known issues" for more detail
• "Devices" tab - Deselected light color now set to black even if not assigned.
• Bug fixed: Exception then edit light name (Devices tab - i don't know, how it works before....)
• Bug fixed: Add/remove new device into USB does not trigger device's rescan.
• Bug fixed: Visual bug with tab selection (tab becoming white).
• Bug fixed: Incorrect selection into device/profile list at corresponding tab

Planned, but postponed to next release:

• For RGB keyboards, a light name can be assigned by pressing the corresponding key.
• KDL update

Known issues:

• 410/510k is so "smart" - at massive update, it accepts all updates, but then starting to play animation to randomly change light color to the assigned. Looks ok if you need to set static color, and terrible for dynamic changes. I'm working to disable this "feature".
• Wave from the last Windows 10/11 update - every 1-2 minutes, light updates freeze for 5-10 seconds (into Windows USB data preparation function). Seems like Microsoft bug, i report it and looking for fix.

---

This discussion was created from the release 6.4.0 (Basic support for Alienware AW410/510k).