TankZilla is an asymmetric sci-fi wargame, where you have to defend your outpost against the AI controlled megatank "TankZilla".
The red AI and blue player take turns controlling their units in a few phases; first there is a move phase followed by an attack phase, and some units get a secondary move phase. After this the other player goes.
TankZilla (the red megatank) wins if it destroys your outpost and then escapes southward. The blue defence force that you control can win by destroying the TankZilla unit.
Your (blue) defense units:
HOVR - Hover tank. Movement 4. Attack 3. Range 2. Defense 2. Gets a secondary movement of 3.
HVY - Heavy tank. Movement 3. Attack 4. Range 2. Defense 2.



A carefully crafted Pico-8 demake of Rareware's ZX Spectrum classic, lost in space and with only your blaster to protect yourself, you must collect all pieces of your spaceship, fuel it up and escape as soon as possible
Credits/Special thanks:
-Main game and most music/graphics by myself, Coffee Bat
-In-game song 3 by the outstanding Blameitontherobot
-Original game by the amazing Ultimate/Rare
-A couple of ideas and the main inspiration to make this game thanks to Asobitech and their amazing Super Jetpak DX






I participated in the 5th Brackeys Game Jam, and here's the final version! Tutorial ingame. Here's the itch version!
I'm very new to linux and raspberry PIs, but I saw that pico 8 had a raspberry pi option so I thought it'd be fun to try it out. All the instructions I saw online looked pretty plug and play so I extracted the folder to the home directory, but when I double clicked the pico8 file a window would briefly pop up then disappear, and upon trying to run it from the command line I got the error message "segmentation fault". Are there any settings I should change? I am using a Raspberry pi 4 4gb model.
Thank you for any help you have.

TL;DR: Do you like your pixels razor-sharp? Do you like PICO-8? Then get this handheld.
Looks
This is the new Game & Watch

This is the Game Boy Micro

And this is the new Waveshare GPM280.

Looks good, don't you think?
And it runs PICO-8 perfectly. The screen, oh, yes the screen. In a word: razor-sharp pixels.
Screen
128x128 is such an oddball resolution. Practically no screens in use can scale that resolution easily, the only exceptions are 1024x768 screens and the iPhone 4's 960x640 retina screen. The solution to this conundrum? A smartphone-like high DPI screen plus an intelligent scaling algorithm. An approach taken by the upcoming Analogue Pocket for example. But that won't run PICO-8.
Take a look. On the bottom is the pixel-perfect iPhone 4 screen (5x integer scale), on the top is the GPM280 screen. Also notice the 45° diagonals, on the RG280V they don't look right because of uneven scaling. Here they are perfect. (Right-click on this picture to enlarge.)








I'm making a collection of songs called Noclip, which anyone here in the community can use with credit, a bit like ToyBox. Here are the tracks I've made so far, enchanced with 0.2.2 music effects!
Track One: Seen. Not sure what you would do with this one, but surprise me!
Track Two: SysNull. Spacey vibes. An expanded version of a song I made a bit of time ago.
If you use these, comment on the post so that I can see what you've done with them! I'm excited to see the uses of these songs.
I tried making a 60 FPS game and noticed a weird behavior of my PICO-8: it's refresh rate stayed at 29-30 FPS even though the game was supposed to be running on 60 FPS according to stat(7) and CTRL-P widget. Movement looked choppy and the builtin FPS counter (stat(9) and show_fps config) shown 29-30 FPS. My monitor is capable of 60hz refresh rate and my CPU and GPU usage wasn't even remotely close to 100% (or even 8%, which is half of a processor core and can be a limit for single-threaded apps). It works properly on the web version.
Pls halp!
P.S.: It works just fine on Linux on the same machine with the same cart and default config.
Relevant config:
show_fps 1 foreground_sleep_ms 5 background_sleep_ms 10 host_framerate_control 0 |
Some stats and readings:
stat(7) and CTRL-P: 60/60 stat(9) and show_fps: ~30 stat(1) and CTRL-P: ~0.3 CPU usage: ~7% GPU usage (3D): ~30% |
Soft/hardware:
PICO-8 v.0.2.2 [ [size=16][color=#ffaabb] [ Continue Reading.. ] [/color][/size] ](/bbs/?pid=87885#p) |



I've seen a significant performance difference between the latest v0.2.2 and v0.2.1b.
For this particular cart, it runs significantly slower on the latest version when measured with a stop watch, but when using the stat(1), the system claims the opposite--i.e. that it's faster. (These are both being run from the .exe on Windows.)
Version stat(1) Stopwatch Timed v0.2.1b 285 30 seconds v0.2.2 219 8 minutes, 14 seconds |
I've included the cart for reference.
-ElectricGryphon



