I'm reading the wiki page on sprite timing here, and just wanted to clarify something quickly.
Taking into consideration the note about odd/even cycles...
Am I correct in interpreting this step as taking 6 PPU cycles, one for each read from primary oam and one for each write to secondary OAM?
More generally, all reads and all writes from primary OAM to secondary OAM occur on separate cycles during sprite evaluation?
Quote:
Cycles 65-256: Sprite evaluation
On odd cycles, data is read from (primary) OAM
On even cycles, data is written to secondary OAM (unless secondary OAM is full, in which case it will read the value in secondary OAM instead)
On odd cycles, data is read from (primary) OAM
On even cycles, data is written to secondary OAM (unless secondary OAM is full, in which case it will read the value in secondary OAM instead)
Taking into consideration the note about odd/even cycles...
Quote:
1a. If Y-coordinate is in range, copy remaining bytes of sprite data (OAM[n][1] thru OAM[n][3]) into secondary OAM.
Am I correct in interpreting this step as taking 6 PPU cycles, one for each read from primary oam and one for each write to secondary OAM?
More generally, all reads and all writes from primary OAM to secondary OAM occur on separate cycles during sprite evaluation?