Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Given that, whatever RGB the devkit might've been spitting out isn't "definitive" in the sense of how the artist intended anyone to see it.

Sure, but that's not what I meant.

Back when images were being bit-banged into computers, you didn't really care what the results looked like on the screen of your workstation, if your workstation wasn't the target system. You designed on paper — usually grid paper — and then iterated from there by flashing an EEPROM and checking the results on the machine.

When I say "the design colors", I mean the marker-pen colors used to color the grid paper. You might also call these the "pre-color-grading" palette.

Certainly, the artist would get a different idea about what they wanted a thing to look like, once the image had been passed through the "color grading" of the NES palette; and so would then iterate toward a design that most-closely lined up the vision in their head with what the NES could actually produce.

But the artist's original intent wasn't to achieve that iteratatively-color-graded final result image; it was to achieve the original colors they had put down on the grid paper. That original intent was just stymied by the system; and so they had to settle for the colors the system could do.

(I realize that modern designers working with retro art styles often design from scratch under palette constraints; but video games were much newer then, and so most of the professional art-and-design people working in the industry had never done digital art before, and had been trained / previously worked only in traditional art. The closest their designers would have got to the kind of constraints imposed by the NES would be in designing neon signs.)



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: