You appear to be correct! :)

When I did a BezelProject install, I got a different set... I think I'm good now but can someone make a quick comment on the 2x sets that BezelProject offers. How did I unintentionally grab one set versus the other?

I obviously managed to select the other set on my previous attempt! :)

Cheers!

Thanks, that seems to get rid of that console error. Now the games just hang, will do some more troubleshooting :D

@retropieuser555 please open a new topic and provide details of set up.

Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@Gobon-Shiteinga See https://retropie.org.uk/docs/FinalBurn-Neo/ and https://github.com/finalburnneo/FBNeo for more information.

That's great to know

@Dan1300 @bollwerk said in MAME not running ROMs issue:

It is perhaps worth noting that, I believe it's possible to create a romset for any version of MAME, by using the latest romset, the latest "rollback" romset, a DAT file from the version of MAME you need a set for, and a tool like ClrMamePro.

I agree I think it's worth noting and worth bothering to learn to use the tools depending on your setup. With current MAME and the rollback sets you can build any version of MAME from the beginning of development for RetroPie or other projects outside the RP scope.

You can build partial or full sets which is handy if using multiple cores with "Arcade" for RetroPie and only need a few games from a specific ROM set or a few per core.

It works fine for vanilla MAME to just get the set from whatever source. If using mame2003-plus or fbneo who's rom sets are ever changing it's a big plus to know the tools but you'll still need to track down some miscellaneous or decrypted ROMs that may not included in the official MAME set when rebuilding.

I find it easier to grab the current DAT once in a while for a changing core to complete a set vs. following every commit to grab the added/updated ROMs.

Also mame2003-plus has the source driver files in the DAT which allows you to build subsets like neogeo only or cps1, cps2, cp3 or whatever combination you want. Now if we could only have the region information.

Along with the rollback CHDs you can include those also in your sets too which is usually v3 with the older cores. A few games with CHDs run acceptably on the Pi 4.

Mame2003-plus has support for UNIBIOS up to 4.0 if you have a need, want to tweak a setting or experiment, it's a core option.

