Support for Alternative Layouts
This is a summary of how alternative layouts have been supported by kits such as Colevrak and Homing. It is not a discussion of alt layout performance and development, but if that interests you I highly recommend starting with Pascal Getreuer’s A guide to alt keyboard layouts (why, how, which one?). It’s a concise and comprehensive overview with links to some great sites that go deeper. He also has a separate Links about keyboards page. The Keyboard layouts doc he recommends explains layout goals and metrics in detail, summarizing the alt layouts discussed here as well as more than one hundred others. Sculpted-profile The majority of custom keycap sets are sculpted-profile (Cherry, SA, MT3, KAT, etc. - more on profiles generally here) so let’s start there. Because each row has a unique keycap shape, alt layouts require a unique keycap for each legend that moves off its QWERTY row. At first there were two The Dvorak layout was patented in 1936 by August Dvorak & William L....
Apr 23, 2024
Also I have the stabilizer issue that was mentioned a while ago in a update we all received. My R2 Left Shift is sticking sometimes, and when it doesn't stick it just feels god awful to touch. Unlike every other stabilized key on the board ... I don't even know if I'm getting the replacement plate from the manufacturing issues but that would mean I just paid over 200 to fix a problem that shouldn't have existed in the first place. Not entirely disappointed, but wtf am I supposed to do ...
Just a guess, but on a personal build I used costar stabilizers, unless they're lubed they tend to stick more often and feel like shit. These two stabilizers on the left shift, are not lubed at all, but the other stabilized keys are. I can probably lube them but that means I have to buy some. Small input on what is probably just another classic Massdrop QC problem.
Edit: To attempt to address the issue with the keyboard randomly not being detected by windows, I checked the Device Manager and it's showing as Unknown USB Device (Device Descriptor Request Failed). It's now in a unflashable state even after hitting the flash button on the pcb. Zadig is showing that there isn't even a Driver for the usb and fails to install one saying "Resource already exists". I'm at a loss with wtf I'm supposed to do with this broken ass keyboard. And no support is coming from anywhere ...
Edit 2: After plugging and unpluging, I can get it into it's original state, but then randomly windows will again shows it's a unknown usb device. Even after getting the driver to install on Zadig, the Kiibohd DFU Flasher returns a code 74 and doesn't flash anything.
Edit 3: By some miracle I got the driver installed and the layout flashed that I was wanting. But it still hasn't solved this fucking issue with the Usb Unknown shit. I took the case apart and checked the pcb, it's totally fine from everything I can see. Plug it in, no case on, can't get Windows to recognize it. Put the case on, plug it in, it's recognized, then I move the board and BOOM windows no longer recognizes it. It may be a physical thing on the pcb ?? Maybe a bad usb port ?? I tried 2.0 and 3.0 both giving the same results ...
Edit 4: I'm definitely suspecting a "static shock" death somehow, as the board will sometimes be recognized totally fine, but the second I jiggle or move it then it becomes a USB Unknown Device essentially just shutting down. I've been issued a return label to receive a new board, great ... hope no one else has to deal with this shit.
It does sound like you just need to reflash a different firmware though, maybe start with the stock QMK firmware for the board and work from there.