How to read this tracker
Approximately Up is a live Steam product whose ship systems, missions, platform compatibility, and community features can change after release. This page separates a verified release checkpoint from player-facing details that must be rechecked in the current client. A date in the timeline is not permission to carry an old value forward forever; it tells you when the source was checked and what the source actually established.
When you see a change that affects a guide, look at the affected task before changing the whole site. A new engine, station, mission, or input behavior belongs in the relevant Builds, Planets, Missions, or Systems page first. Keep the update entry concise: date, official source, what changed, and which evergreen page needs review. Do not turn a rumor, community guess, or store tag into a patch note.
2026-08-06 - Base game release checkpoint
Type: Release milestone
The canonical Steam Store page lists Approximately Up as released on August 6, 2026. The page identifies Approximately Games as developer and publisher and describes single-player or online co-op flight with up to four players. It presents the released base game as a modular ship-building adventure in which players explore 15 planets, reach planet stations, complete challenging objectives, collect components, and rebuild new ships.
- Source: Official Approximately Up Steam page
- The current listing includes Steam Achievements, Steam Workshop, Steam Cloud, and Family Sharing.
- The listed Windows requirements are part of the current Store snapshot; recheck them after future updates.
- No semantic version or default-branch patch label was copied because none was publicly stated in the audit.
The release checkpoint is useful for identity and scope, not for every detailed mechanic. A player asking how a controller, sensor, solar panel, engine, station, payload, or co-op lobby behaves should still be directed to the current game. A player asking whether a page belongs to the base game should be directed to AppID 3904850 rather than the separate Demo AppID 4396220.
What should trigger a guide review
Review Builds when the engine categories, wiring behavior, automation controls, sensors, meters, power sources, heat-resistant frames, or component catalog changes. Review Planets when the number, names, stations, checkpoints, garages, environment presentation, or travel routes change. Review Missions when objectives, delivery conditions, payload behavior, achievements, or rewards change. Review Multiplayer when player limits, lobby behavior, shared controls, reconnect behavior, or platform features change.
Review Systems Requirements when the Store page changes its operating system, CPU, memory, GPU, DirectX, or storage lines. The current snapshot says 64-bit Windows 10/11, DirectX 11, 8 GB RAM and GTX 1060/RX 580 minimum, and 16 GB RAM with RTX 3060/RX 6700 recommended. Those values are useful only with their check date. They should never be copied into a timeless compatibility promise.
Release-state boundaries
The base game and its Demo are separate products. A demo notice should not be written as a base-game patch, and a feature visible only in a demo should not be advertised as a full-release system without proof. This site also does not infer a beta branch, dedicated server, DLC, soundtrack, or alternate edition when the official evidence does not establish one. When Steam publishes a new official update, record the exact title and date instead of converting a BuildID into a version name.
What is not yet verified
At this audit checkpoint there is no public semantic version, default-branch label, beta branch note, or complete patch history that can safely be turned into a fixed version guide. That is a boundary, not a claim that the game has no updates. When a source is missing, the tracker should say “not publicly stated” and point the reader to the canonical Store page or the developer’s official update history. A missing field must never be filled with a guessed version number.
The same rule applies to platform support. The current Store requirements establish Windows 10/11 and DirectX 11 for the audited PC scope. They do not by themselves establish Steam Deck, Proton, Linux, macOS, controller, or cross-play behavior. Those topics can be added after a dated official statement or an explicit live test, with the platform boundary kept in the page title and update note.
Keep the maintenance contract visible
Every future entry should answer three small questions: what source changed, which player decision does it affect, and what remains unverified? If those questions cannot be answered, the item belongs in a research note rather than the public timeline. This keeps the tracker useful during a fast launch period without turning incomplete information into a false patch note. It also makes later audits faster because each evergreen hub has a clear reason to be rechecked.
Player update checklist
- Open the official Steam page and confirm the AppID before trusting a new notice.
- Check whether a change is a release milestone, patch, hotfix, platform note, or community announcement.
- Record the source date and exact wording that can be supported.
- Link the affected evergreen guide and mark exact values for re-verification.
- Keep Demo, beta, and base-game behavior separate.
- Do not add a roadmap date, update cadence, or feature promise without an official source.
Use the canonical Steam Store page for the current product identity and the developer’s official update history for later entries. Until a dated official change is verified, this tracker should say so plainly.