@Gryphon RetroPie already installs a compiler, you need to install the dependencies, as described in https://docs.mamedev.org/initialsetup/compilingmame.html#debian-and-ubuntu-including-raspberry-pi-and-odroid-devices, download the source archive, unpack it and then run make from the sources folder - with the options outlined in the docs.
Here an outline of the process (you can skip any SDL installation commands, they're not needed on a RetroPie installation).

@Kartman Hello, I cannot find a good scanline reproduction with ADVMame. It does not use shaders, only overlays. Tried to make a few scanline overlays and had no luck. There are video options for scanlines, but I could not find anything that looked as good as shaders do.

@Zodiark12 said in FBNeo Set missing samples?:

this seems to be for 1.0.0.0 while I'm using the set 0.2.97.44.

they didn't change for months, maybe years, so that won't be a problem

@kgm316 via what method are you changing them? please fill out https://retropie.org.uk/forum/topic/3/read-this-first

@BuZz Thanks for looking into it. I saw that you have implemented a temporary fix until it's fixed upstream. I will test this and see how it works.

@rejesterd said in Reicast - Mapping controllers??? (2020 version). Stuck.:

@Plex7 Trying to save you some reading here, in case you do eventually come back to this. Going back to the settings shown in your very first post, here's how you map your Microntek USB Joystick controllers (i.e. evdev devices #2 and #3, as shown in your reicast-joyconfig output):

Step 1: Uninstall and re-install reicast.

Step 2: If you haven't done so, map the Microntek controllers in Emulation Station.

Step 3: Run reicast-joyconfig for one of the controllers, and save the output to ~/.reicast/mappings/evdev_Microntek USB Joystick.cfg. Make sure the file is named EXACTLY 'evdev_Microntek USB Joystick.cfg' with the spaces.

Step 4: Search for 'Microntek' in /opt/retropie/configs/all/emulationstation/es_input.cfg

$ grep -i 'Microntek' /opt/retropie/configs/all/emulationstation/es_input.cfg

This will spit out an <inputConfig> element that contains a property called 'deviceGUID'. This deviceGUID corresponds to your deviceName. It will be a long string with letters and numbers like..

deviceGUID="05000000c82d00000161000000010000"

Step 5: Modify the [input] section in ~/.reicast/emu.cfg as follows:

[input] MouseSensitivity = 100 VirtualGamepadVibration = 20 device1 = 0 device1.1 = 1 device1.2 = 1 device2 = 0 device2.1 = 1 device2.2 = 1 device3 = 8 device3.1 = 8 device3.2 = 8 device4 = 8 device4.1 = 8 device4.2 = 8 maple_/dev/input/event2 = 0 maple_/dev/input/event3 = 1 maple_/dev/input/event4 = -1 maple_<YourDeviceGUID> = -1

..where <YourDeviceGUID> is the string you obtained in the previous step above.

Step 6: Also in ~/.reicast/emu.cfg, remove the [players] section you added previously. It's not needed.

Step 7: Reboot and give it a try.

Edit: If you see any other maple_* devices show up in emu.cfg after rebooting, set their values to -1 (which means reicast should ignore them).

And for anyone else who is curious about the [input] device settings..

device1 = 0 # controller 1 is of type 'Sega Controller' (0) device1.1 = 1 # controller 1's primary vmu is of type 'Sega VMU' (1), and is stored in ~/.reicast/vm_save_A1.bin device1.2 = 1 # controller 1's secondary vmu is of type 'Sega VMU' (1), and is stored in ~/.reicast/vm_save_A2.bin device2 = 0 # controller 2 is of type 'Sega Controller' (0) device2.1 = 1 # controller 2's primary vmu is of type 'Sega VMU' (1), and is stored in ~/.reicast/vm_save_B1.bin device2.2 = 1 # controller 2's secondary vmu is of type 'Sega VMU' (1), and is stored in ~/.reicast/vm_save_B2.bin device3 = 8 # controller 3 is not configured .... device4 = 8 # controller 4 is not configured .... maple_/dev/input/event2 = 0 # /dev/input/event2 (Microntek USB Joystick) is controller 1 maple_/dev/input/event3 = 1 # /dev/input/event3 (Microntek USB Joystick) is controller 2 maple_/dev/input/event4 = -1 # ingore the Logitech Gamepad F710 maple_<YourDeviceGUID> = -1 # ignore the configuration for Microntek USB Joystick that is set in /opt/retropie/configs/all/emulationstation/es_input.cfg

Ok I'm hoping you can help me, 2 player controls was working great when I had only 2 controllers using Dragonrise encoders (easy get). Here is the device guid

<inputConfig type="joystick" deviceName="DragonRise Inc. Generic USB Joystick " deviceGUID="03000000790000000600000010010000">

And here is the working emu.cfg for 2 controllers

[input] MouseSensitivity = 100 VirtualGamepadVibration = 20 device1 = 0 device1.1 = 1 device1.2 = 1 device2 = 0 device2.1 = 1 device2.2 = 1 device3 = 8 device3.1 = 8 device3.2 = 8 device4 = 8 device4.1 = 8 device4.2 = 8 maple_/dev/input/event2 = 0 maple_/dev/input/event3 = 1 maple_03000000790000000600000010010000= 1 maple_sdl_keyboard = 0 maple_sdl_mouse = 0

I then used the same setup and hooked up 4 controllers to a 4 Player cabinet. All the same Dragonrise encoders. I have the 4 controllers going into a 4port hub plugged into USB port 1 on the Pi3, then a trackball to port 2, then a mouse/keyboard combo into port 3. Player 1 works as Player 2... resulting in only 1 controller working. Reicast changed the Emu.cfg to the following

[input] MouseSensitivity = 100 VirtualGamepadVibration = 20 device1 = 0 device1.1 = 1 device1.2 = 1 device2 = 0 device2.1 = 1 device2.2 = 1 device3 = 8 device3.1 = 8 device3.2 = 8 device4 = 8 device4.1 = 8 device4.2 = 8 maple_/dev/input/event2 = 0 maple_/dev/input/event3 = 1 maple_/dev/input/event4 = 1 maple_/dev/input/event5 = 2 maple_/dev/input/event6 = 3 maple_03000000790000000600000010010000 = 1 maple_sdl_keyboard = 0 maple_sdl_mouse = 0

I am hoping if I change some of these device/event values it should solve the problem? Do you know what I can try to change?

I switched it to 1080p and it works perfectly. Thank you!

@Izzii0x Welcome to this forum. Some friendly words of advice:

Please give us all the information about your system that's asked for in https://retropie.org.uk/forum/topic/3/read-this-first In general, it is advisable to open a new thread about your problem rather than to "necro" (forum slang) a thread that began 2½ years ago, as your problem could be caused by completely different things than those discussed here earlier.

@mitu said in Caps Lock capture problem:

Try pressing Scroll Lock first.

Thanks for replying mitu, much appreciated. I will try this as soon as possible. :)

That's Final Burn.

You can probably use the Configuration Editor and set the shader for all libretro based emulators. Daphne is not a libretro emulator, so the settings wouldn't apply anyway.