Soop Posted February 13, 2022 Share Posted February 13, 2022 So I think this is different to the other PC Engine issue, OP didn't say how he fixed it in the end. My issie is that the only emulator cores that show up in Launchbox are Mednafen ones, and the only cores I have available in Retroarch are Beetle. I don't believe they're the same thing with different names because nothing I've tried will let me launch games. How can I select the Beetle cores within Launchbox? Quote Link to comment Share on other sites More sharing options...
neil9000 Posted February 13, 2022 Share Posted February 13, 2022 2 minutes ago, Soop said: I don't believe they're the same thing with different names because nothing I've tried will let me launch games. They are the same, they are only called Beetle in the UI, so when specifying the core in Launchbox choose the mednafene one. Quote Link to comment Share on other sites More sharing options...
Soop Posted February 13, 2022 Author Share Posted February 13, 2022 Ok I realised the problem; Retroarch was already open in the background. If you try and launch anything while Retroarch is already open, it will just return you to the same Retroarch view you had open. For me this was the same screen it opens to when you select a core so it looked like it wasn't finding the core. All working now. Thanks for the quick reply Quote Link to comment Share on other sites More sharing options...
neil9000 Posted February 13, 2022 Share Posted February 13, 2022 4 minutes ago, Soop said: Ok I realised the problem; Retroarch was already open in the background. If you try and launch anything while Retroarch is already open, it will just return you to the same Retroarch view you had open. For me this was the same screen it opens to when you select a core so it looked like it wasn't finding the core. All working now. Thanks for the quick reply Yeah, we send a command line argument to the emulator telling it which core and rom to load, we cant do that if the emulator is already open. Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted February 13, 2022 Share Posted February 13, 2022 2 hours ago, Soop said: Ok I realised the problem; Retroarch was already open in the background. If you try and launch anything while Retroarch is already open, it will just return you to the same Retroarch view you had open. For me this was the same screen it opens to when you select a core so it looked like it wasn't finding the core. All working now. Thanks for the quick reply Yeah, this is a very unfortunate Android issue. Sadly there's no real way around it that we know of. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.