![]() 6 with no difference - still black screen of unhappiness. Did a full clean up and reinstall of version. Some roms i replaced (cps1-2), some i didn't, not sure if it made a difference.ģ. I used the RA version from RA website, not app store.Ģ. Thanks for any further input on this issue. Regardless, the mame go black screen has to be a configuration somewhere that isn't happy. I didn't want to use mame4droid because of the bezel setup, but i guess i could, and change the configs in mame bezel project files to point to the RA overlays/ArcadeBezels folder, this would avoid having 2 large ArcadeBezel folders. Pretty much all other cores work as they should, and look great with the bezels (once your roms are named correctly), but all the mame cores go black screen, and so do fbalpha 2012's for the cps1-3, whether using the individual cores or the generic fbalpha with cps 1-3. Meaning, if there is already a core folder in RA/config, Will RA generate the opt file whenever it usually does? opt files in the core folders in config (bezel cfg that i copied over), is this good or bad? This would be before ever installing or launching a core in RA. I've been copying Bezel Project files into RA's config, overlays, wallpapers after RA is installed on the device - and RA has to run once to build itself in the main directory. I really do like how the playlists break down by required core. I just fnished setting up an old Shield Tegra Portable using RA only (launchbox was just too heavy for this old unit), using all the same roms and overlays etc., and all Mame cores work surprisingly well. With the initial folder/file setup being a bit different on Android for RA, does LB do any caching of core info/config files on it's own accord? ie: do i need to make any extra folders in RA to accommodate what LB is expecting? ![]() I've also uninstalled, cleaned, and reinstalled cores. Cleared more than the caches, reinstalled several times Retroarch or Retroarch Plus or stanalone version from RA website, version stable for detected device, delete old folders etc. I'm having this same issue with LB for Android on a P30 pro. What romset version are you using? The mame core in retroarch is the current up to date core, so if your roms are not the current set then you are going to run into issues running games. No Android data cache to clear ( Windows) and no hidden mac files I could find. I'm really growing discouraged after 3+ evenings of troubleshooting. I've also disabled " Enable Game Startup Screen" to see if that helped but no luck. I've read in some threads about changing the display driver ( which I've attempted) though not sure why that'd be relevant as it works when manually launching from RetroArch. I have to ALT+TAB to exit and hard close RetroArch ( running in the background) as my usual Exit button doesn't work. If I attempt to get Launchbox to use RetroArch as the emulator, specifying that same core (mame_librertro) as the associated platform for 'Arcade', it launches RetroArch but then only shows a black screen. If I manually launch RetroArch and load up my MAME core, I can launch a game without any issue. The only emulator installed is RetroArch. ![]() Copied over my game collection from a former install. So just adding yet another bit of data to the thread, although I'm still stuck in limbo Carr.įresh install of LaunchBox 12.5. Thanks in advance and let me know if you need me to provide anything else! Seems to be a an issue with the script or something communicating between LaunchBox and RetroArch. I can also confirm that I can run RetroArch and load all those systems/games through there just fine as well. This doesn't seem to be an issue with my standalone emulators (Dolphin, DraStic, Mupen64 FZ, PPSSPP, ReDream, Yaba Sanshiro) as those all launch as intended. I've tried this with a side loaded 32-bit RetroArch as well as both versions on the Play Store but just ain't having any luck with it. I have LaunchBox pointing to the sideloaded 64-bit RetroArch and then also pointed it to the appropriate core (I've also tried with multiple cores). I'm pretty fluent in tinkering with RetorArch so I'm positive the core configs are correct. I can see that RetroArch launches but I have to force close it cause it doesn't go passed the black screen. I have RetroArch 64-bit side loaded onto my Nvidia Shield TV and with the latest versions of LaunchBox for Android (0.41 & 0.42) I can't seem to launch any systems through RetroArch. I'm hoping you can help me with a weird issue I'm having. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |