The framerates do seem a bit low to me, but box64 is emulating a 64-bit cpu on an arm cpu, right? So a very complex instruction set working on a risc chip. That’s quite the feat… and the frametimes look pretty stable. Looking forward to see this keep developing into the future!

I think the person upset about the anime girl on gitlab is pretty silly! “What if my girlfriend sees and thinks I’m into that?” It’s not inappropriate, it’s just a drawing. And if she’s that concerned for some reason, you could just explain?

That surprises me to hear that gamescope doesn’t have issues with it, seeing as it’s not designed for managing floating windows. Does the game implement its own window system, or does gamescope have a window system?

(Replying to myself) Even if these numbers are legit, we don’t know the process or exact metrics used.

This data may include falsely banned players on Linux (which was reported before they restricted Linux) and may exclude many cheaters on Windows (any of those who weren’t caught). We don’t know.

They tweeted this graph in early December:

[…] In this chart, we’re displaying the infection rate, or the rate of matches that had a cheater present. […]

Note how the graph is missing labels and how neither it nor the tweet include information on how these metrics were gathered.

If you’re feeling adventurous, you could compile Marlin yourself. I did it to use a pin as an “off” signal for my fans, but ended up tinkering with options like linear advance. The set up isn’t too hard, but you need vscode.