would you be able to provide the info in the following: https://retropie.org.uk/forum/topic/3/read-this-first

I think some of it is in your first post, but I'm wondering what emulator is being used for N64 in particular.

lr-Mupen64plus uses retroarch configs and should work okay, but it isn't particularly the default emulator

Mupen64plus used it's own configs. It is supposed to do an auto-config, but that doesn't always work. You can go into the configs and set it manually.

I tend to use lr-Mupen64plus on systems that don't auto-config right, though it may not necessarily be the best performance. N64 is buggy enough that the extra performance difference isn't worth it to me.

@obsidianspider hmm i would guess that it's in the .cfg file, which would be
/home/pi/RetroPie/roms/mame-libretro/mame2003/cfg/gamename.cfg
or
/home/pi/RetroPie/roms/arcade/mame2003/cfg/gamename.cfg
depending on where your rom is.

@PetroRie I'd give it a go. I'm actually complaining about how it is explained to people by the experts not those asking the questions or having issues.

@adri76 No worries. I would recommend changing your password from the default though.

@BuZz I have searched for ages to find an answer but i cannot , I am as new as it gets to this, i shall now put in the relevant information asked for

@columboscoat thank you for your suggestion.

@dudleydes said in Mapping Numeric Keypad to Analog Stick:

Bioforge uses the Ctrl and Alt keys with the numpad for hand and feet combat so using modifiers is going to result in some serious finger contortion!

On all the keypad-based systems I've mapped this way, most just use keypad input for menu options such as player and difficulty selection, which can be casually selected. However, I can definitely see why mapping a game like 'Bioforge' this way wouldn't be any fun. Intellivision games often make the keypad an integral part of the core control scheme as well and I sometimes find myself doing mental and finger gymnastics in order to simply move a character from left to right. I end up having to tailor map a custom control scheme if I want to play the game any further.

Anyway, I'm glad you found an option that works for you. It does seem to be the best solution.

@darkav check this out :)
https://retropie.org.uk/forum/topic/7190/mame-savestates-not-working-in-retroarch/7

it might be that lr-imame4all doesn't support save states at all - that's normal.

@Gaccus
Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Specifically RetroPie Version Used (3.6, 3.8.1, 4.01 etc.. - do not write latest)

Thanks, will have a read through those later, I just assumed NeoGeo and MAME were separate things.

Hi again,
Sorry about that, after entering amixer -i the output is amixer: Mixer default error: No such file or directory and entering amixer -l just gave the above error when I thought you said amixer -1,

And would you have any idea about how I would even read the boot/config.txt file

Thanks

@slydisciple glad you got it working.

@batesman so i tested and it doesnt work any different as i thought. Sorry to waste your time. However this is good stuff to use because you can manipulate both analogs and the dpad to do whatever you want. With this method for using the analog stick as a dpad you could program the dpad to a whole new set of buttons that arent even related to direction like how first person shooters and other games are these days.

Thank you. I got it updated and it worked after an ES restart.

Yeah, I'm not sure what to do at this point. I've completely deleted the emulator and any files associated with it and reinstalled it, and I still get the same issue. I've tried changing the number of devices it's looking for in reicast.sh, I've checked and double checked the controller configs for both my PS3 and Xbox controllers to make sure they were set and named correctly and pointed at from emu.cfg. I've deleted my configs and reconfigured each controller at least twice to make sure that wasn't the issue. Verified both bios files and redownloaded again for good measure. Downloaded a gdi version of the same game just to see if cdi was the issue. I'm out of ideas on what to try next.