Reply to thread

Message: [QUOTE="sandogma, post: 4342, member: 713"] I am not in the know so I'll defer to others who claim they are who chime in, but I do like learning about these kinds of things, so I took this as an opportunity and hopefully can share what I've learned. The NES’s Picture Processing Unit (PPU), which generates the 2D video signal, has a built-in limitation that restricts it to displaying only eight sprites per scanline. This means that if a game tries to render more than eight sprites on a single horizontal line of pixels, only the first eight will appear, causing some sprites to disappear as the NES tries to cycle through them. This limitation is often referred to as the "8-sprite-per-scanline limit". There is a technique where the PPU and CPU work together in reordering sprite data to alter the priority of the sprites on each scanline which causes the sprites to flicker instead of having some disappear entirely, this technique is referred to as Sprite Cycling, or OAM Cycling, as the OAM (Object Attribute Memory), which is part of the PPU, is involved. Left image - no Sprite Cycling Right image - Sprite Cycling implemented [ATTACH type="full" size="324x240"]1535[/ATTACH][ATTACH type="full" size="324x240"]1536[/ATTACH] Source: [URL]https://www.nesmakers.com/index.php?threads/4-1-5-sprite-cycling.2455/[/URL] Source: [URL]https://www.nesdev.org/wiki/PPU_rendering[/URL] [/QUOTE]

Totals may include hidden visitors.