@ts-x I'm going to that site now. Thank You! Sorry for the delay, personal home things....

@mitu This was the cause of my issues. More info here.
https://forums.raspberrypi.com/viewtopic.php?t=349070

My issue was also fixed by adding arm_64bit=0 to /boot/config.txt.

@sleve_mcdichael thanks mate. Got it now. Just needed to get the path fixed. Armor Attack has terrible screeching audio. Other than that all working great.

I don't see an ARM compatible download, so it won't work on a Pi. The Linux installers will work on a PC running an Intel/AMD CPU, but not on a Pi, which has a different kind of CPU (ARM).

For anyone running an older version of RetroPie, this game successfully installed on 4.3 for me. Note that I ran the normal install process but then had to manually move the install script module from ext to scriptmodules/ports, and then install like a normal port from within RetroPie to complete. The keymapper is indeed buggy, using it with my Xbox 360 controller corrupts the Dpad mapping for the game. So you basically have a choice between accepting the default mappings or losing Dpad support (with the game still being playable via the joystick). FYI, I tried @Lolonois' script but it errors out because of missing dependencies related to my older 4.3 install.

Regardless, this is a frantic and fun game...definitely worth checking out!

The major issue I have is that RetroArch input mapping works great, but it doesn't work well with Dolphin or OpenBor or Ports or ScummVm which is the bulk of my gaming. So, that's why I have a hodgepodge of RetroArch, gamecontrollerdb.txt and other stuff going on here.

Not sure why you think RetroArch's configuration is relevant for the standalone emulators - they're entirely separate. Or maybe I'm mistaken ?

I've managed to get joy2key_sdl going. I have 2 8Bit Do Pro2 controllers. Interestingly, when they are by Bluetooth they are called "8BitDo Pro 2" and when plugged in by USB they're called "8BitDo 8BitDo Pro 2".

Yes, that's not un-common for gamepads, having different names and/or input mappings depending on the connection type. 8BitDo are even more eggregious in their behavior since they have also different connection modes (Xbox/PC vs. Switch vs. Android vs. etc.)

When plugged in I get "configured device" despite having a separate "8BitDo 8BitDo Pro 2" config file in /retroarchjoypayds
[...]

and I have this config I sourced from 8BitDo which might be a better bet?

How can I get the USB and Bluetooth connected controller to behave similarly?

Just configure the controller separately for USB and Bluetooth. The input codes may not be identical between the connection types and you can't rely on a firmware update to now change them.

Also, the mapping is rather strange, despite my mapping in the 8Bit Do Pro2 config, it is coming out wonky and despite it working ok in Retroarch and some other configs. Why the pageup and pagedown stuff?

Not sure what you mean here.

@sleve_mcdichael said in Links For "Installing on top of an existing OS" Are Not Working Under the Download Tab:

any docs page I have bookmarked is showing "not found"

Yes, it's just temporary for now, will probably be fixed later on. Probably some pip upgrade broke mkdocs or mkdocs itself is broken ? I'll take a look.

EDIT: Docs should be working again (thanks @BuZz).

@BennyProfane ooh thanks for all the information. I have this book you see called "ZX Spectrum Games Code Club" which gives you a bunch of games you can code for yourself on the ZX Spectrum. Such as Tic Tac Toe and Breakout.

If VS Code can do the same thing and pack it into tap/tzx which I could then port to RetroPie's Spectrum emulator to play, I think that'll be just as much fun to get my teeth in to.

All I know so far is a little bit of C#, html, and Scratch (if you can call that a programming language lol). I'm looking to spread out a little into other languages and since I had the pi and code club book, I figured I'd start with some Basic before moving on to tutorials for Unity.

@Blorpal said in Random movement in the game menus:

@Addison Does that work with a x86 computer or just the pi?

Oh man, it's been so long ago I can't remember what I did back then.

I didn't purchase a USB Hub or solder anything, I know that much.

https://www.reddit.com/r/emulation/comments/7g2d0n/howto_fix_phantomghost_input_on_ibuffalobuffalo/

I still use the wired controllers on my Pi 4 since they're wonderful.

I do have the default Wi-Fi disabled and bought these instead for 8x faster speed:

https://www.amazon.com/gp/product/B07PB1X4CN/

Don't think I can be of any help except for posting that first link I shared.

@sleve_mcdichael Thanks for the clarification. I think I'll just use quotes anyways since, it sounds like it's a good habit to get into for more complex data like strings.

@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.