I use a keychron Q3 and Q0. They can be remapped / programmed through a web (chrome derivs as it requires WebHID) or desktop electron app called VIA, which at the time of writing is proprietary. I believe Vial (written in Qt) is being brought up, so that may be an option in the future.
In terms of managing the firmware, the vendor offers a first party web interface (also leveraging WebHID). The QMK Toolbox GUI is only available on Mac and Windows but you can use the CLI on Linux to get into DFU mode and flash your firmware.
Not really keen on Logitech as a company but I use Piper to program several of their G series mice on Linux. You can check the libratbag support list to see which hardware can work with it.
I see. You can temporarily edit your grub before the OS loads. This should afford you the opportunity to boot into the system without EDID modifications, though im not sure if your modified EDID will still load under this scenario. If so, you may need to switch into a CLI session to undo your changes.
I'm sorry to hear that. Does this system only have access to this single display? Did you use a kernel command to modify your EDID? If so, are you able to temporarily modify your grub before booting into the OS?
Archwiki references a [@<refresh>] (presumably denoted as [@144] for something like 144Hz) property, hopefully that's all you should need to define, though I'm not sure if you'll need to manually recalculate vertical and horz timings or something.
naw unfortunately not. It's kind of crazy that they nestle each individual engine within a wrapper. I'm not sure of this brings the api level to d3d11, or if they had to work to bring each engine up for that. Somewhat explains why MCC as a whole was so difficult to back port improvements to, like configurable FOV and weapon model placements, frame rate unlocking and interpolation, custom keybinds, missing assets and such.
it's kind of interesting seeing the player models rendered in UE when you use the customisation menus; everything looks so glossy and odd.
The 'wrapper' around each of the individual halo engines is in unreal and is arguably the wost thing about the collection from a reliability standpoint.
That said, they'd definitely be able to find people suited for the work, provided said people agent already scared away by stories of the work culture at 343i / MS
I use a keychron Q3 and Q0. They can be remapped / programmed through a web (chrome derivs as it requires WebHID) or desktop electron app called VIA, which at the time of writing is proprietary. I believe Vial (written in Qt) is being brought up, so that may be an option in the future.
In terms of managing the firmware, the vendor offers a first party web interface (also leveraging WebHID). The QMK Toolbox GUI is only available on Mac and Windows but you can use the CLI on Linux to get into DFU mode and flash your firmware.
Not really keen on Logitech as a company but I use Piper to program several of their G series mice on Linux. You can check the libratbag support list to see which hardware can work with it.