Skip to content

Wind Waker Recomp 0.2.2 for Windows (x64) and macOS (Apple Silicon)

Choose a tag to compare

View all tags
@elliotttate elliotttate released this 01 Oct 03:17
v0.2.2
305fe7e

Wind Waker Recomp 0.2.2

Updated October 1 (Windows, same version). If you downloaded 0.2.2 earlier, download it again for:

  • One Frame rate list. Settings, Display now has a single Frame rate list:

    • 30 FPS (the game's own)
    • 60 FPS or 120 FPS with frame interpolation (the in-between frames that used to be
      called Smooth Motion)
    • 60 Hz game logic (experimental, not recommended), which makes the game itself run 60 times a
      second, so parts of it run too fast.

    Before, these were two separate settings and easy to mix up. Each choice now says what it does.
    F10 still turns frame interpolation off and on.

  • A more responsive mouse camera. The camera now uses the mouse's newest movement when it updates.
    Before, it used what had arrived by the previous frame. That shaves about 20 ms of delay on average
    (up to a full game frame, 33 ms), at 60 FPS and at 30. Measured on the test PC: the movement the
    camera used was 21.5 to 55 ms old before, and is now at most one game frame old.

Windows fix: going fullscreen no longer crashes. On some PCs, switching to fullscreen (F11, Alt+Enter
or the settings) crashed the game: it was reported on an Intel UHD 620 laptop, where every switch
crashed, and 0.2.1 did not fix it. While the window changed size, a frame from frame interpolation could be
shown at the same moment, using parts of the picture that were being replaced. That now waits for the
resize to finish. On slower graphics the two met often; on fast ones, rarely.

The Mac app is unchanged, so this release includes the latest Mac build, 0.2.0.

If the game runs slowly on a laptop with integrated graphics, choose 30 FPS (F10 turns frame
interpolation off) and set Render resolution to 1x in the settings (F1). Frame interpolation draws
each frame a second time to show 60 FPS, which doubles the work for the graphics chip. If it is still slow, please send the newest session
log from %APPDATA%\BlueWake\logs with your report. It names your CPU and GPU, and each second it says
which part held the game back.

From 0.2.1 and 0.2.0: closing the game no longer shows an error; Restart now in the settings no
longer crashes; save states (F5 saves, F8 on Windows or F9 on Mac loads); climb any wall.

Downloads

  • Windows (x64, Windows 10 or 11): WindWakerRecomp-0.2.2-windows-x64.zip. Unpack it and run
    BlueWake.exe; saves, settings and save states carry over. Built from windows-release at 9511241
    (RecompCore 9618e9d); WindWakerRecomp-0.2.2-windows-source.zip is that source.
  • Mac (Apple Silicon, macOS 15 or later): WindWakerRecomp-0.2.0-macos-arm64.zip, the same build
    as in v0.2.0 and v0.2.1.

Both need your own disc (GameCube USA, GZLE01 revision 0: .iso, .gcm or a compressed image such
as .rvz). Windows also needs a Direct3D 12 GPU and a CPU with AVX2. No game data is included.

Checked (Windows, i9-13900KF, RTX 5090)

  • The crash, reproduced. The crash was made likely by holding the game to two CPU threads with a
    4x render scale, and pressing F11 30 times, 0.15 to 0.9 seconds apart. 0.2.1 crashed after 9 presses
    in one run and after 21 in another.
  • With the fix:
    • The same test gave 150 switches in five runs without a crash.
    • Every run closed normally.
  • Nothing else changed:
    • Every captured frame is the same as 0.1.0's.
    • The in-between frames of frame interpolation are the same.
    • The speed is unchanged: full speed on 12 efficiency cores standing in for a slower CPU.
    • The translated game is the same as in 0.2.1; the two game modules differ only in their link time
      stamp.
  • The download unpacked fresh:
    • The first launch prepared an .rvz.
    • The game played at 60 FPS.
    • A save state was saved and loaded.
    • It took 5 fullscreen switches.
    • Closing the window ended normally.

For the October 1 update:

  • Frame rate list: each of the four choices was made in a running game. It showed what it does,
    and the settings file kept it.
  • Mouse: with scripted movement sent through the same event queue as a real mouse, the camera
    began turning a game frame sooner than before and ended at the same angle, so no movement is lost
    or counted twice.
  • Nothing else changed:
    • Every captured frame is still 0.1.0's.
    • Fullscreen survived 30 quick switches.
    • The download unpacked fresh, played, took fullscreen switches and closed normally.
    • The translated game is the same as in the first 0.2.2.

Checksums (SHA-256)

  • WindWakerRecomp-0.2.2-windows-x64.zip: 939a5ee8084169b9601548af0fa18f46b6f298a5248abd82117d019ed501b71d
  • WindWakerRecomp-0.2.2-windows-source.zip: 4276e3d31c4a5f44bb4010f934d96228d12857426f07f125f5296cd489432635
  • WindWakerRecomp-0.2.0-macos-arm64.zip: 4870a538122a5dc7e2ae8079ff1c7507418c72843af26c953a9a8b7887a2b330
Assets 8
Loading