@Thorr69 Thank you for your help. I just had a chance today to sit down and work on it. I got it working. Thanks again

Oops just found it (here: opt/retropie/configs/all/emulators.cfg)

Sorry, topic closed!

Hello, thank you very much for creating this repo and the image. I tried it and it unfortunatelly does not run the games, I can at least run Stella in SDL even with my special joystick support!
Btw, are you planning to port it to the latest Armbian?

Don't you just hate when you have had a problem for days and you finally ask for help, you happen to figure it out? I guess it's cause at that point you abandoned your train of thought.

Anyways for anyone else trying to get the analog features working for farious SEGA games and rebind them for your flightstick or steering wheel I've made a little chart so you can add the rebinds manually

Find your games keybindings file, as example i'll use Afterburner II on the MegaDrive. which can be found at: "/opt/retropie/configs/megadrive/Genesis Plus GX/"
In my case with filename "After Burner II (USA, Europe).rmp"

Open it in notepad and adjust your keys, here is an example of the default buttons, with the A,B,X,Y buttons added, and the vertical throttle removed.
I've also made a little picture you can use as reference, you'll find that under the code, it has all the numbers you need to use.
That's all, have fun setting up your flightsticks and racewheels on a 16bit console.

#Device ID for XE-1AP: input_libretro_device_p1 = "773" #Start and Select input_player1_btn_select = "2" input_player1_btn_start = "3" #A,B,X,Y = East,South,North,West input_player1_btn_a = "11" input_player1_btn_b = "13" input_player1_btn_x = "10" input_player1_btn_y = "12" #D-Pad is unused so lets add Select and Start to it incase your flightstick doesnt have enough buttons input_player1_btn_up = "-1" input_player1_btn_down = "-1" input_player1_btn_left = "2" input_player1_btn_right = "3" #Left Joystick input_player1_stk_l_x+ = "16" input_player1_stk_l_x- = "17" input_player1_stk_l_y+ = "18" input_player1_stk_l_y- = "19" #Right joystick (Throttle) input_player1_stk_r_x+ = "-1" input_player1_stk_r_x- = "-1" input_player1_stk_r_y+ = "21" input_player1_stk_r_y- = "20" #Left Shoulder buttons input_player1_btn_l = "10" input_player1_btn_l2 = "12" #Right Shoulder buttons input_player1_btn_r = "11" input_player1_btn_r2 = "13" #No idea what E1 and E2 buttons are for, but lets add them to the thumbstick buttons (R3, L3). input_player1_btn_l3 = "1" input_player1_btn_r3 = "0"

XE-1AP.png

@quicksilver
Thank u i will give a try :)

so im still getting this on my runcommand.log and the game just go back to emulationsatin
https://pastebin.com/KYeiA7DE

@Crush Thank you so much! That worked perfectly

@peggytam009 said in why does mupen64 run better on my old phone, even though it has same specs as the pi3?:

@dankcushions said in why does mupen64 run better on my old phone, even though it has same specs as the pi3?:

what RDP (video) plugin is your phone mupen running?

i'm guessing your phone's GPU is GLES 3.x (pi3 is GLES 2.x), so it can run yabasanshiro, which is a good android saturn emulator. we're yet to get it running great on even pi4, but it won't run on pi3 at all, due to GLES version.

i managed to find the driver that mupen64 uses on my phone, its "GLES2N64"

mupen64plus-gles2n64 is available on retropie, however it's not very compatible and there's an issue with pi4: https://github.com/RetroPie/RetroPie-Setup/issues/3118

as for the saturn emulation, i think i was running the experimental package one called "yabause"

yeah, as far as i know this is good for android, but the linux gles versions are lacking. yabasanshiro is a promising fork, but has issues right now, and no-one to lead development on the pi side.

Thanks for the response @BuZz. What are some of the things that are missing from devuan on the pi that raspbian has for Retropie to work properly?

Yes this work around worked for me as well. Thank you

What was the solution? I'm trying to mount all my configs and roms and everything on an external usb so the 'OS' just runs from the card and nothing else.

@YFZdude So I was able to get SSelph's scraper to work, but after a while, it started giving me "hash not found" errors and a "panic: runtime error". I've been searching for solutions for this, but I've found next to no information on the issue and the github page doesn't seem to be active. I'm gonna try Skraper and see if that gives me better results.

@trallis I tested out removing the RetroArch commands from the conf file and it seems to work now. I guess I can just keep the binding for the menu and do the actions from there - but having the hotkey switch would be nice.

@nmlnet said in Using a second controller for the hot key:

When I map the input controller buttons for the controller and get to hotkey, it doesn't recognize the keyboard input

You cannot map inputs from 2 separate input devices in EmulationStation, each one should be mapped separately. Try mapping your keyboard as well - separately from your SNES gamepad - and choose a hotkey there.

TAhis works because your 2nd device is a keyboard and it works as P1 (just as your gampead), otherwise you wouldn't be able to use a 2nd controller for hotkey - only P1 has hotkey control.

@Quark said in Set amiberry to 50Hz:

But, there is a file or script where to place "tvservice -p" command or must i write it in terminal every time i use and exit from amiberry?

You can use the onstart/onend script support in runcommand (see here) and the tvservice -p in the onend script.

Not sure what you mean - RetroPie doesn't configure a specific video aspect, it uses what is available on the system.

I have to apologise - I got the same error! Was caused by a recent change: https://github.com/mupen64plus/mupen64plus-ui-console/commit/e147b94f3c82866a42e3f72820e73c441158e7d5#comment

it has been reverted following discussion here: https://github.com/mupen64plus/mupen64plus-ui-console/pull/61

Please try again and it should work.

@mitu Thanks! :Banghead: Now that was a typical case of "Betriebsblindheit" (1) inmidst my current setup orgy - Sigh. Should have also tried 'em without the bindings 1st. !

[1]: I never came along a real translation for that, but Target fixation or Tunnel vision (metaphor) may come close to it.

@Clyde Wasn't aware of that tool. Cheers.

@mitu
Thanks for the reply!
I do have a normal TV, the problem is that the HDMI cables I've ordered along with the pi 4 don't work. I'll have to order new ones to test at a later date.
The reason I just kept working on with this screen was that I wanted to build a small (4:3) bar top arcade with it.
Now, knowing that this screen won't work for this, I'll have to research for a suitable replacement as well.
Thanks for the help :)

It has worked!

In a bit more detail:

I didn't add entries for P3 and P4 on retroarch.cfg because, what would I set them to if I only have two controllers? 4 and 5, assuming that I could be plugging in additional ones?

Anyway, I tried to re-add the two physical Logitech controllers to EmulationStation; it detect 4 controllers, but it would keep detecting the button presses as coming from the emulated Xbox controllers.

I then reset the controller settings for EmulationStation on the Retropie menu and again, it would detect 4 controllers, but it also would keep detecting the button presses as coming from the emulated Xbox controllers.

I had to disable xboxdrv and then it would only detect 2 controllers and the button presses a coming from the physical Logitech controllers. The conclusion here is for EmulationStation the physical and emulated controllers don't clash; the emulated ones take priority and the button presses are understood to be coming from them.

I then checked that on the Retroarch menu the emulated controllers were assigned to P1 and P2 and removed the physical controllers that were assigned to P3 and P4. And then everything was fine. The crux here appears to be that I had a clash, as both the emulated and physical controllers were assigned to players and probably registering button presses. Something that support this hypothesis is that on games where you have a grid to select your character (e.g. Mario Kart) it was fairly obvious that when I was pressing once to move one cell to the right, for instance, the selection box was moving two cells.

Thanks again for all your time helping me figure this out.