Popslide: a generic video memory updater

A place where you can keep others updated about your NES-related projects through screenshots, videos or information in general.

Moderator: Moderators

Post Reply
tepples
Posts: 21752
Joined: Sun Sep 19, 2004 11:12 pm
Location: NE Indiana, USA (NTSC)
Contact:

Popslide: a generic video memory updater

Post by tepples » Tue Jan 24, 2017 10:01 pm

Popslide is a video memory update buffer framework for the Nintendo Entertainment System.

NES games need to update video memory in numerous ways during gameplay. But the frame rendering circuitry in the PPU has exclusive access to video memory while it sends the picture to the TV. So games usually buffer updates in RAM. An unused part of the stack is a convenient place to stash such a buffer, big enough to hold the largest practical VRAM update on NTSC.

Some games have only one update routine because all the updates they do are so similar. Others have multiple update routines, one for each kind of update, such as nametable columns, nametable rows, rectangular areas, tile uploads, attribute uploads, and the like. Still others embed information about the shape of an update in the buffer. This is the approach used by Super Mario Bros. and other games using NES Stripe Image format.

Popslide interprets an NES Stripe Image buffer in the stack page, using PLA as an autoincrementing read instruction. It comes in three forms: a looping version, a partially unrolled (16x) version, and a fully unrolled (64x) version.
Attachments
popslide-0.01.zip
(26.68 KiB) Downloaded 517 times

JRoatch
Formerly 43110
Posts: 388
Joined: Wed Feb 05, 2014 7:01 am
Location: us-east
Contact:

Re: Popslide: a generic video memory updater

Post by JRoatch » Sat Feb 04, 2017 10:28 am

Since this "needs feedback badly".

I have been working on a PPU update buffer system very much like this since you started talking about NES Stripe Image format a few months back. Comparing with what I have the one similarity is using pla like in popslide. Other than that, these are the differences:
  • The "increment 32" is put into bit 7 of the address high byte.
  • The maximum length of the strings are then 128, with only bit 7 signifying the run or literal mode.
  • The terminator can then go into the bit 6 of the address high byte, but I don't use this.
  • Instead I use a counter for the number of strings to write, this way the buffer as a whole is always valid for the vblank routine even in the middle of writing a string.

Post Reply