I didn't know about `DXVK_CONFIG` before. It's the DirectX-Vulkan translation layer with its own framebuffer and latency.
I also manually disabled vsync in the game's `local.cfg` XML file.
I love where "gaming on Linux" is going. But I have the feeling the hype on Youtube etc. is in part created by content creators, and doesn't faithfully represent the actual situation (surprise!).
This hits a very soft spot for me. My beloved Spelunky 2 has huge input lag "on Linux", which makes it unplayable for me. It's pretty much the reason I keep my Windows 10 install around. I could not come up with a configuration on Linux that avoids the lag.
It's extra infuriating that online sources report the game running flawlessly but seem to ignore input lag.
It seems to not support 24h? When I see e.g. 17:35 I want to type 17:35 instead of 5:35. Probably because I very seldomly see 5:35 in real life! Interesting observation by itself, but slightly annoying that I have to convert to 12h for this game.
This is a common thing to say, but when during the development of human civilization has this actually been the case? Is agriculture designed around humans more than hunting/gathering? Is industrialized work more designed around humans than agrarian society?
I don't mean to sound pessimistic or technocratic; quite the contrary. But I think we shouldn't project our desire for equanimity onto romantized versions of civilization.
I can only comment about battery life. It's proportinal to how much tailscale is really being used: If you use tailscale with an "exit node", i.e. all traffic is routed through it and it's working continously, it drains battery. If it's only used for services on your tailnet, e.g. Immich, the impact will be very small.
Interesting! It reads to me like Apple advertises AAC-ELD only for Facetime though?
And the alternative, newer "Bluetooth high quality recording" I mentioned in sibling comment is not recommended for real-time communication due to increased latency.
So the situation seems to be more complex than I thought. But I stand by my original sentiment: I dislike the prevalence of bad-sounding Airpods in meetings.
They use hardware tricks (beamshaping) and software tricks (audio processing) to get as much out of them as possible, and they do sound better than generic cheap Bluetooth earbuds, but the Bluetooth connection is still the bottleneck.
They did announce a special "high quality recording mode" for Airpods in iOS 26 (which I didn't know, so thanks) but I couldn't find much except their developer announcement. It's not documented and I don't have the feeling it's being used.
> Note that this is the default for better quality (Bluetooth spec, not Linux).
Yeah, I have the impression most people assume Apple magically solved sound/mic quality in bidirectional mode. Or they just don't care. In any case, I'm unhappy about how much Airpods are used for meetings. They sounds so much worse than any wired mic! Or your laptop's mic, as long as you're not using the speakers.
His long list of conditions is an interesting read. It comes off as arrogant in places, but I guess if you really travel a lot and have unusual requirements it's best for everyone to be upfront about it!
The tomography was done at a synchrotron (ESRF), and with beamtime being very expensive it would be a net-negative to scan lottery tickets, unfortunately...
There have been Issues on Github about the same problem since April. I'm using Codex a lot and I'm very happy with its performance (UX and output), but it's baffling they haven't fixed this problem.
I like it a lot, but unfortunately you can cheat a bit: there are always two opposite answers and two unrelated ones. The correct answer is (almost?) always one of the opposites.
I didn't know about `DXVK_CONFIG` before. It's the DirectX-Vulkan translation layer with its own framebuffer and latency.
I also manually disabled vsync in the game's `local.cfg` XML file.
I love where "gaming on Linux" is going. But I have the feeling the hype on Youtube etc. is in part created by content creators, and doesn't faithfully represent the actual situation (surprise!).