⨯ Did you know we have a Forum? Come and say hi to the wider community!

FEX code cache enabled for Proton Experimental (ARM) to improve frame timings

| Last updated: 28 Sep 2026 at 7:47 am UTC
By

Valve have upgraded Proton Experimental (ARM) with a feature that should hopefully improve some frame timings for devices like the Steam Frame.

Developer Pierre-Loup Griffais mentioned on Bluesky:

"The FEX code cache is now enabled on Proton Experimental (ARM), and should exhibit improved 1%-low frame times, especially over subsequent runs."

The FEX code cache is now enabled on Proton Experimental (ARM), and should exhibit improved 1%-low frame times, especially over subsequent runs.

What is FEX? FEX allows you to run x86 applications on ARM64 Linux devices, similar to qemu-user and box64. It offers broad compatibility with both 32-bit and 64-bit binaries, and it can be used alongside Wine/Proton to play Windows games.

What is the FEX code cache? In simple terms - it's basically a place where FEX keeps the ARM64 machine code it generates after translating x86 code, so it doesn’t have to keep doing the same translation work repeatedly. So with a cache it can read it should hopefully improve game start-up times and help with stuttering. It can't make a cache for everything though, but it's one tool in the box to improve things.

As expected, Valve will keep improving things like FEX, Proton, SteamOS and more that will make the Steam Frame better as times goes on.

Article taken from GamingOnLinux.com.
12 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
All posts need to follow our rules. Please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Readers can also email us for any issues or concerns.
3 comments
MayeulC 28 Sep 2026
I wonder if they will put in place some infrastructure to share the cache among multiple users, like they do for shaders. It is a bit more tricky to secure correctly (I could submit arbitrary code, and boom, you get an RCE vulnerability), but I think it could be dine with a few server-side checks. Or even perform server-side translation and have clients submit the original x86 opcodes.
Taros 28 Sep 2026
User Avatar
Quoting: MayeulCI wonder if they will put in place some infrastructure to share the cache among multiple users, like they do for shaders. It is a bit more tricky to secure correctly (I could submit arbitrary code, and boom, you get an RCE vulnerability), but I think it could be dine with a few server-side checks. Or even perform server-side translation and have clients submit the original x86 opcodes.
Wait..Those downloaded shaders come from other users?
Pyretic 5 Oct 2026
Quoting: TarosWait..Those downloaded shaders come from other users?
Pretty much, making it future proof for all future GPUs.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon Logo Patreon. Plain Donations: PayPal Logo PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register