Pax Autocratica Tech Guide

Pax Autocratica’s current Steam base game is a Windows Early Access release. The official listing calls for DirectX 11, 16 GB RAM, and 40 GB of storage, and it marks full controller support, adjustable difficulty, save-anytime play, and Steam Cloud. Treat those storefront fields as the supported baseline, then diagnose one technical layer at a time.

Verify the exact product and platform first

Confirm that Steam shows Pax Autocratica AppID 1067360 in the library. Do not use a Demo, Prologue, or Playtest installation as a substitute when checking saves, files, settings, or patches. Separate applications can have different depots and behavior even when they share a title family.

The public store data lists Windows support and does not list native macOS or Linux support. A compatibility layer may run the game on another environment, but that is different from an official native-platform commitment. Record the operating system, GPU driver, and Directive date before following a report from another machine.

Compare the PC against current requirements

Read the current Steam page for the exact CPU and GPU examples, because storefront requirements can be revised during Early Access. Having a listed component does not guarantee one fixed frame rate in every colony size or expedition scene.

Apply the official crash sequence first

In the August 13 State of the Frontline, the developers directed crash-affected players to verify Steam files, disable DLSS Super Resolution, disable Frame Generation, and contact the official Discord if crashes continue. Follow that order before adding community launch options or changing save data.

The Crash Fixes guide gives a clean reproduction workflow. Preserve manual saves and the automatic backup added in AG-12. Never delete a save directory as a first diagnostic step; a clean configuration test should be reversible and separate from player progress.

Diagnose performance by scene and setting

Establish a repeatable scene: the same colony view, sector, camera position, and approximate activity. Change one demanding option, then compare frame pacing and stability rather than only a peak frame-rate number. Colony population, visible construction, combat effects, and upscaling or frame-generation settings can produce different loads.

Official notes acknowledge ongoing performance work and mention an attempted FSR-related crash fix in AG-14. That wording is narrower than a guarantee that every FSR problem is resolved. If a current issue is tied to one upscaler or frame-generation mode, record the mode and whether disabling it changes the reproduction.

Check controller behavior systematically

AG-14 fixed a soldier-deployment menu issue at 16:10 resolutions, which shows that interface behavior can depend on aspect ratio as well as input device. When reporting a controller failure, include the screen mode, resolution, and the exact interface where input stops.

Treat Steam Deck and Linux as compatibility tests

The base store does not advertise native Linux support. Steam Deck results therefore depend on the current SteamOS, Proton version, game build, and graphics settings. A community report can establish that one configuration ran; it cannot establish official support or guarantee every colony and sector.

Keep Deck or Linux troubleshooting separate from Windows-native failures. Record Proton selection, whether the issue occurs before the menu or inside a save, and whether another compatibility version changes it. Do not overwrite a Windows save while experimenting without confirming Steam Cloud state and retaining a local backup.

Build a useful support report

State AppID 1067360, Directive date, Windows version or compatibility environment, CPU, GPU, driver, RAM, resolution, graphics options, and input device. Describe the shortest repeatable steps, what you expected, what happened, and whether file verification or disabling DLSS/Frame Generation changed the result.

If a crash affects only one save, preserve both that save and an earlier working one. If it affects a new game at the same step, say so. Use the official Discord path referenced by the developers rather than posting credentials, private system data, or unredacted personal files publicly.

Separate display faults from simulation faults

A panel that clips, disappears, or cannot be selected at one resolution may be an interface problem even while the colony simulation continues correctly. Capture the full screen, resolution, aspect ratio, window mode, and the panel name. Then reproduce the action at a standard 16:9 resolution before changing workers, buildings, or mission state. AG-14’s 16:10 soldier-deployment correction is a concrete example of a display condition producing a narrowly scoped failure.

When the model of a wall, facility, or route looks wrong, observe whether citizens still interact with it and whether resources continue moving. AG-12 and AG-14 include collision, wall, and research-interface fixes, so visual presentation and underlying state do not always fail together. Preserve the colony state, describe both the visible defect and the actual simulation outcome, and avoid demolishing a functional district solely to repair a rendering symptom.

Sources checked August 15, 2026

• Pax Autocratica on Steam — Windows platform, requirements, controller support, save-anytime, Steam Cloud, and accessibility fields.
• Official Steam News — developer crash sequence, automatic backups, 16:10 UI fix, FSR notes, and ongoing performance work.
• Official Pax Autocratica website — current game and support-community context.