Sorry about the double post, but I need some help here.
I finally found the address for the player's X position at 4F, but it is weird. Moving the player from the far left side of the screen towards the right, the address shows these values in the following sequence: 11, 01, f1, e1, d1, c1, b1, a1, 91, 72, 62, 52, 42, 32, 22, 12, 02, f2, e2, d2, c2, b2, a2, 92, 73, 63, 53, and so on, all the way up to aa at the far right of the screen.
As you may be able to see, the left nibble actually descends as the player goes to the right, whereas the right nibble is treated as the upper nibble and ascends as the player goes to the right. The left nibble also skips the number 8, and the right nibble increments every time the left nibble hits 9.
Is there a way I can view this information in a more meaningful way? I'd like to be able to view it from a more traditional sort of view, much like the well-behaved Y position at 5C.
Moreover, this is one of the many ROMs that Bizhawk appears to be emulating incorrectly, as the player's visible X location on the screen skips a number of pixels near the left side of the screen. I am fairly certain this does not happen on a regular console, and a number of different a26 ROMs behave in this same, odd fashion. Should I just wait for Bizhawk to receive an update that corrects this? Conceivably, it wouldn't be an issue for the Mountain Zone or the Sticks Zone, as I don't intend to leave any survivors that could cross that point, nor for the City of Mystery or Gondor, as everything either moves vertically or never reaches that point of the screen. It might become an issue in the Rainbow Zones that regularly move sprites horizontally across that region of the screen, or the Stripe Zone if sprites there actually do (I don't rightly remember). While a TAS could be made, I wonder if it would desync in a later version of Bizhawk that does not experience this problem.
