BigPEmu
The World's Prefurred Large Pussycat Emulatorâ„¢

Home
Compatibility
FAQ
Bug Report
User Manual
Download
Contact

Patreon
Patrons are my only source of support for ongoing improvements to BigPEmu. Please consider adding your support! As a patron, you'll be treated to regular behind-the-scenes updates, screenshots of works in progress, and special pre-release builds.

Bug Report

When submitting a bug report, you'll need to select a saved state from the emulator which is relevant to the report. The location of BigPEmu saved states may vary by platform, but under Windows, they're located in %APPDATA%\BigPEmu. (this usually resolves to something like C:\Users\YourUsername\AppData\Roaming\BigPEmu) By default, the files will be named stateXXX.bigpstate, where XXX is the active state slot. If you have per-game states enabled, the state will be named gameXXXXXXXXXXXXXXXX_YYY.bigpstate, where XXXXXXXXXXXXXXXX is the game's 64-bit FNV-1a hash (you can see this hash for each of your files in the upper-right of application's file browser) and YYY is the active state slot.

Be sure to state the title of the software associated with the saved state. I may be able to divine this from the hash in the saved state data, but not if you're running something (or a version of something) that I don't already have sitting around. Additionally, and this is important, please make sure you provide a saved state which was made shortly before your issue occurred, and describe in detail how I can reliably reproduce the problem by starting from the saved state. There's a possibility that I'll be able to figure out what went wrong from a saved state taken after the problem has already occurred, but in many cases, the damage is already done and there isn't enough forensic data to be able to work out exactly what happened. For this reason, it's helpful if you save the state often while playing games and always try to hop back and reproduce the problem when a problem does occur.

It may also be useful if you provide some way for me to contact you in the report, this will allow me to follow up with any questions I might have about reproducing the problem you're having. There are many cases where reproducing an issue isn't especially straightforward or reliable, and the ability to ask follow-up questions can be very helpful.

If you're reporting a bug which pertains to any of the titles listed on the compatibility page, first make sure the FNV-1a hash of your cartridge image matches the hash listed on that page. Bug reports will be ignored if they apply to bad dumps, ROM images with missing headers, and so on.

Note that only 5 reports are retained per IP address. This count doesn't reset until I've reviewed and cleared the reports. If you've decided to go on a proper QA rampage and really have more than 5 unique bug reports for me, feel free to reach out directly.

Saved state file:


Description:






BigPEmu Copyright © 2022 Rich Whitehouse