Sinking Star Atlas · content last verified September 18, 2026

Sinking Star Atlas

Official technical note

Demo Settings and Performance Checks

The official July 10 technical update describes an optional public-testing branch for the demo. Use this page to apply those settings deliberately and to keep a graphics problem separate from a puzzle problem.

No spoiler

§Opt into the public-testing branch#

These are the steps stated in the official technical update. Steam's labels can change, so check the client text you see.

  • Open Steam Library and locate Order of the Sinking Star Demo.
  • Right-click the demo and open Properties.
  • Open Game Versions & Betas.
  • Choose public-testing. The announcement says no password is required.
  • After Steam applies the branch, record the branch name, date, graphics preset, and hardware before testing a puzzle or reporting a bug.

§What each technical option is for#

Player problemOfficial option or updateLimit to keep in mind
Low frame rate or battery pressureVery Performance graphics setting and broader optimizationsThe post describes improved performance, not a universal frame-rate guarantee
Steam Deck tuningThe update targets 60fps on most levels on Steam DeckMost levels is the published scope; individual scenes can differ
Frame pacing or visual shimmerVsync, frame-rate cap, and antialiasing mode in GraphicsChange one control at a time so a comparison remains meaningful
Dialogue competing with puzzle focusSeparate music, sound-effects, and character-voice volumesAudio controls do not establish that story content can be skipped
Localization checkText language can be switched dynamically from the menuThe demo store page still lists localization as work in progress
Older GPU or low-RAM systemIncreased compatibility for older GPUs and systems with less RAMThe update explicitly says shader model 6.5 support is still unavailable

§A safe troubleshooting order#

This sequence is editorial guidance built around reproducibility. Only the option names and beta-branch path above are official technical facts.

  • Write down the branch, operating system, GPU, input method, language, and current preset.
  • Change one setting, then replay the same short scene or board.
  • If the problem changes, keep the before-and-after values instead of changing several controls at once.
  • If the problem does not change, return to the prior setting and test the next single variable.
  • When asking for help, attach the exact symptom and the last known good branch or preset. Do not call a performance issue a puzzle rule.

§What this update does not prove#

The beta note does not guarantee a fixed frame rate on every device, confirm future console settings, or establish that the public-testing branch matches the launch build. It also does not change the Steam-only scope of the demo progress carryover statement.

If the demo still fails after a controlled comparison, keep the settings record and move the question to a technical support channel. This guide should not turn a hardware symptom into a claimed puzzle mechanic.

§Copy this support note#

FieldExample
BranchDefault or public-testing
DeviceSteam Deck, desktop GPU, or other hardware
SettingsPreset, Vsync, frame cap, antialiasing, language, and audio changes
ReproductionThe same room or short scene and the steps that trigger the issue
ResultWhat changed, what stayed the same, and whether the issue affects puzzle input or only presentation

§FAQ#

Is public-testing required to play the demo?

No. It is an optional beta branch described in the official July 10 technical update. Keep the default branch if you are trying to reproduce a guide or a friend's result.

Does Very Performance guarantee 60fps?

No. The update describes faster frame rates and 60fps on most levels on Steam Deck. Treat that as the published scope, not a guarantee for every device or scene.

Can I use these settings on Switch 2 or PlayStation 5?

The cited technical note is for the Steam demo beta branch. It does not provide console menu instructions.