I'm trying to run Pico-8 on a Raspberry Pi 3 B+ with default Raspbian and OpenGL(Full KMS) driver, but keep getting the error
** FATAL ERROR: Unable to initialize SDL |
If use raspi-config and revert back to Legacy (non-GL) driver, then Pico8 runs properly.
I tried compiling my SDL2 manually using these instructions, but same thing: I keep getting the error to initialize SDL when running under accelerated OpenGL driver, and the only solution is to revert to Legacy driver, and reboot.
Any idea on how to solve it? I'm running other programs that require the OpenGL driver, and changing manually + reboot every time I want to run Pico8 is a big pain.
Thanks!
6 comments
It is Halloween, the year 19XX and the moon hangs low over a tiny village on the outskirts of Duskvale County. But this is no ordinary town. In this godforsaken place, two ancient wizards rise from the grave, on All Hallows' Eve, to duke it out in an all-out, fireball-fueled wizard battle. Caught in the crossfire of this ancient grudge are the villagers. These peaceful skeletons and humans, friends by day, are at night forced by the wizards into a terrible battle.
In this two-player nightmare, take up arms as Malufix, the Wizard of Light, or his immortal enemy, the Dark Warlock Bulfass. Burn your enemies and be the lone winner when the sun's first rays break the dawn. Who will win and become The King of Wizards?
1 comment
This is my first try at a metaballs effect in Pico 8. A bit disappointing: too much noise. Maybe I should consider using ordered dither instead of random noise. Doing internal calculations at a higher precision and then converting to 16 colors is also an option, but no way to make it work @60fps fullscreen.
I have just noticed there's a previous cartridge which did a very good job drawing metaball outlines: Metaballs (Demoscene Effect) by samuelks
3 comments
Scrub and me were just messing around, taking a bit of a break from Paint. He thought it would be interesting for us to write a topview Minecraft in Pico. I took it to mean it would be on a dot level and wrote some code to randomly create colors on the screen, bricks to build with.
But when you take out the colors and mirror the screen, you get a very nice Rorschach Test image.
https://en.wikipedia.org/wiki/Rorschach_test
NOTE: Every test picture has exactly 1001 pixels, no more, no less ! (or 2002 if you count the mirror).
What do you see ?
Post some of your favorites if you like and tell us what you think it is !
5 comments
Because 7 ate 9.
No, seriously, why is color #6 so close to color #7 ?
I mean, if you look at the decimal values for the three colors of 5, 6, and 7, you have:
N .. Red . Grn . Blu 05 . 095 087 079 06 . 194 195 199 07 . 255 255 255 |
You can calculate what color #6 should be based on taking each of the color guns and subtracting the difference from 7 and 5 adding the division by 2.
You would get:
N .. Red . Grn . Blu 05 . 095 087 079 06 . 175 171 167 07 . 255 255 255 |
So why the disparity ? And why are "gray" not matched all across the board ? If you median them out, (adding the 3 together and dividing by 3), you would have:
N .. Red . Grn . Blu 05 . 087 087 087 06 . 171 171 171 07 . 255 255 255 |
So why the current color disparity between grays ?
5 comments
ZX Spectrum allowed enabling XOR pixel operation for drawing routines and text. Some interesting interference patterns could be achieved this way.
3 comments
Controls
Menu: Z to start game.
Game: Left-click on trucks to move in the direction the truck is facing. Right-click on trucks to rotate them.
Game over: Z to restart.
Mechanics
Each level ends when you have used the trucks to collect every piece of rubbish. Click on a truck to move it in the direction it's facing. It will stop when it hits the edge of the screen, or another truck.
Commentary
Puzzle design is super difficult. But this game was a lot of fun to make! Designing the trucks and the rubbish kept me interested over the month, then in the last few days I finally figured out where I was going with it. I bumped over into November because of a number of commitments and other noisy stuff, but I'm very happy with how it came out. Maybe I will make more levels eventually? I'm sorry if it's very boring to people who do lots of puzzles!
itch.io page: here
4 comments
Hi everyone, I'm ReplayCoding.
The PICO-8 community has helped me a LOT learning PICO-8, so I thought I would give something back. So, I wrote the PICO-8 advanced manual! It contains my findings about PICO-8 internals and stuff like that... I hope you enjoy it!
Link: https://www.lexaloffle.com/bbs/files/28213/PICO-8_ADVANCED.zip
zep, please let txt files get uploaded :(
12 comments
Better late than never, here is a short Halloween game I had made with Wayne Kubiak (@WanyoDos on twitter) the artist.
"Hazel May heard that there was going to be a monster party on Halloween, but she didn't know that it would literally have monsters!
Help Hazel may get the monsters ready for the party.
Use arrows to move, Z to select/pick up.
Tell the mad scientist you are ready to party when you've done all that you can."
v1.2 Edit: Fixed a bug that would crash the game if you tried to use arrow keys during a monster's response.
6 comments
A game about aspiration, guilt, and the scarcity of time.
Warnings: existential angst. Player may choose options that include animal abuse and gore.
Arrow keys: move
Z: Interact
X: Use Item
Enter: Menu
13 comments
To all of you users maintaining public Github repositories of either your games or supporting libraries for other PICO-8 users, I've just put up a repository containing PICO-8 badges.
This way you can add a Made With PICO-8 badge to your readme, alongside any other repo related badges you generally use!
Show your support for the tool and enjoy!
1 comment
This works:
s = [[ ... [ ... ]] x = 0 x += 1 |
But this no longer works:
s = [[ ... [[ ... ]] x = 0 x += 1 |
** syntax error line 3(tab 0) ** x += 1 ** syntax error near '+' |
It seems that in the search/replace phase of PICO-8 parsing, when "x += 1" gets replaced with "x = x + (1)", something erroneously considers that the second "[[" was opening a nested string, and does not perform any replacements until it finds a (nonexisting) matching "]]".
8 comments
