[Floob]

Thats right, MAME emulation does not use RetroArch in RetroPie 2.3

You can see how to set an exit button combination here:

[Floob]

You could try rebuilding it, then without updating the retropie script run the controller config.

[Floob]

Maybe just paste the contents here

[Floob]

Many MAME games are variants of the parent rom. Hence you may need multiple roms to run one version of the game.

For example, this game: http://www.mamedb.com/game/fireshrkd
needs a parent rom of fireshrk.zip

To be safe, if you install the full romset it should work.
A popular (good compatibility with mame4all-pi) romset version is 0.37b5

[Floob]

Does this help?
http://www.pimame.org/forum/discussion/728/pifba-arcade-stick-leftrighupdown-axis-how-change/p1

[Floob]

You can see the filetypes set in
/etc/emulationstation/es_systems.cfg

Yes, MAME roms should be .zip (romset 0.37b5 works well)

[Floob]

Great. Can you post (as an attachment, not inline) the Xbox360WirelessReceiver.cfg file.
You will probably need to rename that as a .txt file to post it here.

That should show why your hotkeys arent behaving.

Also, what value does this have (input_enable_hotkey) in your retroarch.cfg file
in /opt/retropie/configs/all/

[Floob]

What happens when you set the video value to ‘1’ in es_systems.cfg?

There is some info here:

[Floob]

Buzz: It does use it, as thats where you can use settings like border etc.. to sort out overscan with MAME.

patrick500: The mame.cfg file in there isnt for the in game controls, they are in the cfg directory, but I dont think these are editable with a text editor. You need to use the in game menu using TAB to alter these.

Some basic details here:

[Floob]

The default behaviour is for the one in the “all” directory to get loaded first, it then imports the autoconfig controller file, and that is likely to overwrite or at best conflict with the “all” file – so you dont really want anything duplicated in that. You can of course not use the autoconfig files if you dont want.

Then lastly the system specific file gets imported which would overwrite anything in the previous two.

[Floob]

Presumably you have these lines set:

input_shader_next_btn = “?”
input_shader_prev_btn = “?”

Check for them in your autoload files:
/opt/retropie/emulators/RetroArch/configs/

and your main retroarch file:
/opt/retropie/configs/all/retroarch.cfg

and your system specific files:
/opt/retropie/configs/{systemname}/retroarch.cfg

[Floob]

You could use this process to create the autoconfig files and see how the system names them each time:

I should really try a few controllers and see what the exact behavior is – especially when the controllers are the same.

[Floob]

Hi,

You can see the exact fiel size of the neogeo.zip in the video – the romset there works fine for me in the RetroPie 2.3 binaries of fba for the pi.

[Floob]

Potentially overthinking. RetroArch will auto detect controllers based on the files in this directory:

/opt/retropie/emulators/RetroArch/configs

you could amend those files to specify which is which player I guess.
I only have two (and they are different) so no real issue.

[Floob]

I’d get a retrolink USB cable. Good retro feel and less hassle to setup.
Most USB based joypads are good.

[Floob]

Does this help you?

[Floob]

If you get a black screen when exiting ES, you can hold Alt-F2 to get a separate display up, then ALT-F1 to flip back to the original that should then show a display.

[Floob]

Can you show the results of ls -lah in your autoconfig directory?
/opt/retropie/emulators/RetroArch/configs

I’m presuming you havent manually updated your main retroarch.cfg file?

[Floob]

Yes, you can remove roms by deleting them from your folders with an SFTP tool like Filezilla. Or you could remove their reference from a gamelist.xml file if you have one?

Check this directory for what controller details are being loaded at runtime
/opt/retropie/emulators/RetroArch/configs
Do ls -lah to see which files have been updated recently.

[Floob]

Hi,

There are some videos in the link in my signature that cover setting hotkeys to exit the emulator, overscan and configuring retroarch controllers. They should help as a first step.

The hotkey for joypad to exit is
input_exit_emulator_btn = “{your joypad code}”

[Floob]

To be honest, thats a hell of a retroach.cfg file. I’d be sorely tempted to clean it up/start again.
A cleaner version can be seen here:
https://www.petrockblock.com/wp-content/uploads/2014/12/retroarch.txt

