You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the documentation, the heatmap RGB matrix effect should normally light up a key and its neighboring keys when pressed. (I don’t understand why it’s designed to also light up neighboring keys in the first place, but that’s not the point of this issue.) The problem is that for quite a number of keys, it will not light up the neighboring keys, but a few keys on the opposite side of the board instead – I does this in a consistent manner, but I cannot see a pattern.
I have found buggy keys like this in every row except the home row. For example the Y key will light up Y, U, H and J as expected (using a standard QWERTY layout here), but then also the first and second key in the bottom row (instead of T and G). I could post more detailed information regarding the other keys if needed, but about a third or so of the keys behave weird like this.
Is this a known issue? Does it also affect other boards? I know it affected me ever since I go the keyboard a few years ago, but I couldn’t find other people mentioning this issue online.
I personally don’t really care so much if this will be fixed or not, because I usually don’t use the heatmap effect. (Maybe I will after it gets fixed, who knows.) Unfortunately I don’t know how to fix this myself, as I have only ever used the predefined lighting effects and haven’t looked into how individual LEDs are addressed by the firmware.
The text was updated successfully, but these errors were encountered:
This is a known limitation on how that effect is coded. "Fixing" this will require someone to rework the maths in the heatmap effect to use physical 224 x 64 LED location values.
Describe the Bug
According to the documentation, the heatmap RGB matrix effect should normally light up a key and its neighboring keys when pressed. (I don’t understand why it’s designed to also light up neighboring keys in the first place, but that’s not the point of this issue.) The problem is that for quite a number of keys, it will not light up the neighboring keys, but a few keys on the opposite side of the board instead – I does this in a consistent manner, but I cannot see a pattern.
I have found buggy keys like this in every row except the home row. For example the Y key will light up Y, U, H and J as expected (using a standard QWERTY layout here), but then also the first and second key in the bottom row (instead of T and G). I could post more detailed information regarding the other keys if needed, but about a third or so of the keys behave weird like this.
System Information
avr-gcc (GCC) 5.4.0
arm-none-eabi-gcc (15:9-2019-q4-0ubuntu1) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]
Additional Context
Is this a known issue? Does it also affect other boards? I know it affected me ever since I go the keyboard a few years ago, but I couldn’t find other people mentioning this issue online.
I personally don’t really care so much if this will be fixed or not, because I usually don’t use the heatmap effect. (Maybe I will after it gets fixed, who knows.) Unfortunately I don’t know how to fix this myself, as I have only ever used the predefined lighting effects and haven’t looked into how individual LEDs are addressed by the firmware.
The text was updated successfully, but these errors were encountered: