Skip to content

Astral Chain PC 2026-11-20 (source; build it with your own dump)

Latest

Choose a tag to compare

@Puddz Puddz released this 20 Nov 13:17

Source snapshots of the three branches as of 2026-11-20. Pick one zip:

Download Branch For
AstralChain-PC-2026-11-20.zip main (0dd1677) Most players.
AstralChain-PC-texture-dump-2026-11-20.zip texture-dump (c1942d2) main plus texture dumping and replacement for modders (experimental)
AstralChain-PC-dlss-fsr-2026-11-20.zip dlss-fsr (967bdf3) main plus NVIDIA DLSS / DLAA and AMD FSR 3.1 / 4 (experimental, new)

These downloads do not contain the game. There is nothing to run straight away: like the repository, they hold
only the port's source, the launcher and the setup scripts. The game is built on your PC from your own dump:

  • the base game (title ID 01007300020FA000), XCI or NSP;
  • the v1.0.1 update NSP (exactly v1.0.1);
  • your console's prod.keys.

To install: unzip the zip you picked to a short local path (for example C:\Games\AstralChain-PC), start
Astral Chain Launcher.exe and press Install game. Setup downloads its own tools (Python, Zig, glslang,
NSTool, SDL3, pinned and checked by SHA-256) and takes roughly 15-40 minutes the first time. See the
README for requirements and details. Updating from an earlier
version: unzip over it; the next Play rebuilds the game once, saves and game data are kept. Each branch is a
separate install (unzip to its own folder).

Items marked not yet confirmed were tested in scripted runs, not yet in play.

