Controller profile issue with standalone cores 4.5

General
1

Since the additional standalone cores were added in .4/.5 I’ve had trouble with the controller profiles.
I am using 2x PS3 original six axis controllers (not dual shock) i have mapped all the buttons succesfully except for Glide on the N64. The issue is that on Dreamcast and Playstation player 1 controller basically switches to player 2 once the game is loaded so I then have to use the player 2 controller to actually be player 1 in the game.
It’s not a massive issue but it is rather annoying, if anybody knows how to fix this it would be appreciated.

Also would like to say thank you for the work you put into this, the new standalone cores and resolution output options have enabled me to really push the N2+ with graphics that are like what I remember back in the early days of gaming!

2

Which emulators are you running? Is this for the Flycast and Duckstation standalone emulators? Or the retroarch libretro emulators?

3

Yes sorry, for the standalone cores. With libretro cores everything autoconfigs perfectly.
I wondered if its because they are both the same controller and the id’s are getting confused but i don’t have another controller to test.

4

Most likely the way it auto configs, it’s sorted by /dev/input/js0 then 1 etc. But in your case the 2nd must be getting assigned to js0. Are they the exact same controllers?

5

That sounds like a possibility, im afraid im not much more help as its outside of my abilities.

Yes both exactly the same controller type

6

connect both up, ssh in and run this command:

cat /proc/bus/input/devices

then paste output in here:
https://gist.github.com/

7

##############################################

EmuELEC

Retro emulation for Amlogic Devices

Based on CoreELEC

##############################################
EmuELEC (Official - EmuELEC is FREE! NOT FOR SALE!): 4.5 (Amlogic-ng.aarch64)
EMUELEC:~ # cat /proc/bus/input/devices
I: Bus=0010 Vendor=1b8e Product=0cec Version=0001
N: Name=“cec_input”
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=1 0 0 10000000000000 0

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name=“meson-ir”
P: Phys=meson-ir/input0
S: Sysfs=/devices/platform/ff808040.meson-ir/rc/rc0/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=100013
B: KEY=fff 0 4200108fc32e 237605100000000 0 700158000 419240004801 9e96c000000000 10000ffc
B: MSC=10

I: Bus=0005 Vendor=054c Product=0268 Version=8000
N: Name=“Sony PLAYSTATION(R)3 Controller Motion Sensors”
P: Phys=00:1a:7d:da:71:13
S: Sysfs=/devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:70/0005:054C:0268.0002/input/input5
U: Uniq=00:1e:3d:96:d9:24
H: Handlers=event2 js0
B: PROP=40
B: EV=9
B: ABS=7

I: Bus=0005 Vendor=054c Product=0268 Version=8000
N: Name=“Sony PLAYSTATION(R)3 Controller”
P: Phys=00:1a:7d:da:71:13
S: Sysfs=/devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:70/0005:054C:0268.0002/input/input4
U: Uniq=00:1e:3d:96:d9:24
H: Handlers=event3 js1
B: PROP=0
B: EV=20001b
B: KEY=f00000000 0 0 0 7fdb000000000000 0 0 0 0
B: ABS=3f
B: MSC=10
B: FF=107030000 0

I: Bus=0003 Vendor=054c Product=0268 Version=8111
N: Name=“Sony PLAYSTATION(R)3 Controller Motion Sensors”
P: Phys=usb-xhci-hcd.0.auto-1.2/input0
S: Sysfs=/devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.2/1-1.2:1.0/0003:054C:0268.0003/input/input7
U: Uniq=00:1e:3d:b4:2b:71
H: Handlers=event4 js2
B: PROP=40
B: EV=9
B: ABS=7

I: Bus=0003 Vendor=054c Product=0268 Version=8111
N: Name=“Sony PLAYSTATION(R)3 Controller”
P: Phys=usb-xhci-hcd.0.auto-1.2/input0
S: Sysfs=/devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.2/1-1.2:1.0/0003:054C:0268.0003/input/input6
U: Uniq=00:1e:3d:b4:2b:71
H: Handlers=event5 js3
B: PROP=0
B: EV=20001b
B: KEY=f00000000 0 0 0 7fdb000000000000 0 0 0 0
B: ABS=3f
B: MSC=10
B: FF=107030000 0

From your earlier comment it looks like they’ve got different numbers assigned…
It seems like there are 4 entries for the pair of controllers. I read that it was advised to first connect and map the PS3 controllers using wired connection and then do the same again with the bluetooth adaptor so everything works correctly.

I just did a quick test and when using both controllers as wired connection the player numbers are correct, this issue only seems to happen once they are connected by bluetooth.

8

Sorry, overlooked about pasting to github, let me know if you need it on there and will sort that out.

9

I think this bug is more to do with the way SDL detects and orders wireless game controllers. The Flycast config looks for SDL Game Controller 0 and 1 in that order. If it’s flipping the issue is with SDL or even the bluetooth driver. I would like to know if more have this issue.

