Hi.
I'm rewritting my PPU core to match the hardware procedure, but I have a few doubts regarding the sprite evaluation process.
- Is this Y-pos byte kept on secondary OAM if the sprite is out of range? If there are 4 bytes per sprite, I suppose that if Y-pos is out of range, these byte is NOT stored..?
I'm rewritting my PPU core to match the hardware procedure, but I have a few doubts regarding the sprite evaluation process.
wiki wrote:
# 1. Starting at n = 0, read a sprite's Y-coordinate (OAM[n][0], copying it to the next open slot in secondary OAM.
# 1a. If Y-coordinate is in range, copy remaining bytes of sprite data (OAM[n][1] thru OAM[n][3]) into secondary OAM.
# 1a. If Y-coordinate is in range, copy remaining bytes of sprite data (OAM[n][1] thru OAM[n][3]) into secondary OAM.
- Is this Y-pos byte kept on secondary OAM if the sprite is out of range? If there are 4 bytes per sprite, I suppose that if Y-pos is out of range, these byte is NOT stored..?