angelobodetti Posted May 18, 2016 Author Share Posted May 18, 2016 OK so I use RetroArchfor MAME. Everything was running perfectly. Then I setup RocketLauncher and setup Retroarch with MAME in RocketLauncher. Now for some unknown reason RocketLauncher can luanch MAME games no problem through RA - But if I try to launch from RA directly or through LB it closes immediately. What the hell could be going on? So again, RocketLauncher can launch MAME games through RetroArch no problem, but If I try to launch a game from RetroArch directly or LaunchBox using RetroArch it fails. Any tips are appreciated. Quote Link to comment Share on other sites More sharing options...
angelobodetti Posted May 18, 2016 Author Share Posted May 18, 2016 Ok I figured it out - this is a little nutty... Essentially RocketLauncher changed the MAME settings in the retroarch-core-options.cfg file. The correct settings are: mame_read_config = "disabled" mame_write_config = "disabled" mame_saves = "game" mame_auto_save = "disabled" mame_mouse_enable = "disabled" mame_throttle = "disabled" mame_cheats_enable = "disabled" mame_alternate_renderer = "disabled" mame_softlists_enable = "enabled" mame_softlists_auto_media = "enabled" mame_media_type = "rom" mame_boot_to_bios = "disabled" mame_boot_to_osd = "disabled" mame_boot_from_cli = "disabled" For some reason RocketLauncher changes mame_read_config and mame_boot_from_cdi to enabled. No clue what I will do other than I guess have a separate RA setup just for MAME? I also use Hyperspin which is why I have rocketlauncher set up. Quote Link to comment Share on other sites More sharing options...
SentaiBrad Posted May 18, 2016 Share Posted May 18, 2016 Yea RocketLauncher likes doing what ever the hell it feels like. xD Part of the reason I try to say to just not use it, but... Quote Link to comment Share on other sites More sharing options...
fromlostdays Posted May 18, 2016 Share Posted May 18, 2016 I understand why RL would change the boot from CLI to enabled. It uses a bunch of CLI options. What I don't understand is: A: Why that would break you're Launchbox launching? (Unless you're not using RL in Launchbox and using RA as your emulator) I use the exact same setup you do, CLI enabled, Launchbox to RL to RA, and I've never had any problems. B: RocketLauncher should not be changing the read config line at all. It doesn't on mine. I'm wondering if that's what broke the launch? C: There is no reason that anything would launch in RL and NOT in LB or HyperSpin (Using RL) except that they aren't communicating correctly to each other. Are you sure you're using RL through Launchbox correctly? I can pretty much assure you something else is afoot, as again, I have the same exact set up with no problems. If you're sure that launching a game through RL is changing the read config line, that's got to be a bug and should probably be reported on the RL forum, but I'm not convinced it is as I'm up to date on LB, RL, and RA and not having this problem. Quote Link to comment Share on other sites More sharing options...
angelobodetti Posted May 18, 2016 Author Share Posted May 18, 2016 I have RA as the emulator in LB, not RL. I don't know how to make RocketLauncher work in LaunchBox. So basically RL was changing the RA cfg file and RL was still able to launch games no problem but RA and LB could not. Quote Link to comment Share on other sites More sharing options...
fromlostdays Posted May 18, 2016 Share Posted May 18, 2016 Still not able to replicate the error. Changed a few mame games over to RA and launched fine. I do suspect this may have something to do with RocketLauncher launching a different config file. Launchbox defaults to the standard RA config, but it's definitely a quandary. 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.