I.K.E.M.E.N GO on Raspberry Pi 4 [Now with an Install Guide!]

SuperFromND

@thesnackist That's probably the cause then; I admittedly have only tested this on Buster-based images, so it's possible that some of the packages required don't exist on Stretch's package pool.

After digging through the 50MB behemoth that is Raspbian Stretch's package list in text format, it seems like all the packages themselves are present... but the version of Golang itself is only version 1.7, which is pretty darn old. I have no idea what the oldest version of Golang that can still compile IKEMEN GO is, but if Gacel's advice from a few dozen posts ago was any indication, having a version this old might be a problem. (For the record, Buster uses Golang 1.11; still pretty old, but it's known to at least be "good enough" for compiling IKEMEN GO.)

TheSnackist

@superfromnd was hoping to avoid having to make a fresh distro (sigh) but it maybe be unavoidable at this point

I just hate having to reset up my reset/shutdown button script and whatever the hell I had to do to get pico-8 running

Troopaking

@superfromnd hello again so I just tested your newest script on pi 4 fresh retropie os. Worked good.
Gonna experiment in converting a mugen over.
How would you add a anither ikemen for example ikemen go then mk vs capcom .
Also why use ports instead of a custom "system"? Just wondering .

Troopaking

@superfromnd after letting ikemen run and walk away came back to errors cant exit . Had to reboot.
Error traceback
A few times mainly
External/script/mainlua/

SuperFromND

@troopaking I mainly set it as a port for the sake of simplicity when installing stuff. It should be entirely possible to set it up in a way to allow for multiple fullgames to be installed (IKEMEN lets you pass a motif, which can contain a character and stage list among other things, using this command:)

./Ikemen_GO -r path/to/motif/system.def

@thesnackist said in I.K.E.M.E.N GO on Raspberry Pi 4:

I just hate having to reset up my reset/shutdown button script and whatever the hell I had to do to get pico-8 running

Aye, indeed it's a bit of a pain to upgrade if you've got a fairly-customized setup. I've had to re-install my custom scriptmodules and ports multiple times, so I understand the pain.

@troopaking said in I.K.E.M.E.N GO on Raspberry Pi 4:

Error traceback
A few times mainly
External/script/mainlua/

I'm gonna need a bit more info than that (external/script/main.lua is just the main logic for the engine, and doesn't really tell anything about what exactly went wrong. I was getting crashes briefly during the demo if an opponent managed to K.O. someone, but apparently that's a known bug and is planned to be fixed soon.)

Troopaking

@superfromnd oh the demo error is probably what happened .
It was running demo .

SuperFromND

So I didn't really bring it up before, but I was having some odd issues with inputs, but only with my specific controller (a Rock Candy Xbox 360 pad). Turns out that wasn't an IKEMEN bug at all, but rather a driver issue. Simply updating xpad (the default driver in RetroPie for controllers) allows you to fully use and remap the controller correctly!

(Oh, quick side note; don't try to compile IKEMEN GO right this moment at the time of this post; some commits that shouldn't have been pushed yet were pushed, and as a result the game crashes on startup due to the game trying to read a nonexistent parameter in save/config.json; this should be fixed shortly after this post's publication!)

SuperFromND

@superfromnd said in I.K.E.M.E.N GO on Raspberry Pi 4:

this should be fixed shortly after this post's publication!

Okay so uh, clearly it hasn't haha. At the very least, I figured out the cause and a temporary, if extremely clunky, workaround: pop open the file /home/pi/RetroPie/ports/ikemen-go/external/script/options.lua and find this line:

if itemname == 'gamespeed' then return config.GameSpeed .. '%' end

and change it to this:

if itemname == 'gamespeed' then return '100%' end

Note that, as you can probably see, doing this will break the "Game Speed" option in the options menu.

SuperFromND

UPDATE: Glad to report this is no longer the case! The game now works when compiling from source once again. :)

@superfromnd said in [I.K.E.M.E.N GO on Raspberry Pi 4]

(Oh, quick side note; don't try to compile IKEMEN GO right this moment at the time of this post; some commits that shouldn't have been pushed yet were pushed, and as a result the game crashes on startup due to the game trying to read a nonexistent parameter in save/config.json; this should be fixed shortly after this post's publication!)

MrRussellgro

Hey, so I want to get this for my RetroPie console, but how do I get it to work? Do I just download it from the Ports section from the online menu?

SuperFromND

@mrrussellgro said in I.K.E.M.E.N GO on Raspberry Pi 4:

Hey, so I want to get this for my RetroPie console, but how do I get it to work? Do I just download it from the Ports section from the online menu?

It's not currently included in RetroPie, so you'll have to manually add it to the Ports section in RetroPie's setup menu in order to install it. Here's a guide on how to do that:

What You'll Need

Some form of FTP client. I use and highly recommend WinSCP, though I've also heard Cyberduck is pretty good.
This .sh file. If you see the script's text but don't get prompted for a download (which is the case in Chrome), just press Ctrl + S to save it as a file.

Installation

If you haven't already done so, update RetroPie-Setup to the latest version and enable SSH.
Using your FTP client, connect to your Raspberry Pi.
Navigate to the directory /home/pi/RetroPie-Setup/scriptmodules/ports. In WinSCP, you can simply copy-and-paste the above text into the address bar and it will take you straight to it. You should see a bunch of .sh files.
Drag and drop ikemen-go.sh into this directory.
Once that's done being transferred, now you can start RetroPie-Setup and navigate over to Ports and, if you did this correctly, IKEMEN GO should be installable from there.

Installation should take somewhere between 15 to 30 minutes on a fresh image.
Usage notes / documentation pertaining to IKEMEN GO are currently available here.

MrRussellgro

@superfromnd So I followed your steps, though I used a USB transfer to my Pi, but it won't launch the game. Anything I'm doing wrong?

SuperFromND

@mrrussellgro A few things might have gone wrong!

Are you running on a Pi 4?
Are you using a Buster-based version of RetroPie (4.6 or later)?
Check the file /dev/shm/runcommand.log for any errors or issues.

MrRussellgro

@superfromnd said in I.K.E.M.E.N GO on Raspberry Pi 4:

@mrrussellgro A few things might have gone wrong!

Are you running on a Pi 4?

Are you using a Buster-based version of RetroPie (4.6 or later)?

Check the file /dev/shm/runcommand.log for any errors or issues.

I'm on Raspberry Pi 4.
I believe I have version 4.7.12 of RetroPie. I might have to look again.

SuperFromND

@mrrussellgro Hm, is there anything in /dev/shm/runcommand.log? What about /opt/retropie/ports/ikemen-go/Ikemen.log?

MrRussellgro

@superfromnd So how can I look into those?

SuperFromND

@mrrussellgro Assuming SSH is enabled, you should be able to view them just by using an FTP client and navigating to /dev/shm; the runcommand.log file should be there after attempting to run IKEMEN GO from EmulationStation.

Since you mentioned using USB transfer, did you by chance place ikemen-go.sh directly into a ROM folder instead of your RetroPie-Setup scriptmodules folder by mistake? I don't believe that USB transfer is able to identify and transfer a scriptmodule into the RetroPie-Setup menu (though I could be wrong).

TheSnackist

@superfromnd I take it there is no way this will work on a RPi 3b? with the price of Raspberry Pis I guess I have no excuse not to get a Pi 4

SuperFromND

@thesnackist I haven't tested on a Pi 3, admittedly! Though I wouldn't be surprised if something is missing on the Pi 3 that was added in the Pi 4's hardware when it switched to the A72 CPU.

TheSnackist

@superfromnd gonna give it another go tonight, maybe I will have better luck (last time it was having trouble reaching GitHub for some reason...)