this post was submitted on 29 Nov 2025
239 points (99.6% liked)
PC Gaming
12798 readers
891 users here now
For PC gaming news and discussion.
PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates.
(Submissions should be from the original source if possible, unless from paywalled or non-english sources.
If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
AFAIK, yes, plus one more.
It can use FEX to run x86 binaries, or use ARM binaries directly in steam for games that have them (games that support apple silicon macs, for example) and it can sideload apks meant for android, if the apk is actually standalone, and doesn't have system dependencies that only exist on meta devices.
The game Valve used to demo the standalone capability, was Hades. The x86 version running on a virtual display, after just installing it via steam.
Apple silicon is weird. It uses 16k page files while most other things are set up for other files sizes.
I am aware; but I am specifically meaning VR games, not just PC games in general. And especially not something like Hades which I can't imagine performing poorly even if emulated on a cheap smartphone. How well would it run Alyx? VRChat? Beat Saber?
yeah I think this is really useful on steamframe. on the machine? hrmmm
I honestly wonder how much of this is just copied over from the functionality they wanted on the steamframe. because there it's a great, potentially fantastic tool, where as on the steam machine it's... interesting?
I'm not sure what you're saying here. Copied over from where to what? The Frame is the only ARM device in the lineup. The Steam Machine is x86.
I may have misread but I thought they were going both directions: arm chips that could execute x86 stuff via proton, and, x86 (whatever amd solution ends up in the machine) reading the APK side.