@mediamogul "first young grasshopper, you must press B to jump."

Hi

I've achieved the same result by opening the RetroArch menu in lr emulators.

I can do this by pressing SELECT and X at the same time (using RetroPie's default buttons). I press the same combination to exit the menu and continue.

Simon

@caver01 said in Configuring <CODE_NOT> Control Mapping in lr-MAME2003?:

@dankcushions I can appreciate that, but it seems lr-mame2010 has it figured out. Maybe apples and oranges, but the double keys aren't showing up there.

i think 2010 gets around it by making mame think a connected gamepad is a keyboard, so it never actually detects gamepads as gamepads, but as the virtual keyboard (i think in the tab menu it will always show up as "Kbd PX...". player 2 SHOULD work (the code is there.. possibly bugged), but player 3 and up won't work i believe, because it only maps 2 virtual keyboards. so this isn't a good solution, but a hack that happens to help in this specific situation.

that's my theory from the code, but i can't test it because i can't connect pads to my mac and can't be bothered to compile it on the pi :)

interestingly, i just found out that mame2010 runs killer instinct 2... at least on my mac.

Hi,

I have not had the issue with the controller yet but I would take a look at your dreamcast's keymappings.

are they not showing up in the directory itself or just not in emulationstation?

@simonster that was it thanks!!

@zakhounet

Short overview here:

@Mantas https://github.com/retropie/retropie-setup/wiki/runcommand#configuring-runcommand :)

How was it connected to the TV? I take it it was through HDMI?
How was it connected to the monitor? HDMI as well?

Except for some rare overscan issues HDMI is usually plug and play.

Yes I am, that is why the MS DOS ones are saving

@herb_fargus Thanks I didn't read the instructions clearly the first time I got it working.

@dannyboyswe

https://retropie.org.uk/forum/topic/3/read-this-first

https://retropie.org.uk/forum/topic/1673/lr-pcsx-rearmed-runcommand-sh-line-804-5728-segmentation-fault-since-3-8/19

@Riverstorm

Sorry, your post got by me somehow. That is very helpful information it's great to have it documented here. I've found that a few of these type quirks regarding specific js numbers are indeed configurable, but in the case ScummVM, the method has escaped me until your post. Since my last comments here, I've taken to mapping a virtual mouse to my controller's left analog thumbstick and have found that it operates more smoothly than if ScummVM tries to utilize the joystick itself. I've also since keymapped my controller with ColecoVision & Intellivision in mind and put the same technique to good use in working around the event order issue with Daphne. In doing so, I can even invert the controls if necessary, which is another known limitation with Daphne's native joystick support.

Please report any bugs with nodebb here - https://github.com/NodeBB/NodeBB - we are using the "Persona" theme and the default composer. Composer bugs can go to https://github.com/NodeBB/nodebb-plugin-composer-default - we are running nodeBB 1.0.3 currently.

Thanks a lot,
it worked!
I did search in wiki and a lot of other forum, trying to change a lot of things. did't type the right keywords I guess. Anyway, tahnk you!

This morning i managed to find a full-set roms for the mame's version that i'm using; and now most part of the roms works properly.
Thank you all for helping.

@Finndersen

Using HDMI detection as a trigger is a keen idea.

Well actually it's more of a combo of buttons. With my configuration above, if I want to do a Save State I have to hold the "hotkey" which is the Select button and then the "save state" button which is the B button. Then to load the save state I hit both Select + X and to exit the emulator i hit both Select + Start.

Also just to clarify, the "#" tells the emulator to ignore all text after it until there is a carriage return (or new line). I use it to put comments in my configuration files so I can easily decipher it later on haha.

Lastly, with that Adafruit display, you might have to manually set the resolution. I've never messed with that but maybe this thread will help:
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=130564