@mitu

Sure i " said in Reicast doesn't work properly" because i solved after this topic and hope to solve completely all even with this problem in controller.

So the adapter emulates 2 joysticks, but only one is actually connected/working ?

Yes, it's all right.

@tackett1980 Cool.. you know, I'm just gonna say the difference in bios files might be a wild goose chase.. so only search for mine if you're really bored :P Hopefully the reicast folks will address the build issue with the stable branch on rpi3.

@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?

@pieguy123 said in Flycast and Reicast not emulating Capcom Vs SNK 2 correctly for character select screen:

I’m running the Japanese version.

I'm running the JP version (http://redump.org/disc/43772/) is there an US version ?

@BJRetro I confirm you'll need a gpu which is vulkan capable (and it's drivers). Currently i don't think there are many SBCs who have vulkan support (probably jetson nano ? maybe odroid N2 ?).

Try editing the mappings file directly, swapping the x or y axis or adding the inverted variable if needed.
Last i checked they were here

/home/$USER/.config/reicast/
or samba here
samba:\\ipaddress\configs\dreamcast\mappings\

@mitu Oh ok, that’s a bit of a bummer. At least I know why it doesn’t work though. No big deal, I mainly use it for MAME anyways. Thanks for all your help!

My issue was that the WinSCP wouldn't give me permission to change anything. But that video helped me to gain permission.

I'm still working on my main issue in getting Reicast to work properly. I had the same exactly issue as the ISeeTana and same hardware just the most recent Retropie version. I believe that everybody who has a new version of retropie will experience this issue with Dreamcast. It doesn't seem like it is anything our our end causing the problem.

I will be getting a pre-loadedSD card in the mail today and will check to see if Reicast works properly and the input controls work too.

@mitu hi thanks I checked the dynarec is marked as “yes” for enabled.

Finally got it working, I Had a backup of an older image I kept. Retropie 4.4.1
So I will need to check which version of reicast it is, also do you know if I choose to update the retropie script and update the OS and other emulators BESIDES reicast…. it should not effect reicast at all?

Thanks for the link to older version.. will have that as backup plan if need to.

The installation error is caused by

/usr/bin/ld: impossibile trovare -lGL

Do you have any 3rd party repositories enabled ? It looks like the OpenGL libraries are not found, which is not something that should happen on a normal installation.

One error i have, but for me is not urgent to resolve yet.
i think is a dev thing

enter to xmb retroarch menu, then resume...
this freezing the retroarch menu, also with rgui

@WildkatCT said in 4.5 Reicast BT PS3 controller setup not working correctly.:

Setting up a clean 4.5 image, can't see to get Reicast to configure controllers at all. Ran the controller setup utility, and all the button presses are detected, but in the actual emulator, only the analog stick works and the PS button is mapped to A.

Oddly though, the controller works fine when plugged in USB.

I tried manually changing the values on the .cfg file for the PS3 controller in reicast, but it doesn't seem to re-act to the changes, or at least the values I have are not corresponding to what reicast is expecting.

How can i get values that reicast would expect? Something like JS test, but those values don't seem to work.

@WildkatCT said in 4.5 Reicast BT PS3 controller setup not working correctly.:

Setting up a clean 4.5 image, can't see to get Reicast to configure controllers at all. Ran the controller setup utility, and all the button presses are detected, but in the actual emulator, only the analog stick works and the PS button is mapped to A.

Oddly though, the controller works fine when plugged in USB.

I tried manually changing the values on the .cfg file for the PS3 controller in reicast, but it doesn't seem to re-act to the changes, or at least the values I have are not corresponding to what reicast is expecting.

How can i get values that reicast would expect? Something like JS test, but those values don't seem to work.

Hello, I am experiencing this problem too, can't get any of my ps3 bt controllers to work with Reicast after the retropie 4.5 update, please help!

I have already configured the "emu.cfg" as showed below and my mappings inside the "mappings" folder are correct for my controllers.

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

@Maalik_ I see. I don’t know what happened that made reicast so screwed up recently. I was fortunate because when I built my bartop reicast was working the best it had and then we got access to lr-reicast (now Lr-flycast) and that was working well on the pi and even gave us access to some Naomi and atomiswave games and then all of a sudden it is like both projects fell off a cliff with a ton of users reporting various bugs. Sorry wish I could be more help.

@Dyelon hey pal, did you ever get it fixed? Having exact same issue as yourself. Bought USB encoders from amazon same thing.

Per another GM (Muti) on another Topic (which I had to heavily research for some reason)…

They're not enabled for the ODROID, only for the RPI/PC. If you wish to test them, you need to remove the !mali flag from the scriptmodules' rp_flags and re-run the setup script to appear