Got it at:
There’s 3 files, right?
CONFIG.BIN
INDEX.HTM
INFO_UF2.TXT
Though Current.UF2 file is optional, but some wired if it doesn’t appeared on your U-drive.
2 Likes
Hi AqeeAqee.
Yes, it’s those three files plus a .uf2 file which is the game itself.
2 Likes
Hi @hugov
I am afraid that I could not make bootloader with GameSlots for you, because there’s no any ex-Flash defination in config of your CONFIG.bin file, that means there’s no ex-Flash chip on your device, I guess.
Have the manufator ever claimed MicroPython/CircuitPython supported in manual or intro?
1 Like
it worked but i need more space for it to work because my games are basically about 800 or over
1 Like
Which console are you playing with, Meowbit? Can it run any game 800+ KB?
1 Like
if you modify the bootloader to use a SD card for storage and edit how much the games hold
has enough for that much
Games’s can’t be running in ex-Flash or SD, they should be loaded into main Flash before play.
it might work
Ah, the drive of Arcade console is a fake one, virtualized via MSC protocal (USB mass storage device class). And the total space is just a hardcoded size, can’t storage any thing else except Makecode apps. Total main-flash, in where games can run only, of Meowbit(STM32F4RE) is 512KB.
2 Likes
I also found another bug in GameSlots where random blocks aren’t actually random, any random blocks (random number to number, number chance) have the same seeds every time I open the game. Is it possible to randomise the seed every time you run a game?
This is by designed of Arcade, which is using pseudo random.
About pseudo random vs really random, is another big topic.
1 Like
I meant like, when you run the game in the default bootloader (Not GameSlots), every number feels random, like this:
(It’s like, the seed is different on every reset)
First reset:
37
68
47
06
12
69
Second reset:
16
78
26
48
96
57
Third reset:
18
57
28
78
55
18
23
But on GameSlots, it’s like:
(It’s like for every reset, the seed is the same, the “random” numbers feel repetitive)
First reset:
28
68
23
59
38
59
Second reset:
28
68
23
59
38
59
Third reset:
28
68
23
59
38
59
By reset I mean when you restart the game or boot up the game (Like resetting the device).
I made a Minecraft clone a while ago, the world generation for that uses Pseadu random. When I ran the code without GameSlots, every time I generate a new world after I reset, they were always different from before. But on GameSlots, now every world is the same (Or well, in a pattern).
I tried on my Meowbit with GameSlot v0.1 with something like “randint(0, 10)”. But can’t reproduce it. Either press reset button, nor slide power switch, every time random result are different after reset/power on.
Can you share a minimal repro project pls?
Sorry for the late reply. That’s weird, but for some reason my random values started being random again. I have no idea why it started working again.
May I also know how you made GameSlots? And if you forked a GitHub repository or something like that, may I also know the original or forked repository? I want to try make my own firmware for the MeowBit and try adding SD card support.
Sure, I just started from here.
Thanks! Just to be sure, would the build of the repository work fine on the MeowBit, without changing the code? Don’t want to risk my MeowBit getting bricked just because there was an error in the code, or that support isn’t yet enabled for the MeowBit.
Ah I figured it out, it’s because every time I wanted to restart the game, I reflashed the game via the GameSlots menu thus resetting the pseudo randomiser. But now I press the restart button two times and the random values are unique every time.
1 Like
Any bricked can be fixed by SWD, if you have one
1 Like
Thanks. May I also know how you built uf2-stm32f? I’ve tried running make on both Windows (MinGW) and Linux but make throws me an error saying that libopencm3/include/libopencm3/stm32/f4/nvic.h doesn’t exist. If necessary, you can check my repository.