The Loopy_V properties...

This is an archive of a topic from NESdev BBS, taken in mid-October 2019 before a server upgrade.
View original topic
The Loopy_V properties...
by on (#48138)
I read nesdevwiki PPU Scrolling and loopy documents and I have implemented the behaviors...
However I would like to understand how really works the loopy_v on scanline rendering....

I mean during the 256 pixels how can I deal with nametable address , attribute address?

Imagine that we are rendering the bg (nametable) so:

We firstly will made a 256 loop...

for (int pixel = 0 ; pixel < 256 ; pixel++ ){

How do I know which nametable address is? (taking the D0-D11 as loopy suggest... gives me a 0x0020) and attribute?

by on (#48143)
Give my experimental in work doc for nes emu programmers a read
http://spark.ofloo.net/~qeed/nes_emu.txt :lol: I cover loopys doc in there with code :P

by on (#48145)
qeed wrote:
Give my experimental in work doc for nes emu programmers a read
http://spark.ofloo.net/~qeed/nes_emu.txt :lol: I cover loopys doc in there with code :P


If you think that the state is not too experimental, it would be great to add it to the new wiki.