It’s voice coils all the way down, baby!

I think it’s valid for boosting raw 60fps to 120fps (or whatever your max refresh rate is) in games that aren’t super latency sensitive. Boosting something like 180 or 240FPS to 360 or 480 is probably valid for more latency sensitive things like competitive shooters since it would (theoretically) increase readability of motion at an imperceptible cost to latency.

Personally, I’d probably use multi-frame-gen only for boosting games that are capped at 60 and for games where I can stably reach 120 but no higher if I had a super high refresh rate monitor and the game provides good clean frames to start with (which is… Arguable in a ton of modern titles).

Using it to boost, like, 30->60 or higher, or even 45->90, is idiotic. The latency at native 30 is already annoying and at 45 is just barely pushing into the range where it’s less noticeable in casual play, so adding any latency is just a really bad trade.

HJKL for ◀️🔽🔼▶️ (Vi layout) under a thumb layer key.

Let’s me use at least the basic movement everywhere both in and out of (Neo)Vi(m) etc. Games excluded of course, I use WASD there (or ESDF if I know I’ll be playing a game long enough to justify remapping things)

Seems neat, though I don’t have a use for it.

It’d be much more helpful to me if it just used those OCR boxes to provide mouse-over dictionary lookups via yomitan rather than a translation.

Right now I use Google Lens for that, but that means I’m sharing selected text into a dictionary app or chatgpt, or gambling on Google search just giving me the JP->EN definition with no prompting besides the word itself.

If something’s marked unsupported I just double check ProtonDB before I buy it

As long as people more competent get control of the longer lived franchises.

NGL that block pattern thing is something I never really noticed but it makes a lot of sense. The messy way to do it in C++ would be with a lambda that you then just evaluate, but being about to avoid that and instead using standard scoping syntax for the same thing neat. I’m pretty sure I’ve even done this before without even thinking about it.

And if you put all of the definitions you need right at the top it’s super easy to split out into a function if/when you need it elsewhere

The only thing I dislike about it, having seen the in-store demos, is the fringing on text and hard edges. It can looks like chromatic abberation in very contrasty games. The OLED subpixel layout just isn’t quite ideal, especially at 1280x800 7.4".

The LCD version has less issues there. Less gaps between the pixels and a standard RGB vertical strip layout.