10

Ok, I’ll have to leave that with you as I can’t help much more than that.
Just for info I loaded Soulcalibur on Dreamcast with both controllers turned on and went to Arcade mode and I’m put into player 2 position. Reset the system and turn controllers on in opposite order and the same thing happens.
I have also tried to order them using the emuelec system menu but that made no difference either.
If I only turn 1 controller on I have no issues…

11

I tested this briefly. If I launch the game with the 2nd controller I can control the game menu, but not the system menu of flycast standalone. 2nd controller also put me in 2nd position during a vs in daytona. So if you launch the game with the first controller does it become the first player. Also I noticed your controllers are the same but different versions.

12

I tested on Daytona, if i start the game with player 1 control, when the race starts its controlling player 2 car.
The version numbers are the same for each pair of controls but they have different numbers for the bluetooth and wired configurations, for some reason…

13

@kallabungo Hey man can you run the following command, when both controllers are hooked up wirelessly? the output you done before indicates that one was connected via usb.

14

EMUELEC:~ # cat /proc/bus/input/devices
I: Bus=0010 Vendor=1b8e Product=0cec Version=0001
N: Name=“cec_input”
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=1 0 0 10000000000000 0

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name=“meson-ir”
P: Phys=meson-ir/input0
S: Sysfs=/devices/platform/ff808040.meson-ir/rc/rc0/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=100013
B: KEY=fff 0 4200108fc32e 237605100000000 0 700158000 419240004801 9e96c000000000 10000ffc
B: MSC=10

I: Bus=0005 Vendor=054c Product=0268 Version=8000
N: Name=“Sony PLAYSTATION(R)3 Controller Motion Sensors”
P: Phys=00:1a:7d:da:71:13
S: Sysfs=/devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:71/0005:054C:0268.0001/input/input4
U: Uniq=00:1e:3d:b4:2b:71
H: Handlers=event2 js0
B: PROP=40
B: EV=9
B: ABS=7

I: Bus=0005 Vendor=054c Product=0268 Version=8000
N: Name=“Sony PLAYSTATION(R)3 Controller”
P: Phys=00:1a:7d:da:71:13
S: Sysfs=/devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:71/0005:054C:0268.0001/input/input3
U: Uniq=00:1e:3d:b4:2b:71
H: Handlers=event3 js1
B: PROP=0
B: EV=20001b
B: KEY=f00000000 0 0 0 7fdb000000000000 0 0 0 0
B: ABS=3f
B: MSC=10
B: FF=107030000 0

I: Bus=0005 Vendor=054c Product=0268 Version=8000
N: Name=“Sony PLAYSTATION(R)3 Controller Motion Sensors”
P: Phys=00:1a:7d:da:71:13
S: Sysfs=/devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:65/0005:054C:0268.0002/input/input6
U: Uniq=00:1e:3d:96:d9:24
H: Handlers=event4 js2
B: PROP=40
B: EV=9
B: ABS=7

I: Bus=0005 Vendor=054c Product=0268 Version=8000
N: Name=“Sony PLAYSTATION(R)3 Controller”
P: Phys=00:1a:7d:da:71:13
S: Sysfs=/devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:65/0005:054C:0268.0002/input/input5
U: Uniq=00:1e:3d:96:d9:24
H: Handlers=event5 js3
B: PROP=0
B: EV=20001b
B: KEY=f00000000 0 0 0 7fdb000000000000 0 0 0 0
B: ABS=3f
B: MSC=10
B: FF=107030000 0

The version numbers are all the same now - I must have had a controller charging when I previously ran the command, sorry!

15

Ok I have made a revision to joy_common which will hope get controllers in the right order? Do you know how to build EmELEC with pull requests? If not I’ll just test it locally.

16

Here is the pull request if you want to test it out:

17

I honestly have no idea with that, I could probably work it out over time but I’ve never built an image and don’t even know what program I would use?
Really appreciate your efforts on this though, thank you.

18

You need a linux distro like Ubuntu to build and instructions here:

But yeah, you might just have to wait until an update comes out. I’m a bit hesitant to release this change though since it might break the ordering for other people configurations.

19

I did some research and found Ubuntu to be an operating system that I can run alongside windows but I don’t really want Linux on my laptop. I then came across Docker which seemed like it would do what I wanted.

Using the commands on the instruction page populated a local emuelec folder but I’m struggling to find the correct command to build the image. “Make image” on this program doesn’t appear to work.

I believe the correct command is: docker build -t emuelec .

From my digging online but that hasnt worked.

I believe I have the files to create the image, I’ve replaced the joy_common so it’s just trying to actually make an image from it…

As you can tell, I’m out of my depth here! :slightly_frowning_face:

20

If you do not want linux running alongside but still want to build I suggest using virtualbox or workstation player to run a virtual instance of linux and compile a build. I’m not so sure about docker being able to do it.

references:
https://www.virtualbox.org/