bsnes-plus (or bsnes+) is a fork of bsnes (based on bsnes-classic) intended to introduce some new features and improvements, mostly aimed at debugging.
- Improved debugger UI with register editing
- Redesigned memory editor and breakpoint editor
- Improved handling of address mirroring for breakpoints (extends to the entire address space, not just RAM)
- Real-time code and data highlighting in memory editor, with fast searching for known code/data locations and unexplored regions
- Cartridge ROM and RAM views in memory editor for mapper-agnostic analysis
- Enhanced VRAM, sprite, and tilemap viewing
- SA-1 disassembly and debugging
- SA-1 bus and BW-RAM viewing and (partial) usage logging
- Super FX disassembly and debugging
- Super FX bus viewing and usage logging
- Satellaview / BS-X support
- SPC file dumping
- SPC output visualizer (keyboards & peak meters)
- IPS and BPS soft patching
- Multiple emulation improvements backported from bsnes/higan (mostly via bsnes-classic)
Up-to-date development builds are available from AppVeyor (64-bit Windows, compatibility and accuracy profiles).
Building on Windows
- Get mingw-w64 (make sure toolchain supports 64-bit builds)
- Initialize the bsnes-plus-ext-qt submodule in git
Building on OS X
Currently, OS X is not officially 100% supported. See this fork for now.
Building on Linux / other *nix
As there is no
configure step, make sure necessary Qt5/X11 packages are installed. On a Debian/Ubuntu system, it would require a command like:
sudo apt install qt5-default qtbase5-dev-tools libxv-dev libsdl1.2-dev libao-dev libopenal-dev g++
make and if everything works out correctly you will find the output binary in the
The snesfilter, snesreader, and supergameboy plugins can all be built by running make (or mingw32-make) after you've configured your environment to build bsnes itself. After building, just copy the .dll, .so, or .dylib files into the same directory as bsnes itself.
bsnes v073 and its derivatives are licensed under the GPL v2; see Help > License ... for more information.
See Help > Documentation ... for a list of authors.