FBA vs. MAME

markwkidd

Edit: Nevermind. My proof needs to be in the pudding.

markwkidd

One more update. There is not a going to be a default mapping for the dual-joystick setup after all, but I did just add a core option that you can toggle to enter "Dual Joystick" mode for this kind of configuration. It is labelled "Dual Joystick Mode (Players 1 & 2)" in the RetroArch menu.

This core option uses a new way of integrating the libretro and MAME input systems that I am very excited about.

It's kept me up late tonight working because unlike similar past efforts to provide alternate modes for input, this core option keeps the MAME remapping menu up to date and accurate as you toggle the Dual Joysticks back and forth.

robertvb83

@markwkidd said in FBA vs. MAME:

Sorry we're now hopping back and forth between here and github.

In conclusion @robertvb83 , do I understand correctly the "Right Stick to Buttons" option is not relevant to setting up the joystick on a player 2 for games like Robotron? (From its name I would have not expected so but sometimes things have different/additional functions . I have never used that core option!)

yes correct this option is not relevant for my use case it is relevant if you have for example an xbox controller you can assign the right Joystick to button functions i guess (i dont use this). but no button binding from differen gamepads to one player is possible in retroarch

robertvb83

@markwkidd wow that sounds really really cool! because i think most noobs like me do not understand that there is a mame menu beyond the retroarch menu. it can be confusing, so such a switch you are talking about seems the perfect solution, you never know if peopledo things completely different and you keep everything as is but with a nice option.

i will test if i have time, can i just update mame2003-plus via retropie?

markwkidd

@robertvb83 said in FBA vs. MAME:

@markwkidd wow that sounds really really cool! because i think most noobs like me do not understand that there is a mame menu beyond the retroarch menu. it can be confusing, so such a switch you are talking about seems the perfect solution, you never know if peopledo things completely different and you keep everything as is but with a nice option.

i will test if i have time, can i just update mame2003-plus via retropie?

If you have a chance to test it that would be very greatly appreciated. Yes you can just update the core via RetroPie-Setup.

Do you have experience setting RetroArch core options? In this case it would be best to change the option only for the games that need it. Setting that option should be the only configuration involved, and it should adjust the mapping to be just the same as what you did manually in the MAME menu earlier.

robertvb83

@markwkidd said in FBA vs. MAME:

@robertvb83 said in FBA vs. MAME:

@markwkidd wow that sounds really really cool! because i think most noobs like me do not understand that there is a mame menu beyond the retroarch menu. it can be confusing, so such a switch you are talking about seems the perfect solution, you never know if peopledo things completely different and you keep everything as is but with a nice option.

i will test if i have time, can i just update mame2003-plus via retropie?

If you have a chance to test it that would be very greatly appreciated. Yes you can just update the core via RetroPie-Setup.

Do you have experience setting RetroArch core options? In this case it would be best to change the option only for the games that need it. Setting that option should be the only configuration involved, and it should adjust the mapping to be just the same as what you did manually in the MAME menu earlier.

now i feel a little dumb... i deleted the /roms/mame-libretro/mame2003-plus/cfg/robotron.cfg EDIT: and the default.cfg (undo the mame menu config)
i then updated mame2003-plus from source, now in RGUI i have the option available 2 Joystick mode. i can set it to enable then i create game override file.
but nothing happens...
i then close the game (start+select) and restart robotron... in RGUI the option is disabled again...? what do i do wrong... seems not so intuitive for me

markwkidd

@robertvb83 said in FBA vs. MAME:

@markwkidd said in FBA vs. MAME:

@robertvb83 said in FBA vs. MAME:

@markwkidd wow that sounds really really cool! because i think most noobs like me do not understand that there is a mame menu beyond the retroarch menu. it can be confusing, so such a switch you are talking about seems the perfect solution, you never know if peopledo things completely different and you keep everything as is but with a nice option.

i will test if i have time, can i just update mame2003-plus via retropie?

If you have a chance to test it that would be very greatly appreciated. Yes you can just update the core via RetroPie-Setup.

Do you have experience setting RetroArch core options? In this case it would be best to change the option only for the games that need it. Setting that option should be the only configuration involved, and it should adjust the mapping to be just the same as what you did manually in the MAME menu earlier.

now i feel a little dumb... i deleted the /roms/mame-libretro/mame2003-plus/cfg/robotron.cfg (undo the mame menu config)
i then updated mame2003-plus from source, now in RGUI i have the option available 2 Joystick mode. i can set it to enable then i create game override file.
but nothing happens...
i then close the game (start+select) and restart robotron... in RGUI the option is disabled again...? what do i do wrong... seems not so intuitive for me

This isn't happening in standalone RetroArch but grant is also having the same issue with retropie. The way it should work is that the new core option should be set to enabled on a per-game basis for those games that need it. While it's on you don't need to do a custom config.

