Vik

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.

Maybe this can help fill in any gaps

https://tomverbeure.github.io/video_timings_calculator

You want to look into modifying your display EDID.

I don’t believe there’s a GUI for this on Linux but this post referencing the Archwiki might come in handy

https://foosel.net/til/how-to-override-the-edid-data-of-a-monitor-under-linux/

they’re trying to ensure an acceptable UX with their browser.

I suppose the root of the issue is developers specifically targeting and testing on chrome.

I don’t understand how this would make Firefox look bad unless you’re pointing at the dire browser share situation.

it do be that way :(

Their latest microcode update from 7 days ago was declared as final. Time will tell about the efficacy of the most recent fixes.

Unfortunately it may only be available via board partners as beta BIOS updates at present.

Isn’t this the kernel driver included by default?

I see, appreciate the info. I’ll have a poke around on fedora later today

Oh right. Do you have a distro specific example of this?

You shouldn’t need to install anything for the amd gpu

I’ve been lucky enough to dumb guy my fedora install since 28, and it’s been pretty decent to me. Granted I’m not using nvidia graphics, and I feel like that could throw a big spanner in the works for regular users. It’s a big enough leap getting into the mindset of installing software from Distro repos rather than directly from the vendor.

I hope the newer nv open kernel modules don’t stay out of tree. Also hope that NVK will give users the ability to just plug and play with mesa drivers in the future.

Perhaps they were looking at people using SnapTap and similar technologies, which were recently banned in CS2.

I feel like analogue / hall effect switches can lend a player a substantial advantage in apex when it comes to strafing. I wonder if they’ve tried to mitigate that.

Glad to hear it!

That would be interesting. I wonder if the internals would allow for the use of the PCIe 2.1 > m.2 for a 5G module but that’d rinse the battery

small update - there’s been a minor (17.4 MiB) patch to Apex since. Could be worth checking in with it to see if it has resolved linux compat,

Edit - it’s working for me on Fedora 40 Workstation. NB that I’ve never hit the original anticheat issue to begin with, and I use the following launch command to run the game under VKD3D (mostly AoT shader compilation) along with suppressing launch splash screens / videos and presenting Mangohud

mangohud %command% -novid -anticheat_settings=SettingsDX12.json

Edit 2 - tested again this morning and still working fine. I think you folks are good to go.

A week ago they made an announcement referring to anti cheat improvements. Today, a couple of friends on Windows noted that the game no longer launched with AutoHotKey enabled (no malicious use cases, just using 60% keyboards) as of last night’s minor update.

Since the game is deck verified, I’d expect respawn will resolve this soon enough.

Yikes I wasn’t aware of the second part