koitsu wrote:
Your whole metasprite + sprite concept here seems very... I don't know. I sort of get the impression you don't understand what SpriteBuf1/SpriteBuf2 do (meaning what they're for and how the SNES uses them), but there's a 50% chance I'm completely wrong and it's just that you haven't written the rest of the code but have designed it somewhere (in which case I apologise + ignore me). But I now understand why you want to "move to 16-bit" -- because the MSB (9th bit) of the Y position of a sprite is separate from the remaining 8 bits. I now actually understand what's needed to make all of that work, but I wish I had a better idea ultimately what your goal was.
???

SpriteBuf1 has 4bytes per sprite (X and Y positions, character data, and extra) for a total of 512 bytes and Spritebuf2 has each sprites most significant X bit and sprite size selection bit, and it is 32 bytes long. SpriteBuf1 and 2 then get DMAed to OAM during VBlank.
koitsu wrote:
P.S. -- One of these days I wanna see what psychopathicteen has been working on for like the past 8 billion years.
I don't know. He's probably making something insane.

By the way, I made the metasprite routine use 16 bits (I haven't implemented the 9th x, not y

bit yet, as it currently just gets erased when storing the number in spritebuf1) and it worked flawlessly, but I tried to make it where you add XPosition and YPosition to the number in the table that gets stored in SpriteBuf1, but the assembler didn't like it.

Edit: I forgot to CLC before ADCing, but it didn't make a difference. (I'm really not sure why it would, but I tried.)
Attachment:
Code.png [ 26.16 KiB | Viewed 2567 times ]
Attachment:
Code Extended.png [ 31.61 KiB | Viewed 2566 times ]
Attachment:
Assember Problem.png [ 11.78 KiB | Viewed 2566 times ]