November 7, 2026
3276245-0-48899500-1794071475-image_d9d7c6.png

“Caching FEX code is vital for frame-time consistency,” Valve software engineer Pierre-Loup Griffais told PCWorld in an interview. “In the future, it will also be integrated with Steam’s Pre-Caching feature, so that cached code is available even before the first local run of an app.”

It’s a neat trick when you’re trying to get thousands of Windows games to run on processors they were never designed for. And it fits with a broader industry push to eradicate one of PC gaming’s most infuriating problems.

Translate games smoothly

FEX is a crucial piece of Valve’s ambitious effort to free Steam from traditional gaming PCs. Most Windows games are designed for x86 processors from AMD and Intel. Arm chips speak a different instruction language, so FEX translates x86 code into Arm instructions as games run.

Fortunately, FEX doesn’t have to translate everything.

“When given a suitable ARM runtime environment, such as when integrated with Proton ARM, FEX only translates the application’s CPU code,” Griffais explained.

Foundry

Proton, Valve’s Windows compatibility layer, may switch to native Arm execution at the Win32 API boundary. The operating system and graphics drivers also run natively, allowing FEX to focus on the game’s CPU instructions.

Avatar photo
Written by

Miraj

**Miraj**

Miraj is a writer and contributor at LFTS, creating informative and engaging articles across news, technology, business, lifestyle, and current topics. He enjoys researching new developments and turning complex information into clear, reader-friendly stories. Through his work, Miraj aims to provide valuable, reliable, and interesting content for the LFTS audience.

Leave a Reply

Your email address will not be published. Required fields are marked *