@NewAtThis said in TI99, Resolution, and Joystick: Do you have any suggestions for the resolution problem? Right now, no, but there seems to be an updated version of this emulator which might be working better on modern Linux installations and we might update it in the near future. I'll test and compare to the current version to see if there's an improvement for video resolution handling in the new version.

Open the options on the Retroarch menu and there's an option whose label I forget that will "map directions to digital" instead of analog. It's set to analog by default. I had to do it a few days ago. See if it works.

@NurseAngela what I have is a cheap usb PS2 replica controller which I have assigned as player one for consoles such as N64, PS1 etc that would need the trigger buttons

@mitu I made a mistake in my testing, I beleive python-uinput my work

@quicksilver, Thank you for your reply

@pjft said in Please help, arcade machine.: If you're in the UK, the folks at https://www.arcadeworlduk.com/ were reliable, back then, and have everything you'll need. I can second that for Germany, too, at least before the Brexit. But I guess it will only add the possibility of import taxes for Europe now. I got nearly everything for my DIY arcade cabinet from AWUK except for the cabinet itself, its screen, and the Pi. You should also look here in the forum for threads about other people's cabinet builds. The next best thing to learning by doing is learning from other people's doing (and their mistakes). :) edit: As for struggling, such a project can really help getting your mind off it. My cab did the same for me when I suffered over the temporary loss of a very close platonic friendship with my ex-girlfriend because her new partner couldn't bear it even after a couple of open talks with both of us. He's already history and we both have new partners by now, but that doesn't diminish the help I had from my project.

Hello all, No idea anyone ? :'( I forgot to mention that : Retropie was installed from an official pre-made image for raspberry pi: retropie-4.5.1-rpi2_rpi3.img... and that I've done an upgrade to 4.6 through the retropie_setup script. Since my 1st post, I've also installed Hatari 1.8.0 after having "hacked" the retropie_setup script in order to deploy the 1.8.0 (through source, pointing to the dowload repository of the official hatari distribution) instead of using the 1.9.0. I made this in order to have similar version as lr-hatari. So... I've restarted Hatari, re-saved my conf (hoping that it will be compatible with lr-hatari) and restarted lr-hatari. But 2nd controller is still not recognized... Any help is welcome. Regards, Ed

@mitu said in master system: I suggest you start with a fresh image and add your ROMs/BIOS files, leaving the configurations alone for this first step. very well, that's what I'm going to do. thank you again for your help and your patient to answer me. thank you and good luck

I did it this way: copy the default RA-controller-config to another place of your choice (i.e.: "/home/AMIBERRY Inputs/") edit the button-mapping as you like in this copied file start AMIBERRY-GUI go to "paths", navigate the "inputs"-path to your new one. click on the button "rescan paths" There you go, the inputs are now as you like to have them global for all games ;)

@DimaKompot I will try that

@Marconemusic If I understand you correctly, everything works except Mame Controls are not mapped how you want, is that correct? If this is true, it sounds like you have to remap your controls for mame emulator. I have an arcade cabinet and when I mapped my controls, I mapped my joystick as D-Pad. I have no analog stick mapped with my joysticks. If I use an Xbox One Controller, I map everything accordingly but outside of that, I don't have an analog stick mapped. Even when I did use my Xbox One controller, Mame and Final Burn did not recognize my analog stick. If Mame is the only thing mapped incorrectly, try remapping your controls for Mame. You can hit tab on your keyboard within Mame and you can set your controller mapping there for the General mapping or for each game. If your Emulation Station also isn't mapped correctly, you may have to remap the controls for that input device. One time I had issues when I was building mine and controllers got reversed between player one and 2 when I didn't plug my inputs into the same USB port they were before. When I plugged in them in how I had it, it fixed that issue.

Found an issue with source code. Pull request are pending. https://github.com/libretro/libretro-atari800/pull/38

So, for me I find "my" solution" to use two joysticks (for my 2P games) without any problem ;-) The DragonRise USB adapter has the option to use (connect) 12 buttons (plus 4 for the directions), I use 6 "inputs" for the second player joystick from one DragonRice Joystick-Adapter. Three free connections on the DragonRise circuit board, and three connections which are not used when playing (like P1 and P2 start-button) and the button 4 (not used in most games), so I have totally 6 "inputs" for the 2nd players joystick. To connect a joystick (I use my 25 years old competion pro joystick) I solder a 9 pole D-sub plug on it, on the Arcade station also a D-sub rifle. The second player has "only" 2 buttons he can use (plus 4 for the 4 directions) , but in my most 2 player games this is enough. In the Mame inside menu I only have to press the wanted buttons on the usual way to learn the buttons for the second player (game by game). For me it works, no issues with a second USB controller etc .... player one and player two are using the same hardware "controller", only different inputs from this ... I hope it's clear what i mean ;-) D-sub rifle (nine pole; 7 used: 6 for the buttons plus ground): Plugged in Competions Pro:

@mitu Thanks, save/load is working. But strange, usb calbe keyboard is connected, also arrow-keys are working inside the retroPie, but in the Game-Menu no key is working, also no (i.e.) "5" to start the game. I must use the virtual keyboard (select key). But OK ....

Ok so this is solved. The good news is at least as far as I can tell the Sanwas don’t go bad after only a year of use. This was a wiring issue with some of the connections I made between the five wire harness and the wires to the usb encoder coming loose, ironically and randomly several at a time. I don’t always supervise the kids’ use of the arcade so it is also possible this wasn’t REALLY random, maybe one of the kids was particularly rough or lifted up the control panel lid and pulled some of the wires. All fixed up now! Now I have a few extra Sanwas for spare parts though! (Only figured out it was a wiring issue once I installed the new joysticks and problem was still occurring...)

@arduinoGamepad Emulationstation is using SDL's joystick sub-system to handle joysticks, my guess it's not detected as such. There's a similar sdl-jstest utility -which is similar to jstest - that tests whether the joystick is detected by SDL. To get it detected by ES, try one of these - in order add a local udev rule to force the device to appear as a joystick: SUBSYSTEM=="input", ATTRS{idVendor}=="<VID>", ATTRS{idProduct}=="<PID>" ENV{ID_INPUT_JOYSTICK}="1" substituting VID and PID with the values you get for your controller from running lsusb. Use Xboxdrv to make your device be seen as an Xbox driver.