I’ve had a GMMK pro for a while. Never cared to remap the volume rotary, and 1.x software seemed fine.
Just bought a GMMK Numpad, and one of the first things I went to do was remap the (now duplicate) volume knob… oh you can’t. Okay cool I guess, I’ll just remap the volume slid… oh… you can’t do that either. So you have two hardcoded volume controls on an ancillary to a peripheral that already has a hardcoded volume control…
… and it’s been pointed out months ago: We have to talk about Core 2.0 and surely internally well before that. And at the time a rep said it was being worked on…
I don’t want to be a negative nancy, but wtaf is the software product team doing? 2.1 is worse than 2.0. The aforementioned numpad volume sliders and knob at least worked previously. Now on 2.1 they do not… How do you not regression test that kind of stuff?
I’m not going to pretend I begin to understand what’s going on behind the scenes to produce software this bad from an otherwise good company, but someone higher up should take charge; the bad software is going to tank your business and the great work the hardware team does.
At an absolute minimum write some more automated regression tests on the software side for the love of all that is holy.