Skip to content

v0.1.7

Choose a tag to compare

@github-actions github-actions released this 11 Nov 05:57
· 385 commits to main since this release

Install

  • Windows: download DissidiaRecomp-Setup-0.1.7-windows-x86_64.exe and run it. It unpacks itself on the first start.
  • Linux: download DissidiaRecomp-Setup-0.1.7-linux-x86_64, chmod +x it and run it.
  • The .tar.xz / .zip archives hold the same files if you prefer to unpack them yourself.
  • You need your own copy of the game (ISO or CSO). The wizard writes setup.log into the install folder; attach it to bug reports.

Changes since v0.1.6

  • README: prebuilt releases, runtime features
  • Frame rate: scale the fixed UI animation step above 30 Hz (VS banner at fight start ran too fast)
  • Test driver: player picked by charId, per-fight input recording, FDUMP in test runs, --watch / --stage / --hold options; drop the never-called move-toward hook; document the Revolver Drive steered-move fix (steer hook already in the tree); replay of a recorded Revolver Drive
  • Frame rate: scale the steered ground move controller's per-update distance (Squall's Revolver Drive rush ran 4x as fast at 120 fps); drop the never-called move-toward hook; ALLOW_PTRACE aid; replay of a recorded Revolver Drive
  • Frame rate: EX Burst quicktime, countdown and release gauge at 30 Hz above 30 fps (controller + UI gated, sticky press edges, timer dt scaled), docs
  • Cloud sync of saves between devices (folder, WebDAV, Google Drive)
  • Test driver: FDUMP in test runs regardless of script id; no speed-slot hook (no effect on Revolver Drive)
  • Battle test: player picked by charId (Squall 15), per-fight input recording, --watch for the memory-write watch, move-toward call log
  • Frame rate: PSPRECOMP_MOVE_TOWARD=0 switches the move-toward hook off (A/B)
  • Battle test: stage selection (default 12), dummy keeps its HP, first-script metrics, motion time in fighter log
  • Battle test harness: headless menu walk, scripted/recorded pad input in game time, action starts any move, CPU freeze, 30 vs 120 comparison (tools/battle_test.py, docs/testing.md)
  • Settings menu: every row's help says L / R changes page
  • Android: declare INTERNET permission; say why ad-hoc is off in the Network status
  • Test driver: scripted/recorded pad input in game time (PSPRECOMP_TEST_SCRIPT, PSPRECOMP_INPUT_RECORD), gt= in fighter/motion logs