New: the dlss-fsr branch (issue #31; experimental, not yet confirmed in play)

Everything in main plus Settings > Display > Anti-aliasing and upscaling: NVIDIA DLSS (RTX GPUs; DLAA at
the Native quality) or AMD FSR 3.1 / 4 (FSR 3.1 on any GPU, FSR 4 on the Radeon GPUs and drivers that have it)
instead of the game's SMAA. Set Render resolution to your screen's size and pick a DLSS / FSR quality
(Native, Quality, Balanced, Performance, Ultra performance): the 3D scene is drawn at that share of the render
resolution and rebuilt at full size; the HUD, menus and subtitles are drawn at full size. How to use it and its
limits: DLSS and FSR.

  • The upscalers' files are not in the zip: the next Play downloads them from NVIDIA's (59 MB, under NVIDIA's
    license) or AMD's (36 MB) own repositories on GitHub. If the upscaler cannot be used, the game's own anti-aliasing
    is used.
  • Tested here on an RTX 4090, in replays only: DLSS 310.9.16 and FSR 3.1.6 from 1600x900 to 3840x2160 and at 32:9.
    FSR 4 was not tested (no Radeon GPU here).
  • On that GPU the frame rate did not change at 4K (the CPU is the limit there and the game's 3D scene is cheap to
    draw): expect a cleaner picture more than a faster one.
  • Known limits: with FSR 3.1 fast-moving characters can smear at their edges; in some cutscene close-ups the
    characters' motion is not tracked exactly.

New (all)

  • New: ambient occlusion (issue #46; not yet confirmed in play; off by default): Settings > Display > Ambient
    occlusion
    in the launcher, or Picture in the in-game menu (F1, applies at once): Off, Low or High. It
    darkens creases, corners and the ground under characters and objects, which the game leaves as lit as open ground.
    Ported from captainj-sparrow's port (MIT): its
    shaders as they are, its hookup rewritten for this renderer (its "bounce light" level is not ported). On save
    states in File 3 the darkening lands where it should and is subtle by design; about 0.35 ms of GPU time per frame
    at 2560x1440 on an RTX 4090. Works with DLSS and FSR on dlss-fsr too.

  • Fixed: fire light flickering on things near a fire (issue #44; confirmed in play): in File 3, by
    the burning barrel next to the stairs, the fire's light on the chairs, crates and Akira went out for single
    frames. After the GPU's light pass the port copied the buffers it had used back into the game's memory whole,
    read-only ones too, and so put old light data back over what the game had just written; one of the fire's lights
    then dropped out for a frame. Now only what the GPU changed is copied back. On a save state at that spot: drops in
    about 9 of 10 runs before, none in 13 runs after, same frame rate.

  • New: save states can be turned on from the in-game menu (issue #44; not yet confirmed in play): F1, the
    Game box, Save states, F6 and F7 (experimental). As with the launcher's option it takes effect the next
    time the game is started; the line of keys at the top of the menu says so until then.

  • New: the launcher's Settings window in boxes; boxes close and open; menu size (issue #43; not yet confirmed
    in play
    ): the launcher's Settings window now has the same titled boxes by topic as the in-game menu, with
    the first sentence of each explanation under the name, the rest as a tooltip on the (?), and a line at the
    top listing the keys used in the game (save states included). In both, a click on a box's title closes or opens
    it, and that is remembered. The HUD layout page (F2) has the same look. The in-game menu's last box, This
    menu
    , has a Size slider (60% to 160%) for its text and window. Not tried with a controller.

  • New: frame rate size (not yet confirmed in play): a Size slider under Frame rate display in the
    in-game menu (F1) makes the frame rate counter and the detailed panel smaller or larger, 50% to 200%.

  • New: a tidier in-game settings page (F1) (issue #43; not yet confirmed in play): the settings are in titled
    boxes by topic (Controller, Mouse, Picture, Frame rate display, Ultrawide and HUD, Title screen, Game), with a
    line between settings and the ones that depend on another set in under it. Only the first sentence of each
    explanation shows; the rest opens when you point at the (?) after the name or move to the setting with a
    controller (that pop-up was not tried in the test runs). A strip at the top lists the keys: F1, F2, F3, F6 / F7
    (save states), F11.

  • New: choose what the detailed frame rate panel shows (issue #43; not yet confirmed in play): with Show
    the frame rate
    on Detailed, the in-game menu (F1) lists the panel's eight parts under it, each with a
    box: GPU and video memory, CPU and memory, frame rate and frame time, the graph, renderer timings (the three
    orange lines), render sizes, frame limit and presentation, GPU and CPU names. Applies at once and is kept.

  • New: size of the HUD's panels (issue #43; not yet confirmed in play): the HUD layout page (F2 in the
    game) has a slider, 50% to 150%, that works at any render resolution. It makes the HUD's corner panels (health,
    Legion, minimap, objectives, items, tutorials) smaller or larger, each from its own corner. Markers over
    characters, text in the middle of the screen, subtitles and the menus keep their size. Looked at in one place of
    the game only, at 3440x1440 and 2560x1440.

  • The in-game menu (F1) says at the top that F6 and F7 are the save states and where they are turned on.

  • Save states (experimental, off by default; confirmed in play on two PCs): with the launcher's new Save
    states
    option (under Troubleshooting) on, F6 writes the whole running game to a file and F7 goes back
    to it: at once, after the game was started again (press F7 on the title screen), or on another PC. It is meant
    for showing a problem from the moment before it happens, in place of a long recording. The file is
    userdata\saves\01007300020fa000\savestates\state.acss (1 to 1.5 GB, about a third of that zipped).
    Before you use it, read save states:
    the file holds game data, so send it privately, never on a public page; a state only loads in the same
    release and at the same render resolution; and after loading a state the game saves that state's progress over
    your save as usual. Tested in scripted runs (20 loads in a row, a loading screen, an in-engine cutscene, FSR
    and DLSS on) and by loading a state made on another PC with another graphics card; not tried on AMD or Intel
    graphics or during a pre-rendered video. With the option off nothing changes.

  • New: frame rate: two more places (issue #43; not yet confirmed in play): the frame rate counter and the
    detailed panel can also sit half way down the left or the right side of the window (Middle left, Middle
    right
    ), which the game's own HUD leaves free. The setting is now called "Frame rate: position"; it applies at
    once.

  • Shadow resolution (issue #40; not yet confirmed in play): a new setting in the launcher and the F1
    menu, under Display. The game draws the shadows of characters and objects into one 2048x2048 shadow map, as on
    the Switch; from close up or at a high resolution their edges show as blocks. 2x, 4x and 8x make
    that map finer each way, so the blocks get that much smaller. It takes video memory: about 250 MB at 4x, 1 GB at
    8x (16x was tried and dropped: 4 GB for a difference hard to see). Off by default; applies at the next start. In the police headquarters at 2560x1440 the blocks along a shadow's edge shrank with
    each step. The line where the game switches to its coarser shadows further away is still there.

  • Ultrawide, HUD at the edges: the duty points and the case icon (issues #41, #42; not yet confirmed in
    play
    ): with "HUD at the screen's edges" on, the pop-up that counts duty points came apart (its arrow stayed in the
    middle of the screen, the bars behind the numbers ran too wide), and the red case icon after the objective's text
    stayed at its 16:9 place while the objective moved to the edge. Those parts are turned within their panel, which is
    why they were left behind; they now go with the panel they belong to. In a replay of File 02 at 3840x1080 the
    pop-up and the icon looked as at 16:9, and the Legion wheel, IRIS's profile panel and the Police Gear menu were as
    before.

  • Ultrawide: boxes and a video in cutscenes (issue #39; confirmed by the reporter): wider than 16:9, some
    cutscenes showed a darker or hazier box over the middle of the picture, of a different width from shot to shot. It
    is a flat card the game puts in front of the camera to tint the picture, sized to fill a 16:9 view; such a card is
    now widened with the picture. A video cut into a cutscene (Olive and Yoseph in File 02) showed the scene from
    before it at both sides of its 16:9 picture; those sides are now black. In a replay of the end of File 02 at
    3840x1080 none of the three boxed stretches showed a box any more, and the video had black sides.

  • Ultrawide: a case's results screen (issue #38; confirmed by the reporter): wider than 16:9, the list
    of bonuses on the results of a case was cut off on its left side, the rank badge (Lappy) that lights up beside the
    total showed stretched at the far right of the screen, and the photo behind the list was pressed into the left
    half of its frame. The list's clipping, the badge and the photo's frame now follow the panel into the 16:9 area.
    In replays of a recorded case at 3840x1080 and 2560x1080 the screen matched the 16:9 one, and the Police Gear
    menu's pages were unchanged. Still open: the photo itself is the wide scene pressed into its 16:9 frame.

  • On Linux? The README now links SrShadowy's native Linux port based on this project (SrShadowy/AstralChain-PC). It is a separate project, not made or tested here; please report problems with it on its own issues page.

  • F3 hides the HUD (issue #35; not yet confirmed in play): in the game, F3 hides everything the game
    draws over the scene (HUD, markers, subtitles, button prompts, its menus) for screenshots, and F3 again shows
    it. A line at the top says which for a moment. It is not saved: the HUD is back the next time you start. In
    scripted runs the HUD, the Legion wheel and the title screen's text were gone and the title's video stayed.

  • Anisotropic filtering (issue #33; not yet confirmed in play): Settings > Display > Anisotropic
    filtering
    (and the F1 menu; applies at the next start): 4x, 8x or 16x for textures seen at a slant, such as the
    ground in the distance. The default is the game's own (2x or 4x on some surfaces). It is applied to the textures
    the game repeats across surfaces, not to every texture: with all of them at 16x, red speckles followed the edges in
    the scene. In the one dark scene tested here the picture was clean and the gain was small.

  • Clearer names for the scaling options (issue #34): Upscaling is now Window scaling (how the
    finished picture is enlarged to the window; on dlss-fsr it is separate from DLSS and FSR 3.1 / 4 and can be used
    with them), and its sharpening is Window scaling: FSR 1 sharpening. Options that do nothing with the current
    choice are greyed out in the launcher and in the F1 menu. Ultrawide: HUD at the screen's edges is no longer
    marked experimental.

  • Render resolutions, AMD FSR 1 and ultrawide are now in main: the upscaling branch was merged into main,
    so there is no separate upscaling download any more. Everything it added is off unless you choose it (the
    default is still 1600x900): render resolutions from 854x480 to 4K, AMD FSR 1, 21:9 to 48:9 with the HUD at the
    screen's edges and the HUD layout page (F2). Coming from an upscaling install: unzip the main zip over
    it (or git switch main and git pull); saves and settings are kept and the next Play rebuilds the game
    once. In a replay of one recording at the default settings, the picture and the frame rate were the same before
    and after the merge.

  • Frame rate display: choose its corner (issue #30; not yet confirmed in play): Settings > Display > Frame
    rate: corner
    in the launcher, and in the in-game menu (F1, and on the HUD layout page,
    F2): top left (as before), top right, bottom left or bottom right, for the plain counter and the
    detailed panel. It moves at once.

  • Shorter README: features and installing on the front page; what's new, playing (keys, controllers,
    the in-game menu), and known issues are now pages under docs/. Nothing in the port itself changed.

  • Saves and settings made safer, and several stops and freezes addressed (from a review of the code; not yet
    confirmed in play
    ). Nothing moves: saves, settings and game data stay where they are, and the next Play
    rebuilds the game once as after any update.

    • Save backups never hold a half-written save: the automatic backup next to the saves (...-snapshots) is now
      taken only while the game is not writing, and thrown away and taken again if the game changed its save during
      the copy. Before, a backup taken in the middle of the next save could be kept as complete.
    • userdata\launcher.ini is not lost or overwritten: the in-game menu no longer writes a new file when it
      cannot read the old one (which dropped key bindings and the other settings); the launcher keeps what the
      in-game menu saved while it was open, and writes the file in one step. The in-game sliders save when let go, not
      at every step.
    • A folder that was copied or moved is built again on the next Play. Before, a copy kept reading from, and
      saving into, the folder it was copied from, and a moved folder did not start (exit code 31).
    • Folder names with letters outside English (for example C:\Users\Jörg\...): the game no longer closes at
      every start with exit code 31.
    • A rare freeze or stop in the game's thread locks addressed: two places changed a lock's state in two steps
      while the game changed it too.
    • A fast mouse can no longer stop the game (host-message-budget) after a long stall.
    • Setup: a folder path with [ or ] is reported at the start instead of failing later; the GPU warm-up's
      time limit now works when it hangs; a failed BC7 textures preparation no longer blocks Play; a build
      cancelled at the wrong moment no longer fails every later build.
    • Reports from a downloaded zip say which version it is (a VERSION file filled in when the zip is made).
  • Detailed frame rate panel (issue #28; not yet confirmed in play): Settings > Display > Show the frame rate
    (also in the in-game menu, F1) is now Off / Frame rate / Detailed. Detailed shows a panel in the top left
    corner: a frame time graph, the 1% and 0.1% lows, GPU and CPU load, video and system memory, the GPU's temperature,
    power and clock, the GPU's busy time and the waits per frame, and the window, game picture and 3D scene sizes.
    Temperature, power and clock come from the graphics driver's own library (NVIDIA and AMD; nothing is downloaded or
    shipped for it); Intel GPUs show the rest without them. Tested on an NVIDIA card; the AMD readings are untested.
    Corrected in this update: on laptops with two GPUs the GPU load read 0% (it was read from the integrated GPU);
    it is now read from the GPU the game renders on.

  • Sharp picture with Windows display scaling (red-Geck0, from issue #25; tested by its author on a 1920x1200
    handheld at 150%, not yet confirmed here): with scaling above 100% (common on laptops and handhelds), Windows gave
    the game a smaller screen and stretched the result, so the picture was blurry (at 150% on a 1920x1200 screen the game
    saw 1280x800). The game now uses the screen's real pixels. In a window it now opens at 1600x900 real pixels, so with
    scaling the window looks smaller than before (before, it could be larger than the screen).

  • Quit game in the in-game menu (thanks to red-Geck0, PR #23; confirmed in play): Quit game at the
    bottom of the menu (F1, or Minus and Plus on a controller) closes the game after asking first, so a controller
    alone is enough, for example on a handheld PC.

  • Swap A and B (red-Geck0, PR #23; confirmed in play): Settings > Controller > Swap A and B, also in
    the in-game menu. On: the bottom face button (Xbox A, PlayStation cross) confirms and talks and the right one goes
    back, as in most PC games; the button icons follow. Off by default (by position, as on the Switch). The keyboard
    keeps its keys.

  • Launcher background no longer tiled (red-Geck0, PR #24; tested by its author, not yet confirmed here): when Windows makes the
    launcher window bigger after it opens (seen with Xbox Mode on a handheld), the background image is made again for
    the new size instead of repeating at the right and bottom.

  • Input recorder: a recording now keeps its last second when the game is closed (the X, Alt+F4, Quit game);
    before, the end could be cut off.

  • Lights missing in blocks of the screen fixed (issue #20; confirmed in play): the game splits the
    screen into small tiles and lists the lights that reach each one. A translation error dropped lights from some
    tiles, which showed as dark blocks with straight, stair-stepped edges, for example on the side of the truck on
    the street after the highway chase. On the test PC that truck is now evenly lit, as on the Switch. Still open:
    in some scenes a light can vanish from the whole picture for a single frame (a flicker); that is a separate
    problem and happens with or without this change.

  • New: input recorder (for reporting problems): Settings > Troubleshooting > Record controller input
    records your buttons and sticks from launch, with a copy of your save as it was at launch, into a new folder
    next to your save (userdata\saves\01007300020fa000\<user>-recordings). Zip that session's folder and attach it
    to an issue: the problem can then be played again on another PC. Off by default. Replays drift a little (the
    game is not exactly the same run to run), so a short recording from a save near the problem works best.
    Recordings also mark where cutscenes start and end, so a replay on another PC stays in step through loading
    and skipped cutscenes.

  • Optional frame rate counter: Settings > Display > Show the frame rate (also in the in-game menu, F1, where
    it turns on and off at once) shows frames per second and the average frame time in the top left corner of the
    window. Off by default.

  • Less waiting and spinning (not yet confirmed in play), from a review of the code for things a PC game
    would do differently:

    • a draw waiting for its shader to compile now sleeps until it is ready instead of keeping a core busy. On a
      first play of the highway chase: 1-2% less time waiting for shaders with 8-16 processor threads, 13% less
      with the game held to 4 threads (where the spinning took time from the threads compiling the shaders);
    • the game's 1 ms sleeps no longer spin for their last quarter millisecond: the two worker threads that sleep
      most use about half as much processor time (small in total: about 0.03 of a core).
      The game's report (stderr.log, 2-s lines) now also shows the driver's own video memory figures; they are what
      showed the problem with the 4 GB option above.
  • Much less processor use (not yet confirmed in play): three of the game's worker threads kept a processor core
    busy each, even with nothing to do. They now really sleep. On the test PC on the highway chase: 4.6 busy cores
    down to 0.8, frame rate unchanged or slightly better (59.7 fps average against 58.7). This should matter most on
    laptops (less heat and power, more room for the threads that do the work).

  • For GPUs with 4 GB of video memory (experimental, not yet tested on a 4 GB GPU): Settings > Shaders and
    performance > Keep the game's memory copy in system RAM
    . The game keeps a 2.8 GB copy of the Switch's memory on
    the GPU; this keeps it in system RAM instead. Corrected in this update: in the previous downloads the option
    did not actually free video memory (the driver kept the copy on the GPU; the 7.2 -> 4.4 GB figure given before was
    the game's own count, not the driver's). Now, by the driver's own figures on an RTX 4090 on the highway chase:
    9.3 GB of video memory in use down to 6.4 GB; frame rate 59.6 fps on average against 59.9, with a few short dips to
    52-56 fps. Off by default. Use it together with Texture compression.

  • Driver error reports say more: when the game is closed because Windows logged a GPU driver error, run.txt
    (in the report) now has the time and the driver's own text for it (for example Error occurred on GPUID: 100),
    not only its number.

  • Optional: the title screen shows the twin you play as (not yet confirmed in play): the game puts the twin
    you did not choose on the title screen. Settings > Display > Title screen shows the twin you play as (also
    in the in-game menu) shows yours instead. Off by default; your save is not changed.

  • "Port by Puddz" on the title screen, above the version number (not yet confirmed in play). On by default;
    Settings > Display in the launcher, or the in-game menu (F1), turns it off.

  • Every setting explained: docs/settings.md.

  • Saves are flushed to disk (not yet confirmed in play): files the game writes are flushed when it closes
    them and at its save commit, so a save survives a Windows crash or power cut right after saving. (A crash of
    the game itself never lost a save.)

  • Save backups only kept when complete (not yet confirmed in play): the automatic backups next to the save
    (<save>-snapshots, newest 30) are now written to a temporary folder and kept only if every file was copied;
    older ones are removed only after a good one. A save made while a backup was being written now gets its own
    backup too.

  • Install: tool downloads no longer stop on a certificate error (issue #16; not yet confirmed): when the
    setup's Python cannot check a download's HTTPS certificate ("CERTIFICATE_VERIFY_FAILED ... unable to get local
    issuer certificate"), it downloads that file with Windows' own downloader instead. Every download is still
    checked against its pinned SHA-256.

  • Game window brought to the front when it opens (issue #15; not yet confirmed in play): the game reads
    no keys or controllers until its window is the active one, and it used to open without asking to be (a pad
    doing nothing until a click; in fullscreen, no start prompt until switching to windowed and back). The
    launcher now stays in front until the game's window opens, and the game makes its window the active one.

main

Since the 2026-11-04.1 release:

  • New: GPU results copied back faster (not yet confirmed in play): only the pages the GPU changed are copied
    back to the game, as on upscaling since October (reported there in play on an RTX 5070 Ti over OCuLink:
    42 -> 53-54 fps with the Legion out). On the test PC (RTX 4090) GPU time per frame on the highway chase went from
    6.3 to 5.5 ms on average; the frame rate was already 60. It should matter most on laptops and eGPUs.
  • In-game settings menu: F1, or Minus and Plus together on a controller. The game pauses while it is
    open. Button icons, rumble, mouse settings, fullscreen and more change at once; changes are saved for the
    launcher too. Confirmed in play.
  • Xbox, PlayStation and automatic button icons: by default the game's prompts follow what you last used
    (keyboard and mouse, or an Xbox, PlayStation or Switch controller). Not yet confirmed.
  • Controller rumble through XInput and SDL3, with a strength setting. Confirmed in play (an 8BitDo controller's
    buttons work too).
  • Uncapped frame rate (experimental, off by default): gameplay is no longer held to 60 fps; cutscenes stay at
    60. Reported in play: it does not feel right above 60 fps yet; being looked into.
  • Faster: atomic memory operations no longer search every mapping table (street after the opening helicopter
    scene, uncapped, RTX 4090 / Ryzen 7 7800X3D: 67.0 -> 71.4 fps).
  • Prepare graphics on a separate thread (experimental setting): hangs and crashes at high
    frame rates fixed. With the uncapped frame rate, the same street ran at 87.0 fps instead of 71.8. Not yet
    confirmed in play.
  • Title screen flicker fixed: for a frame the background was drawn squashed into a band between black bars
    (reported in play: about every 10 s at 60 fps, nearly all the time uncapped). Uncapped title screen, 25 s
    captured per run: 1-12 squashed frames per run before, none in 5 runs after, same frame rate. Confirmed
    in play.
  • Startup stop fixed (host-shared-placeholder-reserve, about one start in 20).

Now in main: render resolutions, FSR 1 and ultrawide (experimental options)

From the upscaling branch, merged into main on 2026-11-12 (see Playing):

  • Ultrawide: Legion skill cooldown rings move with the skill panel (issue #32; not yet confirmed in
    play
    ): with Ultrawide: HUD at the screen's edges on, the ring that counts down a Legion skill's cooldown stayed
    where the HUD is at 16:9 while the rest of the bottom right panel was at the screen's edge. The rings are turned
    like the panel IRIS shows for a scanned person, which stays in place, and were taken for it; they are now told
    apart by where they are. In a scripted run at 3840x1080 (ZL held, X) the ring was at the edge with its panel, and
    IRIS's panel was still next to the person scanned.
  • Ultrawide: Legion wheel no longer doubled (issue #29; confirmed in play): with Ultrawide: HUD
    at the screen's edges
    on, holding Y showed a second copy of parts of the Legion wheel (the ring that follows the
    stick, at times the cube in the middle) at the right of the screen. Those parts were taken for the HUD's side
    panels and moved to the edge; they now stay with the wheel. Seen fixed in a replay of the report's recording at
    3840x1080.
  • New: ultrawide HUD at the screen's edges (issue #27; experimental, confirmed in play): Settings >
    Display > Ultrawide: HUD at the screen's edges
    , also in the in-game menu where it changes at once. With a render
    resolution wider than 16:9, the HUD's side panels (health, minimap, objectives, tutorials) move to the left and
    right edges; markers over characters, subtitles and menus stay where they are. Off by default. Seen in scripted
    runs at 5120x1440, combat included; 21:9 and 48:9 not yet. The menu (minus) and IRIS's panels (file and profile, and the flicker the profile comes in with) stay in the middle
    (in the previous downloads their right-hand parts moved too); a few flat notices (such as the Red Matter cleanup
    rate) also stay in the middle (the menu and IRIS, its flicker included: confirmed in play). Also: the title and
    load screens' dotted lines no longer reach into the side bands.
  • New: HUD layout (F2) (issue #27; confirmed in play): on a screen wider than 16:9, F2 in the game
    (or HUD layout in the F1 menu) opens a window to place the HUD: for each corner's panels (top left, bottom left,
    top right, bottom right) how far they move toward the edge (0-100%) and up or down. The game is drawn behind it,
    so each change shows at once; saved with the other settings. The first time the HUD shows on a wide screen, a line
    at the top says F2 is there (until you have opened it once).
  • New: ultrawide menus, subtitles and credits no longer stretched (issue #22; confirmed on a 32:9 replay):
    wider than 16:9, the title and save menus, character creation, subtitles outside cutscenes and the opening
    credits were stretched across the whole width. They now keep their 16:9 shape in the middle, like the HUD;
    fades and full-screen backdrops still fill the screen.
  • New: ultrawide title screen and videos in 16:9 (issue #22; confirmed in play): the title screen's
    background and logo (videos) were stretched across the whole width. Videos now keep their 16:9 shape, with
    black at the sides.
  • New: ultrawide markers on target (issue #21; confirmed in play): wider than 16:9, the markers over
    characters and targets sat too close to the middle of the screen (at 32:9, half as far out as the character).
    They are now placed with the wider view. On a replay of a 32:9 recording the marker sits on the character.
  • New: 48:9 render sizes for three screens side by side (issue #19; not yet tested on real triple screens):
    Render resolution (launcher and F1 menu) now also has 5760x1080 and 7680x1440. The 3D view gets wider and the
    HUD stays 16:9 in the middle, as with 21:9 and 32:9. 7680x1440 is over the size limit and is drawn at 6788x1272
    (same shape, a little softer); it used up to 11.2 GB of video memory on the test PC. Subtitles and the opening
    credits are no longer stretched (issue #22, below).
  • New: picking the right game file after a wrong one works (fixed on main since 2026-10-23, now here too):
    setup used to keep the files extracted from the wrongly picked file.
  • New: a rare GPU crash cause fixed in the eGPU write-back speed-up (not yet confirmed): with more than 16
    large GPU results in one batch, a buffer could be freed while the GPU still used it.
  • AMD FSR 1 upscaling and its sharpening, both changeable in the in-game menu (F1) while playing.
  • Render resolutions from 1920x1080 to 3840x2160, and ultrawide sizes (21:9, 32:9). Ultrawide untested on a
    real ultrawide monitor.
  • Smaller render sizes for slow GPUs (issue #4): 1280x720, 960x540 and 854x480. The 3D view is drawn at
    that size and scaled up; the HUD stays sharp. It only lightens the graphics card's work (a slow processor is not
    helped). RTX 4090, GPU time per frame compared with 1600x900: 720p -6%, 540p -20%, 480p -25%. Not yet confirmed
    in play.
  • Faster with the Legion out on GPUs behind a slower link (such as an eGPU over OCuLink): only the changed pages
    of GPU results are copied back. Reported in play on an RTX 5070 Ti over OCuLink: 42 -> 53-54 fps (2560x1440, FSR 1).

Not on this branch: the integrated-GPU change from main (PR #13).

texture-dump (experimental, for modders)

Everything in main plus texture mods (issue #14). Step by step: the
texture mods guide.

  • New: a dump that fails part-way is discarded instead of being kept as a short DDS file (and never
    redone).
  • Texture dumping (not yet confirmed in play): Settings > Mods > Dump textures writes each texture the
    game loads, the first time it appears, as <hash>_<width>x<height>.dds (all mip levels; cube maps and arrays as
    such), with textures.csv listing them. Texture dump folder (with a Browse button) picks the folder; empty
    means userdata\textures\dump. Most of the game's textures are BC1/BC3 and are written as they are; ASTC ones are
    decoded to RGBA8. The same texture gets the same name in every run, and files already there are kept. Tested on
    the highway save: 2,217 textures (3.8 GB) in two minutes, every file opened and decoded with Pillow, no change in
    frame rate.
  • Texture replacement (not yet confirmed in play): Settings > Mods > Use replacement textures loads DDS
    files whose names start with a texture's hash (as dumping names them) from Replacement textures folder (empty:
    userdata\textures\replace; subfolders are searched). Any size, so HD textures work; BC1-BC7, RGBA8 and more,
    with the DX10 or the older DDS header; as many mip levels as the file has. The colour space follows the game's
    texture. Tested on the highway save with generated test patterns for all 2,165 dumped 2D textures (same size,
    twice the size as DXT5, twice the size as RGBA8 with mips): all showed on screen, frame rate unchanged
    (59.7-59.9 fps against 59.9), about 1 GB more video memory at twice the size.