@lebonhomme said in Trouble cloning joycond for NS controller:

Firstly it prompts a username and password, making me to create an account on Github

You most likely mis-spelt the repository name/the URL, GitHub will prompt you for user/pass since it thinks you're trying to access a private repository. There's no need to create a user/pass for Github to clone that repository, in fact I just did it and it didn't asked me for user/pass.

@ExarKunIv I attempted this unsuccessfully but will give it another shot.

The configs in openbor are not user readable / not in any way like a retroarch.cfg.

And like I referenced above, my openbor saves are for some reason saving to: /opt/retropie/configs/all/emulationstation/Saves

@owsey147 Your OS is outdated and no longer supported; currently only Debian 10 (Buster) is supported and, unfortunately, cannot be upgraded in-place.

In addition, is not practical to troubleshoot a system that neither you nor we have any idea how is configured. For this reason, purchased systems and other third-party builds are not supported in any capacity.

For both of these reasons, you will need to perform a fresh install of the latest supported version.

Start here: https://retropie.org.uk/docs/First-Installation

I suggest you to backup if able your existing roms and BIOS, and then install the current latest official image for your hardware from the website at https://retropie.org.uk/download. After the new version is installed, you can restore your backed up roms folder.

So most likely the USB hub is disconnecting at some point and EmulationStation crashes during that moment. Can you try and get a separately powered USB HUB ? Or perhaps a newer PC, since the one you have is more than 10 years old ?

@mitu Whew. It's getting weird now.

I just built the latest version of SDL2 from github.

cmake sees SDL2 as 2.29.0 now instead of the previous 2.0.10.

So then I rebuilt Emulation Station.

The preinstalled Emulation Station was v2.11.2rp. The one I've built identifies as 2.12.0rp-dev.

The good news:

Emulation Station now recognizes my L2/R2 triggers!

The weird news:

When I launch retroarch emulators, they do not recognize my L2/R2 trigger presses. While the bluetooth dialog still reports my controller name as "8Bitdo SN30 Pro" when I pair and connect it, this newly-built version of Emulation Station reports it as "Xbox 360 Controller".

@mitu hello and thank you for your answer.

I did what you suggested and nothing happened, but after trying over an over I could make the controller to work.

The thing was that the system didn´t recognize the HID of the device, so I modified the cmdline.txt file to ignore special drivers. After a reboot the controller was detected as a ps3 controller.

By now is working flawlesly wired. I have to figure out now how to connect it by bluetooth.

thank you!

@mitu I see, so use a USB extension cable for the dongle.... I was hoping to keep this as aesthetically pleasing as possible. Are theere any good dongles that have better range?

@JackTaylor said in Retropie saving images in /boot:

However, I have found there is another roms folder on the boot directory, where the images are being sent to when the pi boots.

Not sure why that happens, but it's not from RetroPie. EmulationStation, which is the only RetroPie program started at boot that stays resident, doesn't move images around.

@mitu I found out I had themes and videos saved there, thanks for the help!

@pgcudahy said in Analog trigger on lr-dolphin:

and the triggers are now bound to an axis and not a button

Right. That's good, that's what they should be.

Ah thanks! Section 3.1 was what I was looking to understand ...thanks

@windg Thanks, but THAT game is actually a translation of XZR II and Exile 2 is actually XZR III. XZR I was not translated into English and is only on the PC-88 and MSX.

@avrod7755 I'd look into setting up SFTP (or Samba Shares if you use windows) for transferring roms. For big cd based systems it takes ages over usb. You can monitor the transfer properly and it's less fiddly by SFTP (can even do it by your smartphone if you wish)

I'm not sure what exactly I touched, but it seems to be working better now.

I found that my /opt/retropie/configs/all/retroarch.cfg had sdl2 driver set as default ... I changed that to udev. Now, both my controllers seem to work.

I had originally thought that my old PC had a legacy BIOS/usb option that was doing something ... but didn't prove out to be anything useful. I think the change from sdl2 to udev in the default config was what did it. I don't have a verbose logging or capture of files to prove that, but my verbose logging now shows that udev device being used. Spot check of a few other games seems to have good results. I have a feeling that my install for some reason defaulted to sdl2 driver and what was my issue.

Thanks for the help

@PhtevenTheSecond depends on the game. There's some core settings that can be changed to adjust the loading to an extent. Do beware though that certain games have the load times baked in as part of the games audio and other mechanics, so removing them would screw up the game. Smackdown 1 and 2 are good examples of this I think

@gpmcty hi. I originally posted your exact problem and I highly suggest following that thread which corrected it. Lolonios did an outstanding job of fixing the problem with his "version" of JzIntv.

I hope at some point that becomes the download version, instead of having to apply this patch. JzIntv is not really supported anymore.

@mitu I'll check out the link, thank you

@Sfora hello! Which version of the games are you relying on? I trust it's the .lha version, right? I just tried ChambersOfShaolin_v2.0_3049.lha as well as DizzyPrinceOfTheYolkfolk_v2.0_1146.lha and both work without any issue on a similar setup.

If you're seeing the Amiberry logo instead of a typical WHDBooter page whenever you run a game then something's off on your setup. Please make sure to use the .lha as-is do not rename these files.

amiberry.log is the right place to look for errors. Feel free to share it. Then ensure you're using the exact same KickStart mentioned on that page. Also do not hesitate to read the wiki for further details about WHDLoad/WHDBooter.

Hope this helps.