Buu’s Fury is escaping the Game Boy Advance with a new PC recompilation

Dragon Ball Z: Buu’s Fury is getting a new way to run on PC. Instead of putting the Game Boy Advance version inside a standard emulator, this project recompiles the original game code so it can run as a native Windows application. It’s still experimental, so this isn’t a finished PC port you can simply install and forget about. But the basics are already there. The game boots, runs in Windows, supports keyboards and modern controllers, handles normal cartridge saves and adds save states. There’s also an optional widescreen mode that can show more of the game world instead of just stretching the original picture. Players still need their own compatible US game ROM and a Game Boy Advance BIOS. Neither is included.

Dragon Ball Z: Buu’s Fury is getting a new way to run on PC. Instead of putting the Game Boy Advance version inside a standard emulator, this project recompiles the original game code so it can run as a native Windows application. It’s still experimental, so this isn’t a finished PC port you can simply install and forget about. But the basics are already there. The game boots, runs in Windows, supports keyboards and modern controllers, handles normal cartridge saves and adds save states. There’s also an optional widescreen mode that can show more of the game world instead of just stretching the original picture. Players still need their own compatible US game ROM and a Game Boy Advance BIOS. Neither is included.

How the Buu’s Fury recompilation works

The project uses GBARecomp, a system designed to translate Game Boy Advance machine code into C++. That translated code can then be compiled for modern hardware. That distinction matters.

A normal emulator recreates the behaviour of the entire Game Boy Advance and runs the original software inside that simulated hardware. Here, much of the game itself is converted into native code. A separate runtime then handles the GBA hardware functions the game still expects, including graphics, sound, timers, interrupts, controls and save memory. From the player’s side, most of that stays out of sight. You launch the Windows program, point it towards the required game and BIOS files, configure a few options and start playing.

The launcher can remember valid files for later sessions. It also gives players control over display settings, sound and input. Both keyboard and gamepad controls can be remapped, and the game can run in either a window or full-screen. Save states are included too, sitting alongside the game’s normal save system.

Widescreen shows more than the original GBA screen

One of the more interesting additions is Adaptive Widescreen. The Game Boy Advance originally displayed games at 240 × 160 pixels. That original view is still supported, so nothing forces players to change it. Switch widescreen on, though, and the visible game area can expand horizontally as the window gets wider. At its largest setting, the logical view can reach 480 × 160.

This isn’t the same as taking a 4:3 image and pulling it sideways until it fills a modern monitor. The game actually shows more of the surrounding area. Characters can remain visible across a wider field, and interface elements move to suit the extra space.

That takes more work than a basic display filter because Buu’s Fury was built around a fixed handheld screen. Areas, characters and HUD elements all assume those original dimensions. The recompilation has to account for that when it opens up the view. If you’d rather keep things exactly at the GBA’s original dimensions, you can.

A quick look back at Buu’s Fury

Dragon Ball Z: Buu’s Fury arrived on the Game Boy Advance in 2004. Webfoot Technologies developed it, with Atari publishing the North American release. It followed Dragon Ball Z: The Legacy of Goku II and kept the same basic action-RPG approach. You explore areas, fight enemies in real time, gain experience, improve character stats and equip items.

The story focuses on the later part of Dragon Ball Z, particularly the Majin Buu storyline. It also covers material leading into that conflict, including the Other World Tournament. Players control several familiar characters, including Goku, Vegeta, Gohan, Goten and Trunks. Each has different abilities, attacks and transformations. Combat mixes close-range fighting with Ki attacks, while the RPG systems give players reasons to level characters and adjust equipment between battles.

That mix makes Buu’s Fury quite different from a typical Dragon Ball fighting game. There’s plenty of combat, but there are also towns, menus, scripted scenes, exploration and character progression. All of those systems have to behave properly in the Windows recompilation.

It’s playable, but still experimental

The current public version is 0.0.2. That release updates the recompilation framework, regenerates the translated game code and includes additional work aimed at Windows x64. It also removes an earlier runtime step limit. Still, the project doesn’t claim that every part of Buu’s Fury has been tested from start to finish. Bugs are possible, and some parts of the game may behave differently from the original hardware.

There’s another practical limitation. The software targets a specific US version of the game, so players need matching files. The project doesn’t bundle the ROM or Nintendo’s GBA BIOS. What you get instead is the recompilation layer itself: a Windows-native way to run that specific version of Buu’s Fury, with modern controller support, flexible display settings, save states and an optional wider view. It’s a very different approach from simply opening the game in an emulator, and that difference is really the point.

Spread the love
error: