... Which reminds me that I ported the tutorial game.
@charlie.daft.games
Writes a lot of code, sometimes it even works. May or may not actually exist. (insert useful info here) ... Writing is not one of my skills. ๐ bridged from โ https://fosstodon.org/@Daft_Freak, follow @ap.brid.gy to interact
... Which reminds me that I ported the tutorial game.
Launcher with "Susi Snake" selected. This runs through 32blit-lua, but you can't see that due to the custom metadata.
Of course, the thing the "handler" system was originally designed for (lua) also works.
32blit "beta unit" in a 3D-printed case running the 32blit launcher above my handheld running the "catapult" launcher. Both have a copy of "Tetris DX" selected, showing that it can be launched with the "DaftBoy32" emulator.
Adding some of the last big missing features...
(File handlers)
Lipo battery seen through the back of a transparent case touching the boot/reset buttons on an RP2350 stamp XL. The black wire is also a little short.
One of these days, I'll find a battery that fits perfectly... Until then:
Suspiciously automated-looking PR managing to mess up all the line endings ๐ค
Because of some missing error handling, if my "loader" couldn't find anywhere to install a game, it erased itself and crashed.
I uh... guess that's one way to prevent it happening again...
Hmm, my system really doesn't like it when I'm getting low FPS in games...
(I just realised it happens constantly if I set a 30FPS limit)
๐ค I have a plan for the V3 (?) of the "display" board in my console-thingy, now I just need to do it.
(and come up with some excuse to justify the cost)
If you look closely, you can see that this one is called "catapult". (The previous one was "slingshot")
Also, while I spent ages on the animations again, this one does have most of the functionality working.
Went to fix some stuff, but ended up writing a new launcher.
(Okay, it's based on an older one I didn't finish)
This is such a strange place. Post a picture of a stopped clock and suddenly my screen is full of notifications! ๐
Badger 2350 running the clock app and displaying 16:03... At about 18:05.
Well, at least I know what time the battery ran out.
Makes sure name field is at least 7 chars so my name fits.
Enters name as "daft" anyway. ๐
@gadgetoid.com @arturo182.bsky.social I've had that wired up for ages, but still haven't looked into actually using the I2C. Hmm.
๐ค The temperature difference between these two...
Two boards in a case with a speaker, battery, qwst pad and debug probe connected and placed randomly nearby.
Not making a mess here, nope.
Handheld console running something suspiciously tetris-like.
Well, this was a mistake ๐
Super Square Bros on Tufty2350.
Pico3D on Tufty2350.
Running the PicoSystem classics ๐
(I forgot to disable benchmark mode in Pico3D)
Also I finally finished off parts of the joystick calibration tool.... Like being able to install it...
(Can also see the "thinner part of the case instead of a hole for the LED because it's too bright" feature)
Handheld console thing with purple sides and grey in the middle running Tetris in DaftBoy.
I reinstalled the launcher after having flashed a lot of other things, some of them using most of the flash.
Somehow it started up a copy of DaftBoy that was... hiding in a gap somewhere? ๐
After much work I can now have TWO up buttons on my Tufty ๐
Though everything was broken, but I was just choosing the wrong build option.
(This is my own fault for having "ThingA-ThingB" and "ThingB-ThingA" options that don't do the same thing apparently)
<nav class="time-machine">
Doing some web stuff... Made a little widget to jump between years in a big list, so:
Oh no, I got stuck spending a lot of time to make something slightly faster again. ๐
I am obviously being extremely productive right now.
๐ค Also vertical stripes when accessing the SD card.
In other news, after some hackery the ESP32-P4 build is actually faster than the (overclocked) RP2350 one.
"Mostly fixed" because it still glitches out when there's too much going on. A good example is running a memory benchmark...
Mostly fixed by throwing RAM at the problem...
More specifically I now have a big lookup table to do two 16-colour pixels at once.
I got VGA output working on the ESP32-P4 but it seems the drawing code is not fast enough... Hmm.
Probably enough changes to need to order a new revision, but that would require soldering another 120 pins.
(Probably desoldering the old ones to reuse as well)