xokia

Trying to learn the system too. So learning the file structure and options is preferable to me Ok so you dont need to update anything with the path to the opt file retroarch will just pick it up if it exists? Tried both methods neither seemed to work. But learned something new about the opt and cfg files thank you. I did find the issue. Not sure what I missed the first time through. Maybe I didnt have the bios correct first time through. Even though it says a bios is not needed it appears one is needed. The -cart is required both in MAME(0.274) directly and retroarch . Think I read somewhere it was optional for this system. with -cart and not changing anything else everything works. -f "supracan -cart \"%romfile%\""

I don't have a (\RetroArch\config\MAME\supracan.opt) All the files in \RetroArch\config\MAME\ are .cfg files Can I just create a supracan.cfg file and then add mame_softlists_enable = "disabled" to it?

Yea you are probably right. I'm not really even a gamer. I mainly do this to learn something new and for my nieces and nephews. They are able to log into my server from a firestick and play whatever they want. I was able to get the retroarch console logger working. Looks like it detects the system correctly [libretro DEBUG] Path extraction result: Game path = "Z:\Arcade\Funtech Super Acan\Roms" [libretro DEBUG] Path extraction result: Parent path = "Z:\Arcade\Funtech Super Acan" [libretro INFO] Starting game from command line: "supracan "Z:\Arcade\Funtech Super Acan\Roms\Boom Zoo (Taiwan).7z"" [libretro DEBUG] Searching for driver: supracan [libretro DEBUG] System type: CONSOLE [libretro INFO] Game name: supracan [libretro INFO] Game description: Super A'Can Then detects the bios correctly [libretro DEBUG] Z:\Arcade\emulators\Launchbox_RetroArch\RetroArch-Win64\system\mame\ [libretro DEBUG] -rompath [libretro DEBUG] Z:\Arcade\Funtech Super Acan\Roms;Z:\Arcade\emulators\Launchbox_RetroArch\RetroArch-Win64\system\mame\bios;Z:\Arcade\emulators\Launchbox_RetroArch\RetroArch-Win64\system\mame\roms [libretro DEBUG] supracan [libretro DEBUG] Z:\Arcade\Funtech Super Acan\Roms\Boom Zoo (Taiwan).7z But then fails to match he name? Not sure what to make of that error message [libretro ERROR] "\Arcade\Funtech Super Acan\Roms\Boom Zoo (Taiwan).7z" approximately matches the following supported software items (best match first): [libretro ERROR] * Software list "supracan" (Funtech Super A'Can cartridges) matches: [libretro ERROR] slghtsag Super Light Saga - Dragon Force ~ Chao Ji Guang Ming Zhan Shi [libretro ERROR] monopoly Monopoly: Adventure in Africa ~ Fei Zhou Tan Xian Da Fu Weng [libretro ERROR] sangofgt Sango Fighter ~ Wu Jiang Zheng Ba - San Guo Zhi [libretro ERROR] magipool Magical Pool [libretro ERROR] speedyd Speedy Dragon ~ Yin Su Fei Long [libretro ERROR] staiwbbl Super Taiwanese Baseball League ~ Chao Ji Zhong Hua Zhi Bang Lian Meng [libretro ERROR] formduel Formosa Duel [libretro ERROR] sonevil The Son of Evil ~ Xie E Zhi Zi [libretro ERROR] jttlaugh Journey to the Laugh ~ Xi You Ji [libretro ERROR] boomzoo Boom Zoo ~ Bao Bao Dong Wu Yuan [libretro ERROR] gamblord Gambling Lord [libretro ERROR] [libretro ERROR] [libretro DEBUG] retro_load_game osd_sleep [libretro DEBUG] retro_load_game osd_sleep done [ERROR] [Content]: Failed to load content [INFO] [Core]: Content ran for a total of: 00 hours, 00 minutes, 00 seconds. [INFO] [Core]: Unloading core.. And no to MAME directly. I get a similar message.

Yea I initially tried that. no luck

This one seems like it should be easy after getting mame to work. But For some reason I cant get this one to work. My understanding is that this one should not need a bios. But then I found elsewhere where folks say create an empty file called internal_68k.bin and zip it into supracan.zip. I've tried both cant get it to load the game. What am I missing?

got it all working now. Had the wrong bios and found all my type-O's Thank you !

I did just get bally astrocade to work. The problem was something in my "plugin" directory was causing it to fail. I dont know what. But I created an empty plugin directory and now bally works! What is wrong with my other entries that you noticed? I am trying to get those working now. Missing " I think let me see if that fixes it *update* Trying for entex now. Can't seem to get that one to work. I renamed the bios to advision.zip Do I need to rename the bios file inside the zip folder?

I cant seem to get this to work. I created a seperated "emulator" for mame. within my mame/rom directory I have the bios within my mame.ini I have What am I doing wrong or missing?

in retroarch.cfg this is the option that was preventing this from working. This was false in mine game_specific_options = "true" I appreciate you sharing your known good config. Everything works as expected now. Now on to mame A lot of these emulators are pretty simple to get working but ...........some of these are a real PITA specially when they dont do what's expected.

Here is what it looks like when I try and import a rom with 13.19. Same exact import with 13.18

I downloaded new version of 1.19.1 and 1.20. I'll try installing those later and see if it works.

*update" so same issue the core does not change. I am wondering if its my version of retroarch? Maybe they changed something I am on v1.20.0. Thank you for trying to assist and providing your config. IDK what the issue is at this point I think I have an older version of retroarch on a drive somewhere I could try.

I will try this later today when I get back home. Thank You!

Folks please help I have been at this for 4 days now and ZERO combinations work as expected. I am at wits end I need to change the core model based on which system is running. This is under core options for the cap32 core It refuses to take my custom config file and just uses the defaults I need cap32_model="6128+(experimental)" if Amstrad GX4000 is selected and cap32_model="6128" if Amstrad CPC is select I copied retroarch.cfg and made retroarch_CPC.cfg and retroarch_GX4000.cfg in these 2 files I changed 2 parameters core_options_path = ":\config\cap32\cap32_CPC.cfg" global_core_options = "true" and core_options_path = ":\config\cap32\cap32_GX4000.cfg" global_core_options = "true" I have tried with global_core_options = "true" or flase. Doesnt make a difference just changes where the default CFG gets saved. I read somewhere that if that wasnt set to true it wasn't picking up passed in custom configs. Wether that is correct or not I do not know. I have tried just about everthing and failed to this point. within cap32_GX4000.cfg I have cap32_model = "6128+ (experimental)" cap32_CPC.cfg I have cap32_model = "6128)" Nothing works the way it seems like it should, I tried turning on the retroarch debugger and that tool is utterly worthless. It states it loades the core and game and exits the core. Doesnt contain anything about what it loaded into the core.

Any progress? 13.18 is less broke then 13.19. Themes work fine under 13.18. Maybe its not correct to say 13.18 is broke. 13.18 worked 100% until upgrading to 13.19. After upgrading then reverting back to 13.18 MAME import is broke. Let me know if there is anything I can do to assist in debug.

upgrading to 13.19 fix the MAME set importer but import Rom is still broke. I Can not import ANY roms. It inserts that "file:" into my path and everything breaks. Also themes dont work under BigBox

Tried that did not fix anything

Doing all that switching and rolling back now broke my MAME set importation. Hoping this can be resolved. Object reference not set to an instance of an object. App: LaunchBox Version: 13.18 Theme: Default Type: System.NullReferenceException Site: Void PrintInvalidIterator() Source: LaunchBox at Unbroken.LaunchBox.Windows.Desktop.ViewModels.MameFullSetWizardRomLocationViewModel.PrintInvalidIterator() at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.ChangeAwareVisitor(Object ) at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.PopSessionProcessor() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() Recent Log: 8:23:08 PM Exception

Just sent you both working 13.18 and broken 13.19 so you can diff Only thing I can think of that was done different is 13.18 install file is sitting on the network drive 13.19 install file is sitting on the local drive. Both were pointed to the Launchbox directory on the network drive to install into.

OK this is all really confusing so if I set global_core_options = "false" Then it should take the files in presidence? Basically load up all 4 of those cfg files and apply the overrides based on the order of precedence? My understanding of the precedence is retroarch.cfg->core.cfg->directory.cfg->game.config The game.cfg being the highest precedence. I can't seem to get it to do what I want. I have a single core that needs a different config based on what game platform its using. So I was trying to set the directory.cfg file This is for Amstrad CPC & Amstrad GX4000 So I have a core.opt but not a game.opt https://docs.libretro.com/guides/overrides/ Core options¶ name-of-game.opt If not found load retroarch-core-options.cfg Its starting "core" options and then proceeds to give you "game" options type-o maybe? IDK but these instructions are terrible. Its stating info about .opt files and then proceeds to describe .cfg files lets just gloss over the entire subject . I am going to proceed assuming that was meant to say "core.opt" Moving on: So I create a cap32.cfg (core) I put the following cap32_advanced_green_phosphor = "15" cap32_autorun = "enabled" cap32_combokey = "select" cap32_db_mapkeys = "enabled" cap32_floppy_sound = "enabled" cap32_gfx_colors = "16bit" cap32_keyboard_transparency = "disabled" cap32_lang_layout = "english" cap32_lightgun_input = "disabled" cap32_lightgun_show = "disabled" cap32_model = "6128" cap32_ram = "128" cap32_retrojoy0 = "auto" cap32_retrojoy1 = "auto" cap32_scr_crop = "disabled" cap32_scr_intensity = "8" cap32_scr_tube = "color" cap32_statusbar = "onloading" Now I create a directory.cfg.......... Now I assume they mean the "game directory".cfg So I created Amstrad GX4000.cfg and a Amstrad CPC.cfg I have roms under both these directories. Arcade\Amstrad GX4000\roms\ within those I put cap32_model = "6128+ (experimental)" and cap32_model = "6128" respectively and in the game.cfg file I am assuming launchbox creates those to put the bezels around the games. I didnt touch those My Assumption is that is should take those in order and set the cap_model correctly. But it does not work. So fricking frustrating.

I am trying to pass a core config to a specific core within retroarch.cfg I have : core_options_path = "" global_core_options = "true" I created a filed called Amstrad_GX4000_core-options.cfg and I placed in in retroarch_root\config\cap32\ In that file I have the following cap32_advanced_green_phosphor = "15" cap32_autorun = "enabled" cap32_combokey = "select" cap32_db_mapkeys = "enabled" cap32_floppy_sound = "enabled" cap32_gfx_colors = "16bit" cap32_keyboard_transparency = "disabled" cap32_lang_layout = "english" cap32_lightgun_input = "disabled" cap32_lightgun_show = "disabled" cap32_model = "6128+ (experimental)" cap32_ram = "128" cap32_retrojoy0 = "auto" cap32_retrojoy1 = "auto" cap32_scr_crop = "disabled" cap32_scr_intensity = "8" cap32_scr_tube = "color" cap32_statusbar = "onloading" However it doesnt seem to take my core options I am passing it. What am I doing wrong? Its seem to always want to take the options from retroarch_root\retroarch-core-options.cfg

Sure I can upgrade again later this afternoon.

I already switched back to 13.18. This happens when I try to add roms. I have a mapped drive called games. Z drive. When I choose the importer is starts off in \\Home-server\balh\.blah instead of Z:\ even when I installed in Z:\ Then when I browse to Z:\path_to_roms it will insert the file path it has along with file:\ in the name prepended to the actual path

Issue resolved For some reason I had on retroarch to remove extentions. Not sure why other cores didnt have an issue with this.

I can confirm this is an issue with 13.19 luckily I still had the 13.18 laying on my server. Re-installed and all works again