I got the Ultimarc BlueHID working after a fresh reinstall of the latest RetroPie 4.4. Which is great news, I can highly recommend this controller board with RetroPie!

http://www.u-hid.com/home/overview_bboard.php

mame2003-plus has a new input mode specifically for this purpose.

It is activated via a core option which allows the core to process input through the either mame_keyboard interface or the retropad -- or both simultaneously as with classic mame2003 (although that is not as useful as you are finding out).

i'm afraid I cant find much on how to output to this from python. Im no coder, it needs to be call-able from python once Ive done with my process.

thanks for info!.. do you have any more?

Other options please! what other options do I have to get my character input into ES and retroarch please?

@markwkidd Thank you for the help/replies, it is appreciated.

@mitu okay, cool I'll give that a shot. Cheers.

@mitu Thank you, I will definitely look into this and test it out this weekend.

I apologize for not replying sooner, I have not been getting site notifications for some odd reason.

I should have said, the iGo is a bluetooth keyboard. Sorry, I forgot to mention it in my earlier post.

@johnny5126 I don't think so, how would the system choose which action you intend to perform when you press the key ? If the key acts as a toggle (run/stop), then it might work, but otherwise I don't think it's possible.

odd.
this time when i removed the controller, and restarted emulation station, it let me configure my keyboard. I plugged in the controller, and yep, both the controller and keyboard work. I went back and checked the config file you posted, and now there are two entries, one for the controller and one for keyboard.

thanks for the help mogul.
goes back to figuring the best dosbox settings to get blood to run at a decent resolution

-Pete

Hi,

Could you not read your SD card on a PC running Linux, or with a bit of software on Windows to allow you to read the microSD card, and get your ROM files that way; at least that would save you some work?

Although the horse has bolted, so to speak, if you're going to upgrade anything, always do a backup first. It is so much work to lose if you've built your own image from scratch.

All the best.

@buzz I know it works via the wifikey file, but in this case there was no controller or keyboard working and I was referring to the next section (Connecting to Wifi Without a Keyboard (Raspbian Stretch)) where it's possible to configure wifi directly via the wpa_supplicant.conffile on the /boot partition

@spud11 said in Mapping a keypress to a joystick (Fuse/others):

My runcommand-onstart file is now 113Kb in size, but I've found it has to be devoted purely to xboxdrv and case $2. If I try to add anything else to it with more general application like trying to invoke a bash script unrelated to xboxdrv, runcommand-onstart just doesn't work.

I run 26 systems that make use of xboxdrv, sometimes having several dozen exceptions made for individual games. I've managed to keep the size of my runcommand-onstart.sh down to 39.9k by offloading the execution of xboxdrv itself to separate scripts. All the if/then stuff is still there, but once the conditions are met, it launches an outside script with the xboxdrv command. That may help to alleviate your situation.

@markwkidd Word received 😀. Great work as always 😎

Guys, give a try to the lr-scummvm libretro-based core for ScummVM I put for testing here: https://retropie.org.uk/forum/topic/19693/lr-scummvm-request-for-comments-and-testing/

You can do mappings via RetroArch and customise for each game too easily with RA. Also you can use any RA-supported shader. So far it has been working nice for me, would appreciate feedback from other ScummVM players.

@caver01 Well it was a lucky coincidence that I did the migration shortly after I read this thread. I wouldn't have done that only out of curiosity. :)

Ok, thanks for your answer. Then I have to use my old PS3 Controller

@RetroFreak - This may help .

• Go to "Machine Settings" and then "Joystick Settings".
• Then go to "Map Joystick", this screen will show you the mappings for two joysticks. Navigate to the "up" mapping, select it and then press "up" on the joystick. Repeat this step for all the other mappings, and for both joysticks if you have a two players connected.
• Now go to "Joystick Settings" and "Joystick Device 1" and set this as "Jyostick", you can also set "Joystick Device 2" as "Joystick" if you have two players.
• Next go to "Machine Settings" and "Joyport Settings". Choose "Control Port 1" and select "Joystick, do the same for "Control Port 2".
• Now exit the gui and the joystick should now work.
• However, C64 games are sometimes played from Joystick port 1 or 2, this may mean the joystick will not work. The way to remedy this is to re-enter the gui, navigate to "Machine Settings" and then "Joystick Settings". There will be an option to "Swap Joystick Ports" press enter and then exit out of the gui. The joystick should now work. You can also map the "Swap Joystick Ports" to a hotkey (see below).
• Now these keys have been set they need to saved so that VICE will use these mappings next time it is started. To do enter the gui and choose "Settings Management", then choose "Save Current Settings" and "Save Joystick Map" then exit out of the gui.