Closed BenjaminEHowe closed 3 weeks ago
Don't know what's going on with your game but this isn't the case
That's... fascinating. I thought it might be a simple ordering problem, but clearly it's something more complex.
I'm using John GBAC on Android -- what emulator are you using?
MGBA, and it's been tested by our playtesters on multiple different emulators. Did you build from the repo or use the patch? If it is the patch I recommend you check your SHA1 hash is correct (80956dfc8f617668878c36245377091622553d6d) otherwise something has gone wrong and I'd redownload the patches and repatch.
I used the patch. I think I've fixed the problem, but I've no idea how I caused it...
When I renamed the patched file in the GUI file manager (Linux Mint Cinnamon Edition 20.2), the hash changed to 5d680e0105be0ef5ce1fadccb1e1dbaae0dd1302
. When I renamed it via the terminal / mv
, the hash remained 80956dfc8f617668878c36245377091622553d6d
and this bug goes away.
Any ideas what might be going on behind the scenes? I never opened the file so wouldn't expect the hash to change!
There was a broken patch that was out for a small amount of time on launch (I have genuinely no idea how this happened because I made the patch with the same roms using the same site as the updated one) which resulted in that. If you downloaded within the first few minutes you may have gotten that.
But I'm pretty sure it should be DRK.