@mohrad I think you 'll need to do it cause the vanilla driver is wrongly recognizing any touches in the first place. Also the install does not work for me, maybe because i created the steambuild folder in the wrong directory
@mitu Ah I see! That makes a lot of sense. I've got it now thanks! Just need to figure out what buttons I've got and it's all dandy. Although I guess I also need to map some of them so I can still exit retroarch.
And thanks again, I succesfully mapped the 1 to F1, 2 to F3 and 5 to F5. Although it required some steps.
First I mapped (as you told above) with the virtual keyboard the correct keys, and then saved it. After restarting the Vice emulator the keys weren't mapped anymore. When I loaded the keymap again the keys still didn't work. Then I thought maybe I can add the changed keys in the dsl-vicerc file (a bit like the F12 file) but then more like this "49 0 4 9" which is 1 to F1. That didn't work but I noticed that it would load the keymap according thje dsl-vicerc file, but somehow that didn't work.
Looking in the vice.log file I noticed that it says: Loading keymap `/opt/retropie/emulators/vice/lib/vice/C64/sdl_sym.vkm'
Now I wen to that file changed it according to the saved keymap and it works. Strange thing is that is doesn't look at the keymap it should load.
And what I did for the Dosbox is create .sh file. Not sure if it works for C64 but you can try this e.g:
@sadkiwi Just some tips, if your question involves something that isn't working, explain it as accuratly as you can, and explain how it is connected/related to the pi. Also sometimes add the code you are using for some projects.
@SlowSL MAME GUI seems to generate additve "OR" keymaps while you remain on that line for input. If I want to remap a control, I simply move up or down to the next one, then back to the one I want to edit and remap. This always replaces what is there starting with a fresh mapping. If you just keep pressing ENTER on the same line they combine (as you noticed).
Sometimes, I will combine stuff intentionally. For example, I might combine coin drops when playing from the vertical ends of my cabinet (3-sided cocktail design). I might also map multiple action buttons for a game to give the player the option to hit one button or another button for the same function.
Understanding the "null" mapping in per-rom .cfg files is also really useful, as it blocks the retropad mapping and allows just the raw key inputs to reach the MAME GUI. This is necessary if you want to do complex boolean mapping (with "NOT" settings for example to setup a tankstick).
If I'd known from the start that this thing pretended it was an Apple keyboard this would have taken a lot less time.
I guess the Fn key on the i8 works differently than on a real Apple wireless kbd, hence why holding the Fn key and pressing the F1-F10 doesn't generate the correct keycodes, but reversing the Fn switch with the driver parameter does.
I can now F4 out of ES and F12 to bring up Amiberry config, etc. Yay.
(I just now realised that taking a screenshot on an iPhone is the power button and home buttons together, which explains Fn+F5).
Same problem with new installation.
I have a GamePI20 and can't use it with 4.7.x version (driver/module not support the Kernel version). I use the 4.6 instead. All working great, the GPIO controller work fine in emulator and ES, but under dos-like menu (Raspbian, emu config, packages updates, etc..) only the Pad key Up don't made the right action (tab over bottom buttons). Is do not happen on SNES clone USB controller.
@mrvanes , I follow the request of @Melvin-FoX , you have updated, ok, but what are updated ? Kernel ? Setup-script ? I don't want OS upgrade, because if the kernel is updated, the GamePI20 stop working (no LCD, no pad). But if you have updated all, I guest you don't know the lib or other thing that fix exactly .