The 8-4 timing works now, thanks. However there now is another possibly related bug, which is not that significant but still not intended behaviour. After landing on the axe, the time was shown and mario kept running/walking, fell off the axe block to the left and got pushed through the wall below the axe as the screen scrolled. He also keeps the walking animation while usually standing while the messages appear. Screenshot: https://imgur.com/a/oN9DwJX
It only happens sometimes, I had it happen 2 out of 3 8-4 completions so far.
Hehe yeah I saw that but didnt care enough to fix it :) One of the blocks in the wall where the prince is kept is overwritten too. I'll fix it at some point :)
I finally got around to messing with this and quickly found myself in this situation, lol https://imgur.com/J3cB5Sc
it seems using the built in savestates causes a lot of palette glitches lol
Hehe yea they cause a lot of problems in general :) Did you try to load twice? Actually if it is a palette thing its probably not gonna help. Did you load across levels do you know?
Released 5.3
Changes:
- Disabled B in pause menu.
- Fixed a million bugs related to save states
- Fix rendering issue when showing RTA time @ 8-4s and D-4
Released 5.4
Features:
- Ability to wipe SMB/LL/LL-EXT records under settings.
5.4 bug fixes:
- When starting on a specific rule in Lost Levels the frame counter was set incorrectly, which could cause rule-deviations vs. vanilla.
- Use the coin-sprite for sprite0 in LL (no more glitchy garbage under the coin).
- The Save-state is no longer invalidated as you power the machine on and off.
Get it at https://pellsson.github.io/smb
EDIT: Oh, and of course, huge thanks to @goofychocobo who saved me a countless hours hunting for a ghost-bug that didn't really exist (but resulted in finding the framecounter bug mentioned above). Thank you very much <3 :)
Fixed bug with character selection at titlescreen (Updated the IPS, but did not bump version number). Thanks @threecreepio :D
Release v5.6
- Fixed bug where loading state would cause a subsequent save if select was still held; causing a lot of strange corruptions and stability issues.
- Fixed sprite & WRAM corruption causing a softlock (and worse on physical carts).
- Sanity check settings.
Any% (NTSC) runs below 4:57.000 must now fulfill additional requirements in order to be verified.
- The run's full session must be included in the submission description.
- For emulator runs below 4:57.000, some form of input display must be visible for the duration of the run. A hand-cam or input
