Talk:PPU attribute tables

From Nesdev wiki
Jump to: navigation, search

- Even if the NES does not display a picture of 256x256 pixels, it's technically possible to do. I studied the Mega Man II gfx engine a few years ago, and my level editor renders a full picture of 256x256 pixels. In other words, even if the NES cuts off 2xF8 by half, it's still technically possible to render it.


Attribute Equation Order[edit]

It may be a little better to have this:

value = (topleft << 0) | (topright << 2) | (bottomleft << 4) | (bottomright << 6)

ordered like this:

value = (bottomright << 6) | (bottomleft << 4) | (topright << 2) | (topleft << 0)


Obviously the result is the same, but the second one keeps the order they'd be in the byte after the actual bit shifts. Bottomright would be in the far left of the byte, etc. It makes it easier to quickly glance and see the order. Just a thought, since I don't know if the current way is the standard way of representing bit shift equations or something. --Kasumi 02:24, 27 September 2011 (UTC)

Can we get a screenshot?[edit]

I think it'd help if we had a picture depicting how the attribute table works, using basically a screenshot of the NES nametable (i.e. a screenshot) and then a grid overlayed/splitting up the sections and depicting what attribute table bit/entry correlates with what part of the palette, and the RAM offsets on X/Y axis as well. I don't think ASCII works well for depicting this clearly. I actually find the way i described it in nestech.txt, with words (I think I described it 4 different ways), to be more useful. --Koitsu in #nesdev

I might use a screenshot of Thwaite for this. --Tepples (talk) 16:21, 21 March 2015 (MDT)