Since I posted this in another thread, I might as well post it here too
Running “Portal 2” on a Qualcomm Snapdragon X laptop - Lenovo Yoga Slim 7x.
Runs better than on a Asahi M.2 16Gb with Fedora remix.
3 Likes
It works ! When updating I choose to overwrite the config.json with the one from the snap edge package.
Half life 2 launches. I got issue with HL2 and fractional scaling and mouse cursor position but might be related to other issue.
I tested also the outer worlds, it takes time to load but it works well except from some sound synchronization issues during cinematics.
1 Like
Awesome, glad to hear it’s working now!
We found that adding PULSE_LATENCY_MSEC=50 as a per-game launch option (within the Steam properties page for the impacted game) improved some sound issues with a few games, specifically if you’re hearing the sound cut out intermittently. Might be worth a shot if that sounds similar to what you’re hearing in The Outer Worlds.
I can confirm it also works with older Snapdragon chips. I tested it on a Radxa Dragon Q6A with Snapdragon QCS6490, Armbian based on Ubuntu Noble, kernel 6.18.8.
I didn’t see a difference in performance without thunking, compared to a manual installation of Fex with thunking. I have the suspicion that Fex doesn’t have the GPU drivers in the RootFS, and just uses llvmpipe. And that was why I was looking for thunking, as it makes a big difference with a manual installation of Fex. It might still make sense to use thunking, as I do have the impression that it lowers the memory footprint.
Enabling thunking for OpenGL breaks things. I can enable drm and Vulkan.
With thunking for OpenGL I see this error:
Adding process 3893 for gameID 220
Opening host-side X11 display: 0xaabfdfa0 → 0xffdc9000
SDL video target is ‘x11’
SDL video target is ‘x11’
Failed to create SDL window: Couldn’t find matching GLX visualGame Recording - game stopped [gameid=220]
I also tested it on the Radxa Rock 5B Rockchip RK3588 SBC. I was able to start a game, but performance was horrible. I guess it really needs the panthor driver in the snap package.
How often should we expect updates to the included mesa build in the RootFS?
Installation failed on Raspberry Pi 5 with
Copying default FEX config to /home/pi/snap/steam/common/fex_config/
<jemalloc>: Unsupported system page size
<jemalloc>: Unsupported system page size
<jemalloc>: Unsupported system page size
due to 16k page size. Opening steam kept failing after switching to 4k pages. Steam needed to be removed and re-installed.
I think it would greatly improve UX if the setup checks for 4k pages, fails with a clear error message and allows the setup to be re-started/continued without re-install.
I’m trying not to lag too far behind kisak-mesa fresh, but since this is best-effort, we might not always update ours immediately when that PPA gets an update. It’ll really depend on whether we observe any issues on any of the devices that are currently known to work with this snap, since we want to avoid regressing those.
So, I’d say every couple months is a reasonable guess (but may vary depending on the nature of each update in kisak-mesa fresh).
1 Like
I think it would greatly improve UX if the setup checks for 4k pages, fails with a clear error message and allows the setup to be re-started/continued without re-install.
Thanks for the suggestion - added to my todo list 
1 Like
Any chance you can integrate muvm to enable support for Asahi?
While it would be ideal if we could enable this on 16k page size platforms, implementing the microVM within snap confinement would be a very substantial task (which we are not entirely sure would even be feasible with strict confinement in the end) - so unfortunately, 16k page size enablement is not in our scope.
is there a word on RPI fix?
No ETA on RPi at the moment. I had to prioritize some other work items this week, but that is still on my radar.
3 Likes
Hello, this is my first post on here, thank you so much for the work you’re putting in this, I can confirm the Snap (Edge version) currently does work on the Raspberry Pi 5 8GB (4k pagesize), I’ve been able to get Half-Life Opposing Force to work between 15 up to 33 FPS, only the night vision drops performance massively when enabled, before this the Pi-Apps version of Steam could not run the game at all (constant flashing and single digit FPS) and the client itself was unstable (now also fixed thanks to the native one). Even Proton Experimental is working for some older games and many 2D Unity games that have a native Linux build run flawlessly already.
2 Likes