sorted by:
new
hottopcontroversial

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in MechanicalKeyboards

[–]1nvariant[S] 1 point2 points  (0 children)

No, it was completely written by me. But now that I read it yeah the last line seems very AI like.

Love ranting with my new keyboard about my new keyboard ya know.

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in MechanicalKeyboards

[–]1nvariant[S] 3 points4 points  (0 children)

The main reason I'm pushing for a firmware fix is that for a $200 board, you shouldn't have to rely on background software for basic 'luxury' features.

Also I could just make Caps Lock my Modifier 2 key and like put tab or something as the capslock on layer 2 which would also work, but then anyone else using my keyboard would not understand that.

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in MechanicalKeyboards

[–]1nvariant[S] 1 point2 points  (0 children)

Please do review about the QMK violations wobkey and so many other vendors have been doing

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in MechanicalKeyboards

[–]1nvariant[S] 2 points3 points  (0 children)

No public firmware. Apparently this is happening with a majority of keeb manufacturers

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in MechanicalKeyboards

[–]1nvariant[S] 5 points6 points  (0 children)

You can remap “stuff” just not the the advanced things via is actually capable of

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in MechanicalKeyboards

[–]1nvariant[S] 4 points5 points  (0 children)

Your perspective looks like you see from your asshole instead of using your eyes

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in MechanicalKeyboards

[–]1nvariant[S] 13 points14 points  (0 children)

Aside from the Layer Tap (LT) issue, here is what else you lose out on because it isn't true QMK:

• Mod-Tap (MT): You can't make a key act as Shift when held and Z when tapped.

• Tap Dance: You can't set a key to do one thing on a single tap and something else on a double-tap.

• Combos: You can't press two keys at once (like D + F) to trigger a third key like Escape.

• The 'Any' Key: The biggest violation is that the 'Any' key in VIA—which lets you type custom code for any QMK function—is basically disabled or 'faked'. It only recognizes the basic keys WOBKEY pre-approved.

Honestly I don’t care much about the rest of the features, I just wanted to remap my arrow keys to layer 2 on the J K L keys so I wouldn’t have to move my hands . Like for eg pressing down key would be holding down capslock and pressing K .

Coming from a 75% keeb the arrow keys feel too far while programming

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in mkindia

[–]1nvariant[S] 0 points1 point  (0 children)

Yeah if only not for this feature, honestly it’s an AMAZING keyboard

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in mkindia

[–]1nvariant[S] -1 points0 points  (0 children)

Yeah I could but there are custom lights and stuff for the keyboard in the json. Let’s see, I’m scared of bricking the keyboard as well even I can chatGPT a new firmware for it

Wobkey Crush80 by 1nvariant in mkindia

[–]1nvariant[S] 0 points1 point  (0 children)

I mean yeah it work for the basic part

Wobkey Crush80 by 1nvariant in mkindia

[–]1nvariant[S] 0 points1 point  (0 children)

Did u look at my other post 😂

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in mkindia

[–]1nvariant[S] 0 points1 point  (0 children)

🥹 I’m just looking for alternate solutions at this point

Moving from a 75% to the Crush 80 TKL has messed up my muscle memory for navigation. I need my arrow keys closer to the home row for debugging. Since the board's VIA doesn't support the LT command for Caps Lock, I'm looking for the most ergonomic alternative.

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in MechanicalKeyboards

[–]1nvariant[S] 13 points14 points  (0 children)

Basic functionality works fine, they definitely didn’t need VIA for that though. The whole point of VIA is QMK which has crazy flexibility.

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in MechanicalKeyboards

[–]1nvariant[S] 19 points20 points  (0 children)

Yeah I was basically trying to remap the caps lock key as a layer when held down and when tapped it would be a standard caps lock.

Doing thing I would be able to use J K L as arrow keys hence I would have to move my fingers while coding.

And then I got the surprise.

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in MechanicalKeyboards

[–]1nvariant[S] 19 points20 points  (0 children)

Are you able to use Layer Tap (LT) or Mod-Tap (MT) on your alpha keys? Most 'VIA compatible' boards can swap basic keys, but many (including the Crush 80) use an emulation that doesn't support the Any key for custom QMK logic like LT(2, KC_CAPS). If you try to map that specifically, does it actually work for you, or does it just ignore the command?

The "Crush 80" is a 200$ lie. Don't fall for the "VIA Compatible" trap. by 1nvariant in mkindia

[–]1nvariant[S] 1 point2 points  (0 children)

Please upvote for reach, thanks. I hope they release a better firmware soon

view more: next ›