nesdev.com

So I took a couple days to tackle a problem I had to deal with a couple of times: Fitting complex images into the 256 tile limit.
What I basically tried out was an automated version of the process I end up do manually. Randomly search for 2 similar tiles that are unique in the nametable and merge them in some way.

In this program similar tiles are pairs of tiles that have the least number of pixels changed, and merging is randomly selecting the pixels from both tiles

Example image NES screen sized image with way too many distinct tiles (471)

Source: https://twitter.com/azumakiyohiko/status/495548119048679426

After merging tiles together until there's only 256 unique ones.


Results vary due to random pixel selections between tiles. Not the best of quality, but looks on par with the worst JPEG compression. In any case I figured this hack of a tool might be useful to someone. It's input is the output of tepple's pilbmp2nes.py

Edit: Attachment moved off site to compress-nes-image.py

Two ideas that might improve results:

1. Instead of just "number of changed pixels", multiply this number by the number of times that either tile is being used in the image. That will give you the total number of pixels changed in the whole image, rather than just the number changed in the individual tiles. (Also might guide the merging process; i.e. where pixels differ, take more from the one that is used more.)

2. Use a 3x3 neighbourhood to weight the importance of pixel changes. e.g. if you're about to place a black pixel into a 3x3 region of white pixels, consider this a greater change than placing a black pixel next to a group of black pixels just extending an edge, etc. This might let you favour changes that don't stand out as much? (Also gives you a way to choose which pixels to keep from the two merging tiles.)

Suggestion 1 about counting the pixel changes of the whole image helped a lot. What is measured now better matches what's changed. Combined with the suggestion to bias the merge changes, this now does subtle changes to more tiles rather then big changes to less.



I not sure how to work in suggestion 2. I did try something with a 3x3 region, but I must of severely messed up the weights because the result was garbage.

The way I see the problem is that tiles with opposite edges and corners are matched together, but every time I try to fix the random edge dots, the overall picture gets worse. I'm starting to think the random dots are actually a feature and the best compromise for reducing the tileset.

A thing that I might try another day is to factor in a manually made mask that prevents select pixels from changing. So that some crucial details, like faces, are preserved.

Edit: Attachment moved off site to compress-nes-image-2.py

471? That's honestly not too bad. With fullscreen scenes like this, I say screw the limitations!

I tend to limit my RPG's *ahem* "cutscenes" to 448 tiles, with a timed $00/$10 background split, to use more on-screen tiles. The rest is used for sprite overlays, to enhance the scene. It's all done by hand, on my end, though.

Thanks JRoatch for creating (and publishing) this!
It's fantastic and is already helping me a lot with a NES project.

User NESRocks is also using this - and even created a .BAT to make it easier to use (just drop the BMP file to convert.bat).
I'm attaching it here.

Are you planning to release a version that also removes the duplicated tiles?
It can be done on NES Screen Tool, just asking for curiosity.

Thanks! =)

Looks like this really rocks ! Drawing such a scene limited to 256 tiles should be hard, a bit of automation can always help.

Also, for those pointing to the possibility of doing raster effects trickery to bypass the limitation, I'd add that there's a million of reason why you'd want to stick to vanialla 256 tiles and not want to deal with PPU register writes midframe at all.

A masking feature sounds like a very sensible option to be able to use.

Currently, i'm doing this completely manually.

_________________
http://www.frankengraphics.com - personal NES blog

Would you be willing to make compress-nes-image-2.py available under a free software license so that I can incorporate it into my NES background tools?

Sure, it's now under the "Expat License".

Many thanks.

Some example of as use the output_result.chr and input_tiles.chr In a project?

_________________
https://maquinaslibres.noblogs.org/tag/8bit/
http://4232.cf/

My ff-uniq program will remove duplicated tiles from a tileset. However, it does not use the Famicom format directly (but ffbit and bitff can be used to convert in either direction).

_________________
.

I've started refactoring what I'm calling "JRoatch's Tile Vector Quantizer" to make it more usable from within other Python programs.

• biased_random_byte() now called biased_getrandbits() and allows changing word width like random.getrandbits()
• Can be imported as a library
• Variable output tile count
• Takes a filelike for logging the tile count
• Input and output filenames passed through command line instead of hardcoded

I'll probably add a way to remove duplicated tiles when I integrate it into savtool.

Hay! This is pretty neat. I wrote something kinda similar a few years ago for the Gameduino. It used 8x8 4bpp tiles with individual 16bpp palettes. It made using photo input pretty easy, though it looked kinda terrible.



I've been musing about doing something similar for the NES. Will have to give it a try.

_________________
https://maquinaslibres.noblogs.org/tag/8bit/
http://4232.cf/