Uzebox Forums

Nice! Might start to work on that V6 Bootloader idea, I didn't begin any of it yet. Quite badly drained by work, so nothing too hasty would likely happen - but it is an interesting problem how to get a nice, well customizable bootloader.

Similar script could be written, yes. One of my main plans still with this game is to do some further work on its scripts, likely adding a Python packrom so it could be built completely without the need to compile the Uzebox repo (to get a native packrom out of it). Unfortunately what needed tools a...

Hi Clymax, nice to see some tinkering going on! Was surprised to find that site and that it even covers Uzebox games!

Nice! ... Correction: Those of us not lucky enough to own a fast enough old SDSC card! (Cause I have some, but neither works )

You aren't supposed to plug / unplug controllers while the system is powered, they aren't mechanically designed for that. USB and SD Cards are designed with hot-plugging in mind with having the power and ground pins making contact first (those contacts are longer, so making connection first / breaki...

Game is now reasonably complete... Uh... I mean I really haven't got any ROM left... Anyway, Version 1.0 is up, Wiki created!

A bit baffling to me as it looks like it reports a CRC error, which at that stage it shouldn't do. You might be able to hack yourself around this problem by recompiling the emulator with Line 442 in cu_spisd.c uncommented (it is an "sd_state.r1 |= R1_CRC;"), no idea why you get it with tha...

Thank you! The reset on frame is an interesting one indeed - it does two things. One is more RAM by eliminating the need for retaining the stack while the video frame is ran. The other is consistent timing, which of course took some careful design. The display generation is purposely made so that it...

Hi! Not sure there as I didn't use those libraries. Just to keep in mind if you are trying that, the emulators don't have complete filesystem support. CUzebox is able to catch writes to a file as long as it isn't resized, but nothing more. Uzem is read only as far as I see. So you will need to use r...

Something occurred to me which could explain the wildly varying outcomes. Might we have some uninitialized memory somewhere? (any variable, data structure etc) Possibly something which might result in some part of an algorithm used here going through a loop unexpected amount of times? (There shouldn...