Skip to content

v0.2.0-alpha

Choose a tag to compare

@eliasm4r eliasm4r released this 21 Nov 21:03

60 fps fixed, supersampling back up to 200 %, 1440p and 4K output, two-player co-op, no more freeze at the first mission.

Fixed

  • 60 fps and above (issues #1 to #3): the world map cursor and in-engine cutscenes no longer run twice as fast at 60 fps, and the whole game no longer speeds up at 120, 144 or 240 fps when the frame rate stays under the limit. Cutscenes still animate at 30 frames a second, as on the Switch.
  • Long freeze when the first mission starts, on a first launch: the setup now prepares the shader variants the game asks for in play. On an RTX 4070 the first frame of the tutorial battle went from 2.6 s to about 0.5 s, and no shader was translated during the first 5 minutes of a new game (100 before). On a first launch a battle's first frame can still take a moment while the graphics driver builds its pipelines, once; this is the next thing being worked on.
  • Render scale 125 % and 140 % are back: the endless loading at the first story cutscene is gone (the game's GPU texture pool now grows with the scene).
  • Unlit picture with a black rectangle after "New game" at render scales above 100 %.
  • AMD cards on Windows (issue #4): Adaptive VSync instead of plain VSync where Mailbox is missing, so a late frame no longer judders between 60 and 30; less GPU time a frame (only the flushed parts of the game's GPU buffers are copied); the performance overlay's GPU busy time is right.

Added

  • Render scale 150 %, 175 % and 200 % (up to a 3840x2160 scene for a 1920x1080 picture).
  • Game resolution 2560x1440 and 3840x2160 (Screen tab): the picture and the HUD are drawn at that size, sharp on a 1440p or 4K screen. DLSS and the game's FSR work there too. At 100 % the 3D scene is drawn 2 pixels smaller than the picture (2558x1438 at 1440p) and scaled up, so in-engine cutscenes show their whole picture.
  • Two-player co-op with a second controller: connect a second controller, pick "Two players" on the map, and the battle splits the screen; each controller drives and rumbles for its own player.
  • Updates without your NSPs: when the install folder already holds the game, the setup greys out the NSP folder and only offers Update, which builds from the game data the first install extracted.
  • RecompLauncher: the game resolution can be set from the launcher's settings too.

Update from 0.1.x

  • Windows: download AgeOfCalamityRecomp-v0.2.0-alpha-Windows-x64.zip, start AgeOfCalamityRecomp Setup.exe, keep the same install folder as before and press Update (this 0.2.0 setup does not need your NSPs again). Saves and settings are kept. The shader step runs again to add the new shader variants (about 4 minutes on the test PC); the shader cache grows by about 1 GB.
  • RecompLauncher: update the game there; it builds again by itself.
  • Linux: unpack AgeOfCalamityRecomp-v0.2.0-alpha-Linux-x64.tar.gz over your old folder and run sh setup.sh again.

Important

No game files are included. You need your own dump of the game: the base game NSP, the 1.3.0 update NSP, any DLC NSPs, and your prod.keys. First install: see the v0.1.0-alpha notes or the README.

120, 144 and 240 fps are still experimental. Steam Deck / Linux is still untested. Please report bugs with the dist/windows/logs folder from the install folder attached.

Full list of changes in the changelog.