On Steam Frame (ARM64), x86-64 Windows titles run under the translation layer. For at least one title, Steamworks achievements never unlock and Steam Cloud saves never transfer, while Steam playtime tracking continues to work normally.
Affected title
App ID 2482940 — Little Nightmares VR: Altered Echoes
Store metadata reports platforms: { windows: true, linux: false }, i.e. an x86-64 Windows build with no native Linux build — so on Frame it necessarily runs under translation
The title declares 21 achievements and Steam Cloud in its store categories (appdetails categories 22 and 23)
Steps to reproduce
On Steam Frame, install app 2482940 and launch it locally (not streamed).
Play from start through completion.
Observe: 0 of 21 achievements unlocked.
Separately, launch the same title on a Windows PC (native, no translation).
Observe: no cloud save is present; the title starts as a brand-new save.
Expected behaviour
Achievements unlock on progression and sync to the Steam profile.
Cloud saves written on Frame are restored when the same title is launched on PC.
Evidence that this is the translation path rather than the title
The title's achievements work correctly for other players. Steam global achievement percentages for app 2482940:
Achievement
Global unlock
CompleteTransmission (opening)
64.9%
CompleteSchool
45.5%
CompleteTrainStation
37.0%
CompleteMansion
31.0%
GameComplete
29.8%
Ten of the 21 achievements are simple progression/completion milestones. A verified full playthrough returning 0/21 is therefore not explainable by player error — the unlock calls never reached the Steam client.
Playtime tracking works, but in-process Steamworks calls appear to be dropped. Hours accrue correctly on Frame. Playtime is tracked client-side by the Steam client observing the process. Achievements (ISteamUserStats) and cloud saves (ISteamRemoteStorage) instead require in-process Steamworks API calls from the game. Client-side tracking succeeding while both in-process interfaces fail is the characteristic signature.
This does not appear to be title-specific. Another Steam Frame owner reports the identical cloud-save symptom for Beat Saber and Red Matter — saves shown as "up to date" on both the Frame and the PC, but the save data never actually transfers — while I Expect You To Die worked without issue. That suggests an intermittent, platform-wide failure rather than a single bad title.
Environment
Device: Steam Frame
SteamOS version: 0.4.5 — the stable "SteamOS 0.4 for Steam Frame" release (published 2026-10-08), not a beta build
Title runtime: Windows x86-64 build under Proton / x86-on-ARM translation
Questions
Are achievements and Steam Cloud currently expected to be unreliable for x86-64 titles running under ARM translation on Frame?
Is there a supported workaround to force a Steam Cloud upload from Frame to PC in the interim?
Would logs from a reproduction attempt (e.g. PROTON_LOG=1) be useful for narrowing where the Steamworks bridge breaks?
Summary
On Steam Frame (ARM64), x86-64 Windows titles run under the translation layer. For at least one title, Steamworks achievements never unlock and Steam Cloud saves never transfer, while Steam playtime tracking continues to work normally.
Affected title
platforms: { windows: true, linux: false }, i.e. an x86-64 Windows build with no native Linux build — so on Frame it necessarily runs under translationSteps to reproduce
Expected behaviour
Evidence that this is the translation path rather than the title
The title's achievements work correctly for other players. Steam global achievement percentages for app 2482940:
CompleteTransmission(opening)CompleteSchoolCompleteTrainStationCompleteMansionGameCompleteTen of the 21 achievements are simple progression/completion milestones. A verified full playthrough returning 0/21 is therefore not explainable by player error — the unlock calls never reached the Steam client.
Playtime tracking works, but in-process Steamworks calls appear to be dropped. Hours accrue correctly on Frame. Playtime is tracked client-side by the Steam client observing the process. Achievements (
ISteamUserStats) and cloud saves (ISteamRemoteStorage) instead require in-process Steamworks API calls from the game. Client-side tracking succeeding while both in-process interfaces fail is the characteristic signature.This does not appear to be title-specific. Another Steam Frame owner reports the identical cloud-save symptom for Beat Saber and Red Matter — saves shown as "up to date" on both the Frame and the PC, but the save data never actually transfers — while I Expect You To Die worked without issue. That suggests an intermittent, platform-wide failure rather than a single bad title.
Environment
Questions
PROTON_LOG=1) be useful for narrowing where the Steamworks bridge breaks?