I originally posted this in the Lakka forum, but after an update, I feel this needs to be posted here so the libretro team can see it.
Specs: Odroid XU4, Lakka and roms on a 128gb micro sd card, wireless Logitech Game Controller, Hdmi out
As the title states, FF8 randomly crashes while playing. The game runs flawlessly up until that point. It has happened four times so far on a run that’s 10 hours in. I’ve had to set the sram write interval to 5 minutes in an attempt to save what data I can if it happens. I can’t tell what triggers it. It can happen when entering a battle, during a battle, exiting a battle, or even in a town.
I’ve tried using both American bios, the scph5501 and scph1001. The problem happens with each. I doubt that the Odroid is overheating since it has a fan and the entire system doesn’t crash, only the core as it sends me back to the Lakka OS. It shouldn’t be the ROM, because the same ROM has played fine on the PC without ever crashing using mednafen. I am not running any unique or particular settings. I’ve checked and double checked to make sure there are no hotkey bindings I’m pressing to exit the core. I’ve disabled all of them. I’ve also reflashed Lakka to no avail. Is there a way to check some kind of logs after a core crashes? Or to check and make sure the bios is taking right?
Any and all advice is much obliged. Thanks in advance.
Update: Tried running FF8 on a different distro with Retropie. Still had the same issue. So it has to be something to do with Retroarch or emulator settings.
Final Update: After picking up an old used Lenovo small form factor business PC, my backup of FFVIII, along with the save for this playthrough, has run flawlessly on the x64 bit PC Retroarch installation for a few months. (hope I’m not jinxing it by posting this update haha). I still don’t know what the issue is with the Odroid XU4, Retroarch, and FFVIII. After trying multiple distros of Retroarch and backups of the game, I still couldn’t escape the random crash. I never did try it on a Raspberry Pi machine. Anyways, I’ve still found a solution, even though it isn’t as portable. Just posting this update for anyone else in the future who might run into the same issue. Cheers. Thank you all for the help!