@nicshoe18

I had to add usbhid.quirks=0xf000:0x0008:0x100000 to /boot/cmdline.txt and then reboot to get jstest detect the missing buttons.

@sirhenrythe5th
File patch:
/retropie/roms/psp/Battlefront Renegade Squadron.iso

@fatfei said in Joystick not working in emulators:

I can move the joy stock to select different characters but when it comes to a race, I can't turn. I randomly chose another bye game and the stick doesn't work on that either.

I think this is because the N64 games were set up to only use the analog stick. If you mapped your joystick to the UP,DOWN,LEFT,RIGHT buttons, then that is the same as using the D-Pad. The analog stick has separate mappings. Something like Left Analog Up, etc.

Ok, this is embarrassing.
It turned out that (for some reason) the volume was set to -60 db in the playback audio setting, and this (for some reason) affects also the Kodi UI sound volume. The playback audio settings are separated from the general settings > system > audio, but the playback audio can be modified pressing the keyboard keys + and -. This, coupled with the weird behavior of Kodi that (for some reason) does not play UI sounds when using a controller, but only when using a keyboard.
It turned out to be a rather silly problem, but I leave it here hoping this can help others facing the same behavior.

@jimmyfromthebay

Due to this thread I found that there was a mistake in my script and I fixed it.
So now it can create lr-mess overlays for gnw from the mame artwork.
2022-03-02-183543_800x600_scrot_resized.png
I think it's not what you are looking for, though.
It is still an overlay and transparency is always used and not perfect.

I have tried the combination lr-mess with mame artwork but never had any result,
because then the game just won't load.

Perhaps you both can find a way.
It would really be nice if it could work like you want to.

@silvan Doesn't work even with a dongle. Using bluetoothctl I can pair it, but the controller keeps flashing and it doesn't work,.

@persephale It's the same as flashing a sdcard, if your Pi supports booting from USB. Pi4 should have this by default, for the Pi3 you still need a sdcard in order to boot RaspiOS and enable USB booting. See https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#usb-mass-storage-boot for more details on Pi USB boot support.

@sleve_mcdichael

BLAH! I had a feeling that was coming. Cool. Thanks for the info!

@redmarsbluemoon We intend to include SDL 2.0.20 - not only in Bullseye, but on Buster also. For Mesa, we always use the version offered by the OS, I don't think this will change soon.

@chaoseffect Done. It's possible it'll just lead to a "mute" moment, but it's worth a shot :D I'm happy to follow a lead, but I really just don't know where to go from there.

Roms (and saves) can be easily be placed on an external disc - https://retropie.org.uk/docs/Running-ROMs-from-a-USB-drive/.

For configurations (almost all of them are kept in /opt/retropie/configs), there's no out-of-the-box solution available, since they require a Linux filesystem and generally users have a PC/macOS compatible partitioning schema on their external disc.

If you want to dedicate a SSD just for running RetroPie, you can just install RetroPie on the SSD drive (same process as installing it on a sdcard) directly.

Has anybody ever came across a good learning book for this stuff?

RetroPie specific documentation - https://retropie.org.uk/docs/. Raspberry Pi documentation - https://www.raspberrypi.com/documentation/ (has a Getting started section and a Using RasPI OS guide). The RetroPie image is based on RasPI OS. For Linux in general, I'd recommend the Debian user guide (https://www.debian.org/doc/manuals/debian-reference/index.en.html). RasPI OS is based on Debian, so it should apply to a RetroPie installation.

We have some notes in the docs about dealing with a 4k resolution, but the canonical source is always the Raspberry Pi docs at https://www.raspberrypi.com/documentation/computers/configuration.html#hdmi-configuration.

EDIT: I'll add some notes about the 2nd port and a link to the video mode table listing.

@winterelf 3rd party builds are not supported by this forum.

If this were a build direct from this forum, the above fix would have worked. The file extension list in the es_system.cfg is the only change you need to make to allow a file to be shown in the game list of each system. It will just show without meta data until it is scrapped. This is also how it shows any images or videos. Once ES reads that file extension in that list, it knows what to do.

So who knows why your build is not doing that. You'll have to ask the team that created it.

@tigtagle said in Rasp-Config not working:

I also used a wolfanoz image for arcade 1up and flashed that onto my card too.

3rd party images are not supported as they are often distributed with copywrited material and are basically impossible to troubleshoot.

In case it helps anyone, the way I achieved this was to put single disk games and m3u files for multi-disk games in the root of roms/x68000, and place the images for the multi-disk games in a separate sub-folder (roms/x68000/multi) then write the m3u files to point at them.

The system ignores the sub folder and just the stuff in the root is displayed.

Root of x68000:

6b7f8744-7d12-48fc-abe3-c0ce2921bc79-image.png

Contents of 'multi' folder:

b0e9f1ad-1d6b-4241-86b0-2e4d45bc0db3-image.png

@dankcushions I have many games that run full speed with 4x MSAA and a CRT shader when using lr-mupen64plus-next. The issue I have is the temporary freezes when loading new textures/shaders for the first time. Standalone mupen64plus-GlideN64 runs at native resolution for me, i.e. 320x240, which to my eyes is unbearable on a modern screen.

Still, thanks for pointing me in the right way of the .cfg file - I wasn't sure if this was the one that would be used by mupen64plus-GlideN64 :) I will try experimenting a bit and will report back.

@mitu

Hey sorry for the lack of information I sometimes forget there can be a verity of variables. I’m nowhere near my Pi at the moment so I’ll give the information I know now, and once I get to my Pi I’ll share the rest.

Pi Model or other hardware: Raspberry Pi 4 B 4gb overclocked CPU 2Ghz

Power Supply used: Not entirely sure at the moment, but my
Pi is in the RetroFlag NesPi4 with the External usbs and Ethernet ports disconnected because of Bluetooth/WiFi interference

RetroPie Version: I installed 4.7.1 to an SD card and regular update it in the Retropie script (I know I need to be exact, I’ll get this information as soon as possible)

USB Devices connected: 1 terabyte SSD Sata to USB3

Controller used: Official Atari VCS Classic Joystick

I’ve only tested the two default RetroArch cores for NES and Genesis (I will find out exactly which ones later)

In the RetroArch menu If I go into settings -> input -> ports1 (I think it’s called that), I see that the input device is set to classic controller and the inputs match the numbers of the buttons. EX: button 0 = ‘a’.

Interestingly enough if I disconnect that controller while the game is running and connect a WiiU pro controller, the buttons remain messed up. (I tested this a long time ago so for the sake of assurance I’ll test this again). If I quit RetroArch swap controllers then open a RetroArch core buttons revert back to normal.

I will test the joystick with that command in the terminal when I get a chance, but I did do jstest and the spinners seems to read like a joystick with a single axis.