Vegz78 / McAirpos

MakeCode Arcade games in RetroPie, Recalbox 7/8 and Batocera, running natively as ELF executables on Raspberry Pi OS/Linux ARM with 1-2 gamepads

Home Page:https://Vegz78.github.io/McAirpos

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[Recalbox 8] Unable to lauch (Planned to include in future tests)

aaadddcom opened this issue · comments

Hi, I have a raspberry pi 3a+ with recalbox 8.1.1-electron and my games wont launch, when i click the game my recalbox shows up an error saying
"Looks like your game didnt lauch correctly!
This is probably caused by:
-incorrect rom
-obligator bios files not found/incorrect
-optional bios files not found/incorrect(but neccesary for this game)"
Sorry if i have bad english, its my second language.

Hi @aaadddcom,

Thanks for trying out McAirpos and sorry for my late reply!

Did you solve this issue eventually and have something to report back here?

I cannot interpret clearly from your inquiry whether you have problems launching MakeCode Arcade(MCA) games with McAirpos in particular on Recalbox, or whether you have a general problem with all your games and emulators in Recalbox? MCA requires no BIOS to run...

If regarding MCA and McAirpos, could you please provide here a copy of you /tmp/McAirpos.log file from right after you attempted to launch a game?

Update:
I see the same error as you when attempting to launch MCA games from the menu in Recalbox v9. There is a fundamental error just launching the .elf file here(Bus error). Did not know that this maybe has started occuring in v8 as well?

Could you please ssh into your Recalbox installation, copy a game.elf file to the folder /recalbox/share/bootvideos/makecode, make sure it is executable(chmod 755 game.elf and run it from this folder ./game.elf and see if you get the same error message?

Sorry,but I think Im not going to be able to try that since I had completly forgotten about the problem and also because it was really really hard to ssh into it, it kept giving an error on powershell on the pc and I did not find a way to fix it.Even if I found a way to fix it, I dont really use my raspberry pi now.

Reopening this issue just so that I remember it in future tests…