If you restart the image, you could auto detect your controllers again in a cleaner way?

[Floob]

Edit the main retroarch.cfg for hotkeys.

Its at
/opt/retropie/configs/all/retroarch.cfg

[Floob]

When you run mame, it uses tab to bring up the main menu.

[Floob]

Are both controllers detected when you start a game (yellow writing at bottom of screen when it starts).
If you are using the autoconfig files for the controllers, they are in
/opt/retropie/emulators/RetroArch/configs

Just do ls -lah to see which have been written to recently.

This may help:

[Floob]

If you still have issues you could force the slot it should load with this in the relevant retroarch.cfg file

state_slot = “0”

[Floob]

I’m presuming you dont have any state related config file in your /opt/retropie/configs/{systemname}/retroarch.cfg files that may be overwriting your main file?

To use F6 / F7 – hold the hotkey down as you do it.
Also, your cfg says you are autoloading the controller config, but then you specify it at the bottom of your script, I would do one or the other.

You can also get the GUI to try the options if you press F1 (with hotkey)

Yes, the # is a comment, but the value shown is a default so it will still work.

[Floob]

The F1 button on the keyboard should bring that up.

Or you can map it to your joystick with hotkeys.
See the end of this video for hotkeys.

[Floob]

This should help you get up and running:

Watch out for this though:

Error with RetroPie Setup scripts

[Floob]

I think you can get most stuff on 16GB, but 32GB would be ample. I guess if you wanted every rom under the sun you could get bigger but I really dont think you need it.

The big ones are usually mame/neo geo related.

[Floob]

Try this video, and check the link in its description:

Your issue may relate to this line:
overscan_scale=1

[Floob]

Can you see the file in the directory when you do ls -lah ?

If so when you type sudo nano – if you then type an X then ‘tab’ it should autocomplete the filename – that will ensure it is spelt exactly.

[Floob]

The mame file is:
/opt/retropie/emulators/mame4all-pi/mame.cfg

You can see the ascii key setup in there.
For example, escape is ’27’
http://www.theasciicode.com.ar/ascii-control-characters/escape-ascii-code-27.html

Game specific and the default ingame controls are here:
/opt/retropie/emulators/mame4all-pi/cfg/ (although you cant edit these with a text editor)

[Floob]

This thread may help.

Error with RetroPie Setup scripts

If not, please post the steps you take and the error you get.

[Floob]

Can you do a ls -lah command in the /home/pi/RetroPie/savestate diretcory?
Just to make sure the permissions are ok – can you paste the output here?

What about if you reset those lines to

# Save all save files (*.srm) to this directory. This includes related files like .bsv, .rtc, .psrm, etc ...
# This will be overridden by explicit command line options.
# savefile_directory =

# Save all save states (*.state) to this directory.
# This will be overridden by explicit command line options.
# savestate_directory =

Can you save and load then?

Although, looking at it, it seems to be trying to load a state file that isnt there – i.e. with a ‘1’ at the end.
So it maybe related to this

# State slots. With slot set to 0, save state name is *.state (or whatever defined on commandline).
# When slot is != 0, path will be $path%d, where %d is slot number.
# input_state_slot_increase = f7
# input_state_slot_decrease = f6

Try pressing f6, to set the slot back to ‘0’ if you see what I mean.

[Floob]

Check out the videos in my signature below for some help.

You could put the relevant keys into the main retroarch.cfg in this section to specify which player

# Joypad buttons.
# Figure these out by using RetroArch-Phoenix or retroarch-joyconfig.
# You can use joypad hats with hnxx, where n is the hat, and xx is a string representing direction. 
# E.g. "h0up"
# input_player1_a_btn =
# input_player1_b_btn =
# input_player1_y_btn =
# input_player1_x_btn =
# input_player1_start_btn =
# input_player1_select_btn =
# input_player1_l_btn =
# input_player1_r_btn =
# input_player1_left_btn =
# input_player1_right_btn =
# input_player1_up_btn =
# input_player1_down_btn =
# input_player1_l2_btn =
# input_player1_r2_btn =
# input_player1_l3_btn =
# input_player1_r3_btn =

[Author]

Posts