Dreamcast Button Mapping for PS3 DS3 Controller

This site is best viewed in a modern browser with JavaScript enabled.

wortlaich

Hi everyone,
I tried the Reicast Emulator on a Odroid XU4 and it works pretty well. Except for the controller. I use an original Sony PS3 DS3 Controller. The Button Mapping seems to be okay, but the left Analog Stick doesn't work as it should. If you push the left Analog Stick to the left it works at first but if you push it to the far left it then turns into a different signal. In Sonic Adventure for example, I can turn left if I move the Analog stick just a bit. If I move it too much Sonic suddenly turns right instead of left. Something must be wrong with the axis configuration.
I tried to change the config (https://github.com/retropie/retropie-setup/wiki/Dreamcast) in the emu.cfg or controllerP1.cfg files but these files revert to their original state everytime reicast is started.
Anybody got an idea?

luizthiago

wortlaich Friend, you solved this problem ? any things to do ?

nadenislamarre

hi.
i guess the bug is in this file : https://github.com/nadenislamarre/recalbox-configgen/blob/batocera-5.X/configgen/generators/reicast/reicastControllers.py

this file is called to create the controller file when you run a dreamcast game. it's why your file is erased.
This file can be modified in live :

mount -o remount,rw /
cd /usr/lib/python27/site-packages/configgen/generators/reicast # approximative path

wortlaich

This seems to be the right file but changing it would require to make the squashfs (/dev/loop1 / squashfs ro,relatime 0 0) writable which seems to be a pain. I'll give it a try later.

nadenislamarre

@wortlaich no, you can modify it.
i placed an overlay over the squashfs to make it writtable.

just follow :
https://batocera-linux.xorhub.com/wiki/doku.php?id=en:modify_the_system_while_it_s_running

mount -o remount,rw /
vi
/recalbox/scripts/recalbox-save-overlay.sh

wortlaich

Im using a XU4 and can't make the rootfs readable. I guess this is the issue stated on the site you mentioned? "Note : it cannot be done for the current Odroid xu4 version." I'm using the latest beta (20170404).

nadenislamarre

@wortlaich if you create a usb key and reproduce on a computer, you will be able to easyly found and fix the problem. i'll be able to update the file for the next update.

Gutozdf

Hey, I´m having the exactly same issue.

Please, any way I could fix it without use linux? If I have to use, can you give a tutorial? Im using a PS3 Shanwan controller, Batocera 5.8 on PI3.

luizthiago

Same problem Here... Now, in 5.16 (New fresh install in RASPBERRY PI 3) Ps3 Shanwan pad with "official" driver in RECALBOX.CONF.

In the past my control would normally pair with the "bluez" driver and everything worked fine. However, now, in this new installation, it only accepts the "official" or "Shanwan" driver, but both cause this problem ONLY in the DreamCast emulator ....

DragonRaise generic PS3 USB controls work OK on DreamCast, but my bluetooth control does not .... it goes all around and the analog directional refuses to go up and left.

what to do ? is there any palliative to solve the problem?

Maybe return the "bluez" driver to older version thats my pad pair OK with this ...

nadenislamarre

sorry, i don't understand the problem precisely.
- it is a regression from 5.15 or before ?
- is it for any ps3 controller or just "PS3 DS3 Controller" ?
- does it fail in usb or in bluetooth or none of them ?

it look like to be a reicast issue + "PS3 DS3 Controller", can you send a report file please ?

luizthiago

nadenislamarre I have an generic PS3 Shanwan control ....

before i have made my clean install, all works ok because i have updating my system for last 5.08 to actual 5.16 and bluez driver even pair my bluetooth pad OK.

with bluez, if i pair my control with bluetooth mode, it's recognized as "PLAYSTATION(R)3Conteroller-PANHAI" , and all works OK in DreamCast.

but with my clean install, the bluez driver don't works anymore, my bluetooth not pair and i have to use the Official or Shanwan driver ...both are work for other emulators, but not for DC.

you can put ther old driver for bluez to work ?

luizthiago

nadenislamarre I'll explain:

Version 5.15 or 5.16 does not work with the bluez driver ... maybe you know some way to turn this drive back to a previous version where the bluez driver seemed to normally pair my control, being recognized as PANHAI and all works fine.
With the clean install, only the official or shanwan drives work to pair the control, but in both the same problem occurs.
It seems to occur for any version of the PS3 control, as it was first reported here in 2017 that the friend had the same probme as mine, however, his control is official and uses the official driver. I have not faced this problem since the old versions were being updated and my PANHAI control was perfectly functional with the bluez driver. as my control is not official but a generic, but that of the friend was official, I believe that it happens with any control of the variant PS3 being official or generic.
The problem occurs only if the control is used in bluetooth mode. Yesterday I did the test and the same control I have is detected as "SHANWAN" if plugged in the cable, or PS3 OFFICIAL if connected with bluetooth either using the official driver or the shanwan "- the same control, connected by the cable, does not cause the problem, however, connected via bluetooth causes the problem.

It seems that there must be a problem with the official driver and shanwan regarding the generation of configuration of the axes (problem that was not with me using the driver bluez) or in the script that generates the configuration of controls for this emulator.

What occurs:? - The axis configured to command the character (left) does not work properly. if I push it to the middle to the left or half to the top it works, but if I continue to push until the end of the lever it reverses and the top becomes low and the left becomes right .... what is or is a failure in generating the script for the controls if used official driver or shanwan ...

maybe, if you can regret the bluez driver to an old version before this problem, my pad can work again in Reicast, but the oficial driver and shanwan still continue with this problem too ....

Do you need me to generate a support file for you?

superMDMArio

nadenislamarre I have this same problem.

Using the same control over the USB cable works perfectly.

I think the problem is in the bluetooth configuration.

I can not test bluez because i can not pair.

I use rpi3b+ and can not test versions prior to 5.15.

In 5.15 it presents the same problem.

luizthiago

nadenislamarre The retropie has tested and this problem not occurs... Even in The Shanwan or gasia drivers... In script configuration has an inverted X axis and inverterd y axis as NOT.

See it Here : https://pastebin.com/4CNLJdB7

This can be The solution for The problem, no?

axis_x_inverted = no
axis_y_inverted = no

luizthiago

nadenislamarre I have tested a new clean install off 5.15 and same problem ocurr ....

if i made a new clean install of 5.14, the problem not occuring ....

this problem is related to new version of the bluez driver before 5.14 version ...

i pair my pad ok with 5.14 and make a update to 5.16 into the system update option ...

after update, my pad still working, but, when i try to pair a new pad as not pair before the update (same pad type and model), this is not pairing !

please, return the old bluez driver to 5.14 version, but it's OK !!

I have updated my support file for you to help solving this problem ....

suport file here : https://we.tl/IpyPZVHBHS

luizthiago

@nadenislamarre could you tell me in which version the bluez driver was updated / changed so that it no longer matched my control? because in the versions where I was always updating it was always ok because probably this driver is not changed in updates .. only in clean installation. My attempt I wanted to make in another SD is to install an older version, type 5.14, see if the bluez driver works and if it is OK. if it is, I upgrade to 5.16 and see if the "full screen" is working in the other emulators and if DreamCast will be running OK with this driver .. if all goes well, I do the same on my 64GB main SD ... .It would be an alternative until I discovered the problem. I think the cause is related to the axis limit in the script that generates the configuration of controls in this emulator. and is related to Driver bluetooth since the same control with USB cable works well, but if you are in bluetooth mode do not! The crash is apparently associated with the "Official" and "shanwan" drivers since I did not have the problem with Bluez and needed it to work so I could confirm ...

If you know, tell me in which version the bluez driver has not yet been changed so that I make tests here on my side too ....

I'll also try to generate the support file you requested.

The problem now occurs with original or generic PS3 controls, since everyone has to use the other drivers ...

Thanks so much if you can help me!

nadenislamarre

@luizthiago bluetoothctl --version to get the bluez version. i don't think i've changed it at the end between versions.
so i understand:
- there is a paring issue on 5.15 and 5.16 with the ps2 ds3 controller
- the mapping in dreamcast is broken only with this pad ; remapping the buttons doesn't help.

it's hard to help you while i can't reproduce while i've not the problematic hardware.
moreover, i dont understand if there is a link between the paring issue and the dreamcast issue. you seem to tell that after updating, without a fresh install, the pad is working, but i don't understand if you were under dreamcast or not.

luizthiago

nadenislamarre The pair problem is related tô the bluez driver... If i can pair with bluez, The DreamCast works ok with my Ps3 pad. If i Can't pair with bluez (5.15 or New), i have tô pair with official OE Shanwan drivers and The DreamCast problem occurs...

luizthiago

nadenislamarre about your quests:
- yes, the problem exists, but in an clean install of 5.15 , not occur ....in 5.16, i have this problem in an clean instal
- yes, the mapping don't help for solve this problem on DC

the mapping problem with bluez it's associate to the DC because if i pair with bluez suceffuly, the DC problem dont occur, but, if i can pair only with official or shanwan, the problem in DC occurs ....

If i update from an 5.15 or older version with my pads paired previously the 5.16, these pads still working ok and paired with the system (with bluez) - [ maybe because then has linked to the system before the update ] , but, if i try to pair a new pad of same type has not paired before ...don't works !

nadenislamarre

@superMDMArio @luizthiago can you try to connect via ssh
then
bluetoothctl
scan on
devices
info xx:xx:xx... where xx:xx:xx if your device
check if that's paired, connected, trusted.
you can then
trust xx:xx:xx
pair xx:xx:xx
info xx:xx:xx
and see if that may help.
i don't think it will help, but it can help us to found.
something changed in the last versions however, but i can't say exactly what (maybe really the bluez version)
before 5.? my ps3 pad were automatically trusted.
in the last versions, it didn't occured. thus, i made a patch to trust it automatically (when you plug the usb)
maybe it's something near that.

luizthiago

nadenislamarre in 5.14 my pad is paired trusted with bluez driver and All is ok even in DreamCast! But in 5.15 or newer The pad not paired (in clean install) or New pads in The same type...