Talk:PPU palettes: Difference between revisions

From NESdev Wiki
Jump to navigationJump to search
Line 13: Line 13:
The palette values from this table are read from left to right, then up -> down. Is this ok?
The palette values from this table are read from left to right, then up -> down. Is this ok?


00 01 02 03 ... 0F
00 01 02 03 ... 0F<br>
10 11 12 13 ... 1F
10 11 12 13 ... 1F<br>
20 ...
20 ...

Revision as of 12:42, 28 December 2013

It says that the background palette hack can be used to display the unused palette data. Can the EXT pins also do this? --Zzo38 (talk) 22:30, 1 July 2013 (MDT)

Yes, I think so. While rendering background pixels, the palette index that gets looked up is simply 0<exp_in3><exp_in2><exp_in1><exp_in0>. -Ulfalizer (talk) 03:58, 2 July 2013 (MDT)
Interestingly, it looks like the background palette hack wouldn't work for output to the EXT pins though (bit 6 of $2000 set). The logic that causes the VRAM address to be used for the palette index while the background palette hack is active comes after the logic that outputs the index to the EXT pins. -Ulfalizer (talk) 04:15, 2 July 2013 (MDT)
Thank you for information. I suppose if you are using the master/slave, you can connect the EXT pins in reverse (EXT0 to EXT3, EXT1 to EXT2, EXT2 to EXT1, EXT3 to EXT0) so that this can be used to make extra colors. --Zzo38 (talk) 23:05, 2 July 2013 (MDT)

Source of palette

Where did the palette added by Lidnariq in this edit come from? --Tepples (talk) 18:56, 25 December 2013 (MST)

Screenshot from Nestopia running blargg's full_colors and nes_ntsc. Feel free to bikeshed. —Lidnariq (talk) 20:00, 25 December 2013 (MST)

Parsing the palette

The palette values from this table are read from left to right, then up -> down. Is this ok?

00 01 02 03 ... 0F
10 11 12 13 ... 1F
20 ...