@raspberry79
could you please be more specific when opening threads?
What games are you running?
Which Emulator are you using?
What for a screen are you using?
What did you change allready? The stock-image does not produce tiny screens, there seems to be something changed.

@TonyXL When I do this I get a message that says, “error saving controller profile”

@raspberry79 I know I shouldn’t be responding because everyone else has answered you, but I feel need to simplify cause you seem lost.
A file extension, be it a .bin, .iso, .zip, .whatever does not tell you what emulator to use. You have to know what system the game you have is for and put that file(s) into the proper rom folder. That’s it
If you don’t know what systems it is for, we don’t know.

@psun03 which system? Is it one of the supported platforms?

https://github.com/muldjord/skyscraper/blob/master/docs/PLATFORMS.md

@mitu Not really, I just translated the basic things in the menu. I made those translations for my dad so he can understand what are those things in the menu. I am the one who adds roms, configures the system etc. so I don't really need a full system translation. Anyway, thanks for your help guys. <3

You can rename the configuration file (amiberry.conf, in /opt/retropie/configs/amiga/amiberry/conf) and start again the emulator.

@Thorr69 OK good to know. I'm just surprised because when I select amiberry 500 via runcommand, I get "Unknown command FAILAT" with every game. And if I use Amiberry 1200 most of the games are working, that I tried yet. Do you know what this error message means?

@mitu Is the Retroarch version the number shown in the bottom left corner of RGUI, along with the currently loaded core? If so, mine is on 1.8.8 somehow. If not, where can I check my current RA version?

Yeah, so I now updated to RA version 1.10 (d'oh) and I can see the menu entries in the aforementioned places.

Setting turbo mode to single button (hold) and turbo default button to X (my preferred button) still doesn't make it work as I intend. For instance, 1944 still charges up a shot when holding down the button instead of rapid firing. single button (toggle) does work as I would expect it to, though.

What am I doing wrong?

EDIT: Okay, got it. After updating RA, if I put

input_turbo_period = "6" input_duty_cycle = "3" input_turbo_mode = "2" input_turbo_default_button = "0" input_player1_turbo_btn = "3"

into my cfg file, button 3 does function as a turbo button, WITHOUT modulating any other buttons, so I guess the previously linked post was correct after all, I was just rocking an older version and didn't realize it.

Thanks to all respondents for bearing with me!

@Folly 😆

I don't have much experience with AdvanceMAME either, but what I'm reading indicates that its lightgun controls function as emulated joysticks and/or are Windows only. A quick test with the border applied via artwork gives an inaccurate cursor with bad sensitivity. The performance loss is a hurdle that seems to make further testing pointless.

A careful application of the RetroArch lightgun API doesn't require any sensitivity adjustments by the user. As long as the coordinates are scaled properly by the emulator, where you point the gun is where the cursor goes.

@mitu It seems to work fine now, but if it starts to mess up again I'll let you know, thank you.

Thanks, I will try this, but I doubt this will help. Raspberry PI OS and Emulation Station recognise the display correctly as they feed it with 1280x800 automaticaly. RetroArch seems to miss this information or ignores it.

Edit: With hdmi_ignore_edid=0xa5000080, resolution in raspi-config = 1280x800 and no resolution set in RetroArch everything works fine. I still do not realy get why, but thanks a lot @mitu!

@NIGHTKILLER05 I'm not at my device right now to test it but I think quoting the actual "${0%.*}" should do it. You'll need to use "double-quotes", since 'single-quotes' prevent ${variable_expansion}. Since it's inside the (parentheses), I think it's okay to have the quotes inside the other quotes and you shouldn't have to \"escape them\". Try:

ln -sf "/home/pi/.emulationstation/downloaded_media/ports/screenshots/$(basename "${0%.*}").png" /opt/retropie/configs/ports/doom/launching.png

@10vorne If you are using lr-fuse, there is some useful info here:
https://retropie.org.uk/docs/ZX-Spectrum/#controls

I use that to set the gamepad to act as a Kempston joystick then choose that in the game. So thats just editing the spectrum retroarch file in /opt/retropie/configs/zxspectrum/retroarch.cfg

For what its worth, here are some notes I scribbled some years ago

input_libretro_device_p1 = "513"
input_libretro_device_p2 = "0"
input_libretro_device_p3 = "259"
input_libretro_device_p4 = "1"
input_libretro_device_p5 = "1"

This sets the first player to Kempston and player 3 to keyboard

To choose controls when starting a game, press select to bring up the keyboard overlay
some games may need core option set per game to force 48k model for compatibility (like dizzy)

@mitu Ok i will try that and get back if I face the same problems. This is what I will do, I will install a debian 32 bit(somehow my tablet only support 32 bit uefi and can only detect 32 bit bootable linux distros). Then I just install retropi again through RetroPie-Setup.

@barbudreadmon I had no idea! This particular emulator never hit my radar. Going to have to try it more often. Thanks so much.

from a cursory google search Kore seems to be a remote control app for kodi. I don't think it is supposed to show you any video - you just use it to act as a remote control for your kodi device (which in this case is the pi, showing video on the attached screen).

in any case, this seems to be a kore support issue, not a retropie one. kore isn't part of retropie.

@smelly fyi setting overscan settings without overscan_scale=1 will not apply them to emulationstation - see https://retropie.org.uk/docs/Overscan/#the-console-looks-good-but-the-picture-is-off-for-emulationstationretroarchetc (and also see further up this page for other/better ways of solving overscan issues)

@raspberry79
from your link:

To do this type sudo apt update

this is essentially exactly what retropie's scripts do when you update underlying OS. retropie is effectively a bunch of scripts that automate the running of terminal commands, so you shouldn't need to manually do them too often :)