I've been looking into the controls thing more, and lots of issues here i'm afraid to say... but i guess this is all still work in progress? Some of this might need resolving further 'upstream' ... i dont know, i just hope it helps.
I am using a PS3 pad on uae4arm. In all examples i am setting 'port 1' as the most common option.
- with 'dpad as joy' or 'dpad as cd32' , i get no results.... no fire / no movement.
- if i select 'sony ps3 controller' ....
-- Analogue only works as directional controls (nothing on the d-pad)
-- I cannot set joystick or cd32 options for the PS3 pad without using 'custom' setting.
-- using custom setting, i am missing the option of adding anything to the PS3 start/select buttons. This creates an issue for CD32 pad mapping, as it is lacking a input button (i.e. having only 6 to choose, where my controller has 9 available and the CD32 has 7 to map)
-- the cd32 options , when set on 'custom' do not appear to work, no response on testing so far.
-- there is no 'cd32 red' 'cd32 blue' or 'cd32 play' available in the custom drop downs.... please note that red/joy fire 1 and blue/joy fire 2 are *not* the same input. Although they often operate the same, the code to read the (amiga side) differs, and this does cause 'fire' not to work in some games where 'red' does.
(there is common CD32 WHDLoad asm reading code that has this difference)
If it helps, i have a small program for testing cd32 inputs:
https://drive.google.com/open?id=0B4272 ... 0xhRVJ2bXc
This was needed for resolving similar issues on PSPUAE development, some years ago.
I confess the 0.4 input system wasnt too bad, i could probably have coped with just adding the CD32 buttons to the custom list, and the addition of the extra host inputs being mapped!
Any progress getting these fixed, very much appreciated.