Open Auretus opened 6 months ago
I checked the info.json
for this board, and the matrix values were basically copy-pasted from the one in crkbd/rev1
. The formatting is a bit screwy, but after parsing what was supposed to go where in terms of X-Y coordinates, nothing seemed to be out of place there.
Describe the Bug
KB model: Boardsource Unicorne OS: Windows 11 23H2 Software version: QMK latest, pulled from Github @ 2024-03-05 18:29 EST Build environment: QMK Toolbox
I'm seeing a weird thing happen with my Unicorne (Corne variant running on RPI2040), and I'm not sure what's causing it. When I enable any of the RGB matrix patterns, they mostly work as expected--mostly. The bit that's off: the pattern acts like the last column on the right-hand board is located on the far left of my left-hand board.
As with many split keyboards, the matrix is defined with the two halves on separate row numbers, to avoid confusion. Left hand uses rows 0-3, right hand uses rows 4-7
This happens on any animated RGB matrix effect, though I'll use the
RGB_BAND_VAL
effect as an example for clarity's sake.What I expect to see: a band of color going from left to right column by column, like this:
What I actually see:
The screwy thing is that reactive layouts like
TYPING_HEATMAP
and theSOLID_REACTIVE
set trigger their waves at the correct key location, while still displaying this weird wrapped-around boundary behavior for propagation.Furthermore, the static
ALPHA_MODS
pattern doesn't seem to do this, it correctly shows the thumb keys and the outermost columns (column 0 on left board, column 5 on right board) in a different color as expected. Every other pattern behaves this way though, AFAICT. (Hard to tell with the patterns likeCYCLE_ALL
andBREATHING
that play the same animation on every key in sync.)Keyboard Used
boardsource/unicorne
Link to product page (if applicable)
https://www.boardsource.xyz/products/unicorne-LP
Operating System
Windows 11 23H2
qmk doctor Output
Is AutoHotKey / Karabiner installed
Other keyboard-related software installed
WinCompose, Microsoft PowerToys Preview
Additional Context
Tested this with both my custom keymap/ruleset and the default, and the same behavior obtains in both places. EEPROM reset and reflash obtains similar results.