Advertisement
fig02

Epona issue with Mupen64plus Next

Apr 10th, 2020
208
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.37 KB | None | 0 0
  1. Epona issue with Mupen64plus Next
  2. All of the addresses given here are for the NTSC 1.0 version of the game.
  3.  
  4. The instruction that crashes is located at 8039E08C in RAM.
  5. This is in a function located at 8039DE78 that seems to deal with interface/HUD things related to the
  6. player (just a guess)
  7.  
  8. The instruction crashes because its trying to read data from a pointer in the v1 register.
  9. This pointer is expected to be Epona's instance. It gets loaded from a variable in Links instance
  10. which we call the "rideActor". That is, a pointer to whatever actor link is riding. This pointer is located at
  11. link+0x430 (801DAE60ā€¬).
  12. The code that crashes does not have a null check before it tries to read from the rideActor, so it is expecting it to not be null.
  13.  
  14. After having a look at the relevant function, the only condition this code should run in is if Links state flags
  15. have the 00800000 bit set, which denotes that Link is in the state of riding Epona. Links state flags are located
  16. at link+0x66C (801DB09Cā€¬).
  17.  
  18. If it can be figured out why Links state flags are being set incorrectly, this will probably help single out the issue.
  19. Someone reported in the speedrunning server the other day that it happened to them when they got hit by something and
  20. pulled out the hookshot at the same time. This definitely sounds related to Links state.
  21.  
  22. Thats all the info I have on it so far.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement