@mitu I have attempted that but you dont have to wait to when using the up down left right arrows, i have tested this and it works before the time runs out

Maybe a config override for that core?

@Riverstorm

I agree with what you are saying.

However, Guarantee = safety factor in engineering. If I want to burn my Pi in 2 years instead of 20 and I want to approach S.F. to 1.0 by iteration because I want more from my machine, I do not see where the problem is. I saw a difference in the performance, that's the problem.

I think It's not a bad thing to explore It with knowingly and knowing the impacts.

Everyone has their opinion on the matter and that's fine like this.

@mitu said in MAMEdev MAME Installation Script Broken:

Then it might be something with the latest update. I tried to test the libretro builbot version, but for some reason, the armv7-neon-hf build for the lr-mame core is build for aarch64 and it can't be used on RetroPie.

The issue is being looked at upstream - https://github.com/libretro/mame/issues/163

@Brandon12345678 Ok I got it working. Using only one font helped. Thanks for the help.

Use the core input remapping feature - https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping.

I am not familiar in any way with NDS emulation, sorry. I can work on a Pi on Tuesday to see where you can locate the config files. Do you have a SSH server running on your Pi?

@Unknown It will not disable them, the emulator can read both zip and 7z compressed files. If you have scraped the games already you could run into a problem with emulationstation looking for whatever-your-game-is-named.ngp instead of whatever-your-game-is-named.zip (or .7z) which can be solved by rescraping or editing the gamelist.xml for neo geo pocket.

[edit: realized I worded the first sentence very poorly...]

@Muteki correct. These files are mostly copyrighted (there's a few cases where vendors have permitted distribution), so we can't install them automatically.

Some systems run without. Eg. Zx spectrum, as the bios is included due to being permitted by the copyright holder (in this case Amstrad). Or because they use a replacement copyright free bios. Eg. There is one for the Amiga for example.

@quicksilver thank you so much, that's all I needed to know

@mitu said in N64 emulator doesn't save any settings:

you need to save a game or core override after you've changed the parameters

Can you please tell me where I can find the Overrides-menu? Or which solution would be the best?
When I switch the "Use Global Core Options File" to OFF, then I still the the same problem.

@mitu thanks for your help. The amendments to the CFG file worked.

@norbit911 Why do it backwards ? You can start the Desktop from EmulationStation, so leave EmulationStation running by default. If you wish to run the desktop also when exiting EmulationStation, modify the autostart.sh file and run the desktop startup command after the emulationstation line.

@Clyde That’s fine, I just needed to know there is hope to play it. I remember when it was first emulated and I had to buy a top of the line computer to play it. Stun Runner was always my baseline to know how fast a computer was. My multi build is more based around Star Wars games so Stun Runner will actually be a nice bonus if it works. Thanks again!

@BuZz thank you. I'm really sorry I thought this was a newer release,

@Spark Ask the author of said image, we don't support 3rd party images.

Vagrant Story has a bug with lr-pcsx_rearmed in that the game won't recognize its own save file checksums sometimes and it won't let you save the contents of your Container, losing anything you have put into it. You can still save your game progress though. I recommend Save States, but sometimes it will crash when you go to save state...

@BuZz https://retropie.org.uk/forum/topic/27043/libpng-dev-not-installed-x86

Plug your controller setup in your Pi without any other controller except the keyboard, boot it up, close ES and run this

ls /dev/input/

It should show all input devices of which joysticks/joypads are shown as jsX (eg. js0, js1, ...).

If it is not present, try to look if the USB device is present with

lsusb

If a controller is present and you want to test if the device translates the PS2 buttons correctly, run this and test

jstest /dev/input/jsX