@mitu ok right it finally works. I found the CTRL and F1buttonns and configure the keymap

It works on everythink except on the number pad.. i think there is a problem with the NUM bouton. I see that the NUM led dont light when i push it.. i test on another key and its the same... my configuration configures the page up bouton and not the 8 bouton i think

The same problme appears with CAPS bouton, does raspberry support the changing of CAPS and NUM
it ligh on my computer but not in the raspberry

@harrycool25 We don't support 3rd party images - why don't you ask your friend ?

Probably you'll have to play with the Overscan settings to see if you can remove the borders.

@hermit Looks like if you launch and exit the pixel desktop it fixes the issue. I'll try to find another workaround.

@tuki_cat said in lr-fuse and saving configurations for each rom:

rk but have had no success - how do you save configs per rom in lr-fuse? I essentially want to save the configuration so that it uses the 48k spectrum for certain games and 128k for others.
I have seen this link, but this doesn't work for me - https://retropie.org.uk/forum/topic/5409/jetpac-on-zx-spectrum
I have tried running a rom and the tried selecting the "save game overrides" in the RGUI I get a meesage that tells the file has been saved, but the configuration does not work and I can'f find where it has saved the .cfg

Main Menu > Quick Menu > Options > [change keyboard controls there] > [click on the top "Game-options file.... [name of game]... Took me ages to work that out.

@mitu If retroarch is looking for and the bios, which folder? As if there is a folder it is searching at all it could be worth to drop it into that folder. I reinstalled and nothing.

@mitu Thanks for the reply,

Unfortunately this is not the information I was wanting. This information is good IF your using packages within Retropie but not external emulators away from Retropie. It doesn't explain why it would load an emulator but not dump the rom on load up.

sorry I am new to the fine detail on simple codes. Thanks for the help

@webodan I don't think ES reads the list of Audio cards present in the system - the choices you see now are the default choices.
Try using the instruction from the USB Audio FAQ page.

@iyonuk Genius ✅

none of the above. I think? I might have changed some settings that were suggested in the github article about reducing input lag, but AFAIK I only did that in the NES core

Please provide more information about your setup/system as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

@riverstorm Thanks for a very comprehensive and helpful reply.

@mitu thanks mitu will do

@crumbs said in Neo Geo setup and installation:

The guy asked the question a number of times and no one answered it directly or adequately

We answered adequately, you didn't, you just told "pick random roms and perhaps they'll work with one of the emulator", which is the worst way to do that, and against what retropie documentation recommend.

@crumbs said in Neo Geo setup and installation:

I have consulted the documentation plenty of times. The links do tend to go round in circles or take you off track to tell the truth.

Documentation is crystal clear about this : select an emulator then pick the right romset for it. You do exactly the reverse, you recommend doing the reverse to other people, and you say you consulted the documentation ?

Honestly i couldn't care less how you do things, but the fact you are trying to mislead other people is a cause of concern, because that kind of post lead to more topic like this one. There is no need for trial and error, you can directly pick the right romset which is faster, easy, and the rightful way to do this.

Thank you for the fast answers.

Now I understand. I didn't understand that the m3u-Option is a separate method to pbp.

OK. Then i can go back to work :-D

Thx

@kdragon_2 RetroPie is just Raspbian Linux underneath, so as long as your setup works with Raspbian and the OS detects your setup as a controller, RetroPie should recognise it and use it. As for the how to communicate with it, that's up to you - Linux/RetroPie already includes a few drivers that interpret GPIO inputs as a controller - look in the Docs.

I have an old model IPAC4 that I used back in 2008 running Win98, XP, etc. and I eventually rebuilt my system around the PI (you can see details linked in my profile or signature below). Anyway, my IPAC has the PS2 connector but works with a USB adapter cable.

Here is the thing--the IPAC is a keyboard. Or at least it looks like one to the computer to which it is connected. Your joysticks, assuming they are microswitch-based, could be pushbuttons. There is nothing about the fact that it is a stick vs. a button--it is simply shorting the input on the IPAC to ground.

So, what happens if you wired a joystick to BUTTON1,2,3,4 on the IPAC? I would think this would let you trigger those buttons when you move the stick to short the respective inputs. If true, you should conversely be able to wire a button to one of the joystick inputs and pressing the button should trigger that key. And this brings me to my point. . . Do you know what keyboard keys are getting sent by each directional trigger? How are you testing on the Pi? Are you opening a text file in Pixel for example? My player 1 joystick maps to the arrow keys I think. So, if I open a text fine on the Pi, I can move the cursor around just like I am typing arrow keys.

I know I am not offering an answer but more of a testing method. Mapping keys can get really confusing once you launch an emulator, so my approach is to verify the raw inputs are getting out of the IPAC and into the Pi.

One approach to testing keyboard inputs is to launch the keyboard testing executable from AdvanceMAME at commandline. This will let you watch on screen what the PI is receiving when you pound on buttons or move your sticks. I don't remember the test command off-hand, but if you dig into the Docs here on the RetroPie and look for the Spinners/Trackball page, there is a similar test you can run for Mouse input. I know, we are not testing a mouse, but there are three executables in there for AdvanceMAME that let you test each Mouse, Joy and keyboard inputs. Might be worth a little time looking that up. Sorry , don't have my Pi handy to check.

My thought is that once you know the inputs are getting sent, you are no longer troubleshooting the IPAC, but rather the mapping. Knowing that much can go a long way to figuring out the next step.