-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shrek 2: less overall lag than real-console #312
Comments
Thanks for this. I am not sure how to address this yet besides hoping that general accuracy improvements will fix this eventually. |
I ran this on my GBPlayer and 2-4 end should be 5F45 rather than 5F54 |
Fixed now; that typo fix makes the math for 2-4 and 3-1 deltas make much more sense. @alyosha-tas Additionally, I have some newer patches: my older patch has saving, which complicates testing because flash cartridges won't have proper EEPROM timing. I made some patches that remove it. I also made a patch that disables prefetch. This
I'm not entirely happy with my versioning here, but hopefully that at least gives them distinct labels. |
I tried 0.5.4 on hardware, and I get 1-3 end is 1E27 instead of 1E25. I also get 1E27 on emulator. I didn't check all the values but I get the ending value of (25B0, 1D1D) on emulator. |
I rechecked by video footage, and the I also rechecked my 0.6.0 video, and the ending value of |
Using a TAS of Shrek 2 played back on emulator vs. real console for comparison, I found mGBA is currently ~17.9 seconds faster than real-console, while NanoBoyAdvance e170695 is net ~79 VBLANK frames faster than real-console (NBA 1.7.1 is ~81 frames faster than real console because it's an additional 2 frames faster in one level).
For testing, I modified the game to display frame count + "input" count in the top-right; here's a patch: Shrek_2_GBA_TASHack_0.4.1.bps.zip. It works by overwriting the game's input subroutine to play back hardcoded inputs. To use it, it requires starting with no save file and I hope to rework it to be more detailed, easier to use, and overall better in the next few months.
You can see how long a level took by seeing when the frame count freezes at the end of a level and comparing it to real-console. Here's what my results were:
Basically, on my AGS-101, it will display
2611,1D1D
by the end of 5-4, while on NBA it will display25C2,1D1D
29 July 2023: fixed a typo in 1-2 and 1-3 in the level diff/cumulative diff results. I also added SkyEmu results.
The text was updated successfully, but these errors were encountered: