I won’t be completing the APU Lakka project after all as I think I’ll be better off selling the parts now that they’re still worth a damn. Thanks for the support though, gouchi!
However, I managed to grab an ASRock Q1900DC-ITX motherboard on sale with, as the name suggests, an onboard Intel Celeron J1900 CPU. Originally I had a server project planned but I just might look into getting Lakka running on it. The J1900 is clocked at 2GHz which, I assume, should be able to handle everything up to and including PS1 emulation (correct me if I’m wrong, though).
–
Couple of questions in the meantime – I’ve still got Lakka set up and running on the R7 250 gpu:
I haven’t been able to get Saturn & Dreamcast working.
- BIOS files were put in the system folder: saturn_bios.bin & dc_flash.bin (region free).
- Roms transferred succesfully, although they don’t show up after scanning.
- Dreamcast roms are mostly .cdi, not compatible with Lakka perhaps?
Am I doing something wrong, did I miss something?
Also, next to the usual .cue and .bin file(s), some PS1 roms have .ape files. I’ve decompressed them to .wav with Monkey’s Audio. But then what am I to do? I’m unable to mount such images on my desktop to test with ePSXe, and they too fail to show up after a Lakka scan.
A quick look at the .cue file reveals that the now converted .wav files are supposed to be .bin files. So I edited the .cue file and changed each .bin to .wav inside it. I then am able to mount the image but only as a redbook audio disc. Starting the mounted image with ePSXe shows error notification ‘ePSXe (error) Recompile block too large (28573) (28572)’. I realise this has got nothing to do with Lakka but I do have to test out these roms before moving them over to Lakka.
Finally, every USA (Rev A & B) Ocarina of Time rom I’ve tested results in Lakka restarting instantly after defeating Gohma, the first boss of the game. The Eur (En Fr De) rom just freezes, I can close the game normally using Lakka. [SIZE=2]All of this happens exactly after Gohma disintegrates. Has anybody else encountered this issue?[/SIZE]