This is working right now for standalone RetroArch so there is probably a fix. Apologies that you are stuck with us for a minute.

markwkidd

grant found the error @robertvb83 -- it was a serious typo on my part, but not the kind that causes a compiler message. nasty!

If you give us one more recompile then it should be possible to save an individual game core option for robotron with the command at the top of the the RetroArch GUI options screen, as normal.

0_1526843920910_Screenshot 2018-05-20 14.17.35.png

Note that I am using outrun for my testing. Not the most appropriate game for dual joysticks!

robertvb83

@markwkidd is it already online can i compile now?

grant2258

@robertvb83 said in FBA vs. MAME:

@markwkidd is it already online can i compile now?

yes ive compiled and tested its working

robertvb83

@grant2258 wow you guys are damn fast :-). ill try in a minute
EDIT: tested and working. so cool! i think it reall makes things easier. no messing around with the sort of hidden mame tab nenu, very convenient solution.

Loggahead

@robertvb83 said in FBA vs. MAME:

@udb23 the option in lr mame is not working for me because i use seperate usb controllers for p1 and p2...
however via mame menu i finally made it work!

@grant2258 oh my god you are right it is working! via mame menu i can assign the p2 buttons totally flexible. i did not know about this possibility i always used retroarch menu...
THANK YOU! i was close to giving up here after searching the compkete internet (grant was pointing me into that direction ib github issue discussion)
its so cool to play robotron now like its meant to be played!

Yup, just now catching up on this thread. This is exactly what I did. Just used the mame menu to map the P2 joystick as the P1 right joystick. I also did this for Smash TV, Black Widow, and Wacko.

Loggahead

I just came across an isse trying to run Shock Trooper (shocktro.zip) using FBA. I am on retropie 4.4 on an rpi3b and update fba from source to check that. Here is part of the run command verbose log I get when trying to launch it:

[libretro WARN] [FBA] Searching ROM at index 0 with CRC 0xefedf8dc and name 238-pg1.p1 => Not Found
[libretro WARN] [FBA] Searching ROM at index 128 with CRC 0x91b64be3 and name asia-s3.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 129 with CRC 0x9036d879 and name sp-s2.sp1 => Not Found
[libretro WARN] [FBA] Searching ROM at index 130 with CRC 0xc7f2fa45 and name sp-s.sp1 => Not Found
[libretro WARN] [FBA] Searching ROM at index 131 with CRC 0xe72943de and name sp-u2.sp1 => Not Found
[libretro WARN] [FBA] Searching ROM at index 132 with CRC 0x62f021f4 and name v2.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 133 with CRC 0x2723a5b5 and name sp-e.sp1 => Not Found
[libretro WARN] [FBA] Searching ROM at index 134 with CRC 0x2025b7a2 and name sp1-u3.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 135 with CRC 0xf0e8f27d and name vs-bios.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 136 with CRC 0xacede59c and name sp-j2.sp1 => Not Found
[libretro WARN] [FBA] Searching ROM at index 137 with CRC 0x9fb0abe4 and name sp1.jipan.1024 => Not Found
[libretro WARN] [FBA] Searching ROM at index 138 with CRC 0x03cc9f6a and name sp-45.sp1 => Not Found
[libretro WARN] [FBA] Searching ROM at index 139 with CRC 0xdff6d41f and name japan-j3.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 140 with CRC 0xfbc6d469 and name sp1-j3.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 141 with CRC 0x16d0c132 and name neo-po.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 142 with CRC 0xd27a71f1 and name neo-epo.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 143 with CRC 0x698ebb7d and name neodebug.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 144 with CRC 0x162f0ebe and name sp-1v1_3db8c.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 145 with CRC 0x24858466 and name uni-bios_3_3.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 146 with CRC 0xa4e8b9b3 and name uni-bios_3_2.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 147 with CRC 0x0c58093f and name uni-bios_3_1.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 148 with CRC 0xa97c89a9 and name uni-bios_3_0.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 149 with CRC 0x27664eb5 and name uni-bios_2_3.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 150 with CRC 0x601720ae and name uni-bios_2_3o.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 151 with CRC 0x2d50996a and name uni-bios_2_2.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 152 with CRC 0x8dabf76b and name uni-bios_2_1.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 153 with CRC 0x0c12c2ad and name uni-bios_2_0.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 154 with CRC 0xb24b44a0 and name uni-bios_1_3.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 155 with CRC 0x4fa698e9 and name uni-bios_1_2.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 156 with CRC 0xe19d3ce9 and name uni-bios_1_2o.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 157 with CRC 0x5dda0d84 and name uni-bios_1_1.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 158 with CRC 0x0ce453a0 and name uni-bios_1_0.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 159 with CRC 0xcb915e76 and name neopen.sp1 => Not Found
[libretro WARN] [FBA] Searching ROM at index 162 with CRC 0x94416d67 and name sm1.sm1 => Not Found
[libretro WARN] [FBA] Searching ROM at index 163 with CRC 0xc2ea0cfd and name sfix.sfix => Not Found
[libretro WARN] [FBA] Searching ROM at index 164 with CRC 0x5a86cff2 and name 000-lo.lo => Not Found
[libretro INFO] [FBA] Parsing archive /home/pi/RetroPie/BIOS/neogeo.
[libretro WARN] [FBA] Searching ROM at index 0 with CRC 0xefedf8dc and name 238-pg1.p1 => Not Found
[libretro WARN] [FBA] Searching ROM at index 134 with CRC 0x2025b7a2 and name sp1-u3.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 140 with CRC 0xfbc6d469 and name sp1-j3.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 141 with CRC 0x16d0c132 and name neo-po.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 142 with CRC 0xd27a71f1 and name neo-epo.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 143 with CRC 0x698ebb7d and name neodebug.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 145 with CRC 0x24858466 and name uni-bios_3_3.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 159 with CRC 0xcb915e76 and name neopen.sp1 => Not Found
[libretro INFO] [FBA] Parsing archive /home/pi/RetroPie/roms/arcade/0 FBA/shocktro.
[libretro WARN] [FBA] **Searching ROM at index 0 with CRC 0xefedf8dc and name 238-pg1.p1 => Not Found**
[libretro WARN] [FBA] Searching ROM at index 134 with CRC 0x2025b7a2 and name sp1-u3.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 140 with CRC 0xfbc6d469 and name sp1-j3.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 141 with CRC 0x16d0c132 and name neo-po.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 142 with CRC 0xd27a71f1 and name neo-epo.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 143 with CRC 0x698ebb7d and name neodebug.bin => Not Found
[libretro WARN] [FBA] Searching ROM at index 145 with CRC 0x24858466 and name uni-bios_3_3.rom => Not Found
[libretro WARN] [FBA] Searching ROM at index 159 with CRC 0xcb915e76 and name neopen.sp1 => Not Found
[libretro INFO] MVS Neo Geo Mode selected => Set NeoSystem: 0x00 (asia-s3.rom [0x91b64be3] (MVS Asia/Europe ver. 6 (1 slot))).
[libretro ERROR] [FBA] ROM at index 0 with CRC 0xefedf8dc is required ...
[libretro ERROR] [FBA] Cannot find driver.
[libretro ERROR] [FBA] Cannot load this game.
[ERROR] Failed to load content.

I noticed that it is looking for a file called 238-pg1.p1 and when I open shocktro.zip there is only a file names 238.p1.p1. Could that be the issue? This same rom worked perfectly on 4.3 and all my other neo geo roms are still working now.

Any thoughts?

mitu

@loggahead You should open a new topic for this particular problem, but anyway - it's probably because the Romset has changed between FBAlpha 0.2.97.42 (which was the default in RetroPie 4.3) and FBAlpha 0.2.97.43 - which is the version you get if you update from source right now.

Loggahead

@mitu said in FBA vs. MAME:

you get if you update from source right now.

roger that and sorry about posting here. I've just noticed a lot posts about fixing particular games in this thread. I'll make a topic under help / support.

AndersHP

@Pussyfoot @markwkidd @cosmo0
are these "optimal cores" still being updated after 0.2.97.43 and do we have some place online to find the complete lists with best cores? I see you @cosmo0 have been asking and concluding things above, but shouldn't we have a central place to store these lists for easy access?

markwkidd

We (mostly arcadez) is doing a thorough job of maintaining the mame2003-plus CHANGELOG. The intention is that be a reliable reference for the one core at least. If someone notices something wrong or out of date it with, an issue report or PR is very welcome. That's what I can commit to helping with as part of the overall goal of having accurate information.

Edit: In addition, arcadez and @grant2258 have both have been keeping the status of individual games updated at the driver level, so it's possible to in theory produce reports and gamelists for mame2003-plus that have details about whether games have known issues, how severe they are, does the issue affect sound, etc.

That information should be the basis of any data-driven/spreadsheet type analysis. The changelog is for more qualitative human use.

AndersHP

@markwkidd Allright, I might start getting into this MAME2003_plus business. Is there generally no downside compared to the default MAME2003 emulator?

Do you have the supported games in MAME 2003_plus on a list, to replace my old mame2003 list?

This would come in handy when building the Arcade folder to contain both FBA and MAME2003_plus.

robertvb83

@andershp fba has also updated, so we can start fresh ;-)

AndersHP

@robertvb83 yeah. Actually, it's really hard to find out what to do when building a combined Arcades folder.. Both the FBA and MAME2003_PLUS boys are making progress all the time. But having 2 nearly identical romsets on your build just seems silly.