The Core for Deadline-Demoparty, Berlin 2016
The first demo I ( @Nodepond) made together with @gruber_music.
Demo was released at the deadline-party in Berlin an made the 3rd-place at the combined newschool demo category. Pico-8 is still not a single category in the demoscene yet, but more and more people hear about pico-8.
https://demozoo.org/productions/163764/
I have a question on the pico-8 palette. Sometimes I observed the behavior, that some colors changes on the pico-8 palette, when messing around with .png's.
For example, if I save screenshot directly from pico-8 and open it in an editor, that red, i.e. is sometimes displayed at R 251, G 0, B 61.
When I open the official pico-8 palette in one editor (in that case PikoPixel, OS-X), than red is again R 251, G 0, B 61. If I open the same file in another editor (Pyxel Edit, OS-X), then red becomes R 255, G 0, B 77. If I import the same image as palette in Pyxel Edit, red again becomes R 251, G 0, B 61.
Is someone able to explain this behavior? Or had similar observations and can help by adding use-cases?
I wrote a little tool, that converts 128x128 .png images to native .p8 code. It does not import the image to mapdata, (like https://www.lexaloffle.com/bbs/?tid=2715), but converts it to native code.
https://github.com/nodepond/pic2pico/
Currently only exact matching colors are transfered into code.
This tool might be useful, if you want a background, but also have sprites for i.e. displaying text. Of of the next features might be some compressing of image data, to show even more images.
A drawing tool, inspired by PETSCII and live-drawing in front of an audience. Shout out to Raquel Meyers for being a constant source of inspiration!