0.4.7 fixes problems reported after 0.4.6, mostly graphics on Windows and controls on Android. The HD pack has not changed and is still HD 1.1.
What’s new
- Windows: a likely fix for a crash at the title on some AMD graphics. A player’s Apex (Radeon 8060S) closed 0.4.6 at the title. The crash file added in 0.4.5 showed why: releases had the graphics driver’s debug checks on wherever Windows Graphics Tools or a Vulkan SDK is installed, and one sampling mismatch in drawing the menus stopped the game there. The checks are off in releases now, and the menus are drawn single-sampled, away from that path. I do not have this GPU, so please let me know if it works. Thanks to the player who sent the crash file.
- Garbled menus on some Intel graphics are most likely fixed too, by the same change. The anti-aliasing switch now applies to the game picture only; the menus stay sharp.
- Keys no longer stay held after a short story skip. When some short skips ended, the reader missed the end, so the touch buttons stayed on Stop skip and the D-pad and OK seemed held down.
- The map’s objectives screen no longer holds keys either; it was taken for dialogue.
- Android: a thumb rocking on the edge of the touch D-pad is one press, not two (it skipped a row on the pre-battle page), and a touch between its arms no longer takes the page’s focus.
- Pre-battle page: a tap beside the buttons (a pilot panel, a picture, the numbers) no longer drops the yellow focus frame.
- With battle animations off in widescreen, the HP window no longer jumps to the right edge for a target on the left.
- Widescreen: a story choice’s green bar stays inside its window.
- A new cheat: 4 part slots on every unit (Options → Cheats). Turned off, the parts in the extra slots go back to storage at the next intermission menu or load, so nothing is lost or counted twice.
- The parts cheat gives 15 of every part instead of 9. 9 is only the original’s drop threshold; 15 is the most a save keeps, so the original and emulators read such a save the same. The holder list shows 9 rows and scrolls.
- Android: the last three runs’ logs go to Documents/Marchwind64/logs, so a phone that cannot reach the settings can still send them; they show where each thread was when the game got stuck.
Known issues
- The black screen on the Redmi K60 and similar phones is not solved yet. The game gets stuck inside Qualcomm’s graphics driver while making the screen’s buffers, and nothing tried so far gets around it. If it happens to you, please send the logs from Documents/Marchwind64/logs on GitHub Issues with the phone model and Android version.
For other problems, Options → Report in the game copies the platform info and exports a problem report.
Android chips tested
The game starts and plays on real phones with these chips (Android 12–16). Entry-level chips like the Dimensity 6100+ run at about 14 FPS; the others mostly at 30. A chip that is not listed has simply not been tested yet; reports on Issues are welcome.
- Qualcomm: Snapdragon 865/870 (Adreno 650; Galaxy Tab S7, POCO F3), 888 (Adreno 660; Galaxy S21 Ultra), 8 Gen 1 (Adreno 730; Galaxy S22, Xiaomi 12), 8 Gen 2 (Adreno 740; Xiaomi 13, Galaxy S23), 8 Gen 3 (Adreno 750; Galaxy S24 Ultra), 8 Elite (Adreno 830; Galaxy S25)
- MediaTek: Dimensity 7300 (Mali-G615; Solana Seeker), Dimensity 6100+ (Mali-G57; Galaxy A15)
- Samsung: Exynos 1380 (Mali-G68; Galaxy A35)
- Google: Tensor G2 (Mali-G710; Pixel 7), Tensor G3 (Mali-G715; Pixel 8)
If you play on a Dimensity 8200 phone, please let us know whether it runs well.
Download
Get it from the install page or from GitHub. On Android it installs over the old version and keeps your saves; on Windows, extract it over the old folder. The previous changes are in the 0.4.6 notes, and the full feature list in the 0.4.0 release notes.