Skip to content

Alienation PC v0.1.1

Latest

Choose a tag to compare

@saulob saulob released this 20 Nov 02:42

Alienation PC v0.1.1

Alienation for PlayStation 4 as a native PC port for Windows and Linux, with experimental Steam Deck support

No game files are included. You need your own legally obtained Alienation PS4 package from one of the supported builds

If you use v0.1.0, the launcher updater can install v0.1.1 while preserving your installed game files, saves, settings and logs. The update only starts when you click UPDATE NOW

Although it is a patch release by number, v0.1.1 is a substantial stability release: 32 commits and 189 changed files since v0.1.0, mostly in the Vulkan renderer, the crash and Bug Report pipeline, frame pacing and the launcher

GPU stability and renderer

v0.1.1 hardens the Vulkan renderer against the GPU hangs, device losses and out-of-memory failures reported on NVIDIA, AMD, Intel and Linux systems

Particle spawn workload (Issue #10)

v0.1.1 includes protection for the reported unbounded particle-spawn workload and for structurally equivalent loops that can be proven safe

  • Particle shaders that append particles in a loop are rewritten so the work done per dispatch is bounded, however large the spawn count the game computes
  • cs 0xe114750a (CUSA00062 1.06), the shader named in the report, is covered, and so are the equivalent spawn loops of all three supported builds
  • Normal particle output is preserved, and so is the final value of the game's GDS counter
  • Loops that do not match the safe pattern are left untouched
  • Shaders cached by v0.1.0 cannot bypass the protection (see Pipeline and shader cache)

This was tested successfully on an RTX 4070. The original report came from an RTX 3090, and Issue #10 remains awaiting confirmation from the original reporter. It is not confirmed fixed, and this does not prevent every GPU hang or driver reset

Controlled shutdown after a device loss

  • When Vulkan reports that the device is lost, the first cause is recorded once, further GPU work stops, waits end and the presenter stops
  • The game then exits with a crash report instead of failing in secondary ways or hanging on a black screen
  • Every point where the renderer talks to the GPU is covered: queue submit, sparse bind, semaphore and fence waits, acquire, present and wait-idle
  • The renderer never completes GPU work on the driver's behalf
  • The GPU crash trace is much richer: every pipeline and compute shader of each unfinished submission, the last dispatches with their group counts, separate draw, present, flip and buffer-memory timelines, heap budget warnings and the buffer fallbacks that were used
  • Windows now writes a minidump (alienation_NNN.dmp) beside the session log for a STOP, a GPU library assertion or a device loss
  • Linux ends with the same status and records the crash in the session log, but has no minidump

This improves what happens after the driver reports the loss and what a Bug Report contains. It cannot prevent the driver reset or the Windows TDR itself

Video memory and large buffers

  • Non-sparse arena fallback: GPUs without sparse buffer support use ordinary device memory for the game's buffer arenas, with the same migration, readback and indirect-draw ordering. Sparse memory stays preferred, and no sparse bindings are made in the fallback
  • Low VRAM (Issue #9): when a device-local allocation is refused with out-of-device-memory, the buffer backing is tried in the other memory types the arena accepts instead of ending the game
  • Arenas above 2 GiB: arenas are now always two pages wide, so GPUs with a 2 GiB buffer limit (AMD) are no longer asked for 3 to 5 GiB buffers, and barriers on overlapping arenas follow the guest address
  • A timeline value the driver reports as never signalled is treated as a device loss instead of a completed tick
  • The buffer address table (BDA) is republished after every arena migration, and stale bindings are refreshed on every draw, dispatch, copy and detile path

Texture cache, samplers and shaders

  • Texture cache garbage collection: eviction used inverted minimum ages and let pinned render targets use up the whole eviction budget, so the cache could grow for the entire session without evicting anything. This explains the unbounded texture-cache growth seen in some reports
  • A thread-safety fix and an early-stop fix in the LRU cache, and stale image references are no longer used after a cache insert
  • Frame images fall back instead of aborting when the video-memory budget is refused
  • Samplers are kept alive until the GPU has finished the last draw that used them
  • Wave64 lowering no longer places workgroup barriers inside divergent branches that contain atomics, GDS appends, shared-memory reads or subgroup operations. For the shaders this game ships the generated code is unchanged, so this is a hardening fix
  • NVIDIA shader interfaces: geometry and tessellation pipelines no longer mismatch the pixel shader's emulated clip-distance inputs, and pipelines without a pixel shader no longer inherit the previous draw's pixel-stage state
  • Persistent VK_SUBOPTIMAL_KHR: a swapchain the driver keeps reporting as suboptimal is replaced once instead of being recreated every frame, and an out-of-date swapchain is never kept

GPU command buffers

  • Command buffers the game rewrites while the GPU is reading them are now read in place, the way the GPU does it, for graphics, constant-engine and compute queues, including guest-address DMA that patches a compute dispatch
  • Indirect buffer ranges are validated before they are read, and the draw pipe is drained after a self-write
  • The experimental command-snapshot approach was withdrawn, so no unsafe command snapshot copies exist in this release

Related reports

Report Symptom Status
ALN-XXJJ7R Random crashes Wave64, texture-cache eviction, LRU, frame-image and SUBOPTIMAL defects fixed as part of a broader root cause. The reporter's exact cause is unproven
ALN-GKAQG9 Slowdown followed by a device loss Sampler lifetime fixed as part of a broader root cause. The reporter's exact cause is unproven
ALN-4KPCU7 Device loss during explosions on AMD Arena sizes above the 2 GiB buffer limit fixed as part of a broader root cause. The reporter's exact cause is unproven
ALN-MKL8FP Slowdown with a growing texture cache Fixed as part of a broader root cause (the texture-cache eviction defect)
ALN-VUK9PE Device loss while shooting on NVIDIA Fixed (shader-interface and pipeline-state fixes)
ALN-GLZYXD Device loss in the first mission Diagnostics only (separate timelines in the crash trace)
ALN-2RDFRU Device loss on an RTX 3090 Diagnostics only. The evidence was insufficient for a behavior fix
ALN-NKBTJV Device loss with wave64 shader warnings Regression coverage only
ALN-CGRZLW Random device loss on NVIDIA Not fixed. Investigated, no new defect found
ALN-S44D4A Crash in the first mission Not fixed. The report's log could not be recovered

Pipeline and shader cache

  • A corrupt, truncated, empty or damaged pipeline cache file is detected and rebuilt, and the cache is sealed with a magic, size and checksum with a 64 MiB cap
  • Cache files are written atomically, and the cache is kept per game build
  • Pipeline creation is retried without the driver's cache before it is treated as a failure
  • A BuildGate serializes pipeline builds and lets the game's own pipelines go ahead of warm-up builds
  • Driver pipeline binaries are cached for graphics pipelines
  • Background warm-up: pipelines from earlier runs are rebuilt in the background after startup, which is meant to reduce shader-compilation stutter. The first run after updating still compiles shaders. ALN_PIPELINE_ON_DEMAND=1 turns the warm-up off
  • Compute shaders with the particle protection are stored under a new shader revision, so a shader cached by v0.1.0 can never be loaded in place of the protected one

You do not need to delete your v0.1.0 caches. They are replaced automatically, and the first run after updating may stutter once

Performance and frame pacing

  • Frame rate remains a presentation setting. The game itself still steps at its original 59.94/60 Hz
  • Repeated frames are now capped at the display's refresh rate in every present mode, including VSync off. Under Gamescope this removes presents nobody can see
  • The F2 counter and the window title show the game's own frame rate, with the number of presented frames only when it differs. Tools such as MangoHud count repeated presents as frames
  • The log gets a one-line frame summary about once a minute, and a read-only probe records the game's fixed-step counters on all three builds, so a slow-motion report shows whether the game itself fell behind

These changes address the Steam Deck pacing report and Issue #5. They have not been validated on Steam Deck hardware

Audio

  • A backlog of audio the device has not played is dropped and refilled with silence once it exceeds the target by 100 ms, instead of growing, so audio no longer drifts behind the picture
  • Normal audio cadence is untouched

Controllers and input

  • gamecontrollerdb.txt beside the settings file adds or overrides SDL controller mappings, and SDL_GAMECONTROLLERCONFIG still takes priority
  • Joysticks without a mapping are named once in the log with their identifiers
  • Xbox and PlayStation controllers are unaffected
  • Issue #2: only diagnostics were added. The log records the platform and device, and a diagonal or alternating left-stick pattern with the raw and converted values. The stick conversion itself is unchanged from v0.1.0, so Issue #2 is not fixed

Launcher and windowing

  • Windows: the launcher now renders with a hardware-accelerated Direct3D 11 renderer for a more responsive interface. The game itself still uses Vulkan
  • d3d11.dll and dxgi.dll are loaded from the system folder only and kept loaded for the process, so a copy beside the executable is never used
  • If either DLL cannot be pinned or the renderer cannot be created, the launcher falls back to the software renderer
  • The launcher closes before the game starts in the same process
  • Linux: the launcher uses SDL's normal renderer choice with the software renderer as the fallback, and has no Windows-specific code
  • The log records renderer_selected, frame_pacing, loop_sample, launcher_present_stall and launcher_frame_pacing_excessive to diagnose launcher slowness
  • Window fitting: the launcher and the game window open on the right monitor, fitted to its usable area using the real window borders and the display scale. This was checked at 100%, 150% and 225% scaling. A window is never made larger than requested, and the saved size is not rewritten
  • The launcher's window-size list is no longer filtered by display

Bug Report and crash diagnostics

  • Bug Report can attach the crash dump of the same session. A dump is paired with a log only when it has the log's own name, sits in the same folder, was written within two minutes of the log and is a real minidump
  • A crash dump can contain process memory, so check the Bug Report preview before sending one
  • A new session log never reuses the number of a crashed session's dump
  • The game build in a report comes from the selected log's own session, not from the launcher's current build
  • Crash reports from online sessions name the room state and the online callback that was running (ALN-YB9NZA, diagnostics and regression coverage only)

Crash dump upload requires the updated production lobby Worker. The rest of a Bug Report does not

The production lobby Worker was updated before this release with the crash dump upload support required by the v0.1.1 launcher

Online

  • The production lobby endpoint is unchanged from v0.1.0
  • Online crash diagnostics are better: reports name the room state and the Matching2 callback that was running, and late-join paths have regression coverage
  • No specific online crash is claimed fixed by this release

Other fixes and improvements

  • NV12 video frames with padded rows are copied correctly
  • The GPU trace records heap budget crossings with one warning per heap, labels heap kinds, and reports correct buffer fallback text
  • Acquire and present failures go through the same Vulkan failure handling as other errors
  • A GPU library assertion after a device loss is routed to the first recorded cause
  • Package naming in the launcher and documentation now says complete package for the single CUSA00062 1.06 package, with no change in behavior
  • README, documentation and the Windows and Linux package READMEs were refreshed

Issues and community reports

Community reports relevant to this release include

  • Issue #2 left thumbstick direction issues. v0.1.1 adds diagnostics only. The stick conversion is unchanged and the issue remains open
  • Issue #5 Linux Intel slow motion and frame pacing, addressed in v0.1.1 and awaiting reporter confirmation
  • Issue #7 crashes during the second mission, no direct v0.1.1 fix proven. The broader stability fixes may help
  • Issue #8 repeated crashes during the first mission, no direct v0.1.1 fix proven. The broader stability fixes may help
  • Issue #9 Linux crash when beginning the first mission, addressed by the texture-cache and buffer-backing fixes and awaiting reporter confirmation
  • Issue #10 particle spawn GPU hang on an RTX 3090, fix included and awaiting confirmation from the original reporter

Not every issue listed above is fixed in v0.1.1; this section also documents open reports that remain relevant to the release

Other Bug Reports

Report Symptom Status
ALN-U3T5UQ Steam Deck running slowly Fixed (repeated frames capped at the display's refresh). Not validated on Steam Deck hardware
ALN-YB9NZA Crash after joining an online room late Diagnostics and regression coverage only. The crash report now names the room and the online callback
ALN-P8JPZ8 Weapons not dropping as expected No code change required. Drops follow the game's own level-gated data and the host's real clocks, and no port defect was found
ALN-87B4EJ Not retrieved before release Not fixed. No change was made for it

Supported game versions

Region Title ID Versions
Europe CUSA00062 1.00 and 1.06
Asia / Korea CUSA04430 1.00

CUSA00062 1.06 can be the base game plus the official update, or the complete 1.06 package. The USA release (CUSA04181) is not supported

All three builds receive every fix in this release. Build-specific features are unchanged: local co-op on CUSA00062 1.06 only, Asian Menu Buttons on CUSA00062 1.06 and CUSA04430, and the Voice-Over text fix on CUSA04430

The final v0.1.1 validation completed with 84 PASS, 0 FAIL and 0 NOT RUN, with 176,919 counted checks

  • All three prepared builds validated
  • Patch-site tests and feature parity
  • GPU regression suites, pipeline and cache tests, device-lost tests and particle spawn tests
  • Controller, online and Worker tests
  • Packaging checks, repository hygiene and release contracts
  • Windows package validation and Linux AppImage validation

Real gameplay, controllers, audio and visuals still require manual testing

Windows

  • Windows 10 version 1903 or newer, or Windows 11, 64-bit
  • A Vulkan 1.3 driver, and a processor with AVX and LZCNT (Intel Haswell, AMD FX or newer)
  • The launcher uses Direct3D 11 by design, and the game uses Vulkan
  • Updates go through trg-updater.exe

Linux / Steam Deck

Linux is a native x86-64 AppImage. It does not use Wine or Proton

The AppImage keeps the Ubuntu 20.04 compatibility target, and the final binary inspection found a maximum required GLIBC symbol version of 2.30, below the supported glibc 2.31 baseline. The pinned AppImage runtime is unchanged from v0.1.0

The AppImage has the same cross-platform game features as the Windows build, including online play, local co-op, frame rate options, render resolution, True Ultrawide, Skip Intro, Exit Game, Asian Menu Buttons, controller and keyboard support, Xbox prompts, the pipeline cache and background warm-up, the non-sparse arena fallback and device-loss diagnostics

Intentional Windows and Linux differences remain: minidumps are Windows-only, Allow overlay programs is Windows-only, the launcher renderer is Direct3D 11 on Windows and SDL's choice on Linux, and Linux updates replace the AppImage instead of using the Windows updater helper

Steam Deck support is experimental and has not been manually validated on hardware

Known issues

  • Issue #10 is awaiting confirmation from the original RTX 3090 reporter. Other causes of GPU hangs, especially on NVIDIA, may remain
  • Issue #2 remains open. Only diagnostics were added
  • Issue #7 and Issue #8 remain open
  • ALN-87B4EJ remains unresolved
  • ALN-S44D4A remains unresolved
  • ALN-CGRZLW remains unresolved
  • Linux has no minidump, so a Linux crash is recorded in the session log only
  • Steam Deck has not been manually validated on hardware, and Linux has had much less real-hardware testing than Windows
  • The Windows launcher previously used the software renderer because of a teardown race seen with NVIDIA drivers. The Direct3D 11 path pins the system DLLs to avoid it, and has had less testing on NVIDIA
  • The non-sparse arena fallback for GPUs without sparse buffers has had little real-hardware testing
  • True Ultrawide may place mission map markers wrongly
  • Frame rates above 60 repeat the latest game frame; they do not create new game frames
  • Local co-op exists only on CUSA00062 1.06
  • DLC is not supported

Downloads

Windows 10 / 11 x64

Download AlienationPC-v0.1.1-windows-x64.zip

Windows SHA-256 file

Extract the ZIP into a writable folder (not Program Files), run alienation.exe and install your game from the Play page

Linux x86-64 / Steam Deck

Download AlienationPC-v0.1.1-x86_64.AppImage

AppImage SHA-256 file

Make the AppImage executable and run it

Full installation and configuration information is in the README

Linux and Steam Deck details are in docs/LINUX.md

Online behavior is documented in docs/ONLINE.md

How releases are built and how the updater works is documented in docs/release.md

Security

The exact final v0.1.1 release artifacts and executables were checked with VirusTotal

At the time of validation all four scans reported OK

VirusTotal is an additional verification signal and not an absolute guarantee of safety

File SHA-256 VirusTotal
AlienationPC-v0.1.1-windows-x64.zip de49e7b735c26e801f3f927973b9c48c2190824e1dbc4efdc69db25ac6fc4008 VirusTotal
AlienationPC-v0.1.1-x86_64.AppImage 8b83ffeadb18269dfae1acff122d03b363964d2f3270262be24be8d899bc453e VirusTotal
alienation.exe ff9ac5a596b88328346de13aaebbeccb01cc3b424342c77cac812eba8f2b3d5d VirusTotal
trg-updater.exe b1795ca31eed313654ec1dabedb7d35ac083b3fecc34f0a156f4aa6b3961d050 VirusTotal

Final release inspection found no DEBUG_SAULO markers, local repository paths, user saves or logs, game data, PDB files or development symbol packages inside the public downloads. The Windows package was also checked for credentials and private tokens, RenderDoc binaries and development Vulkan layers

Checksums

de49e7b735c26e801f3f927973b9c48c2190824e1dbc4efdc69db25ac6fc4008  AlienationPC-v0.1.1-windows-x64.zip
8b83ffeadb18269dfae1acff122d03b363964d2f3270262be24be8d899bc453e  AlienationPC-v0.1.1-x86_64.AppImage

The matching .sha256 files are included with the release and are used by the updater when GitHub provides no asset digest

Changes since v0.1.0

v0.1.1 contains 32 commits on top of v0.1.0

View the complete v0.1.0 to v0.1.1 comparison

Thanks to everyone testing different GPUs, Windows configurations, Linux distributions, Steam Deck environments, online play and controller configurations, and especially to everyone sending Bug Reports and GitHub issues with enough information to investigate problems