The encoders should appear as regular joystick/gamepads under Linux, so something like pygame or python-evdev should be enough to read the inputs.

Can you run EmulationStation with debug logging and upload the log ? Exit ES, then run it with emulationstation --debug, reproduce the issue and then post the log file on pastebin.com.
The log file is in $HOME/.emulationstation/es_log.txt.

I've tried the steps you mention in reproducing the error, but as far as I see omxplayer stops once the screensaver is stopped.

Do you have any additional configurations in ES - namely any external scripts tied to the ES Scripting API ?

@sleve_mcdichael Thanks

Thanks for the responses so far. An update on this issue: I gave the analog settings in Retroarch a try but they had no impact on the sensitivity.

I decided to go back and dig deeper into mouse polling. I came across more information about mouse polling in Linux: https://wiki.archlinux.org/title/Mouse_polling_rate#Polling_rate_and_polling_interval

I added usbhid.mousepoll back to the boot config file, set the GRS spinner to pulse at 512, and did some testing. Without that command or when I set it to value 0 (system use polling rate requested by device), my spinner runs slow. When I force the system to poll at either 1, 2, 4, or 8, the spinner runs at a much faster speed. The spinner moved at the same speed with all four values, so I left it on 8 to save CPU cycles on the Pi.

I set MAME sensitivity according to the formula (14%) and the blaster now free spins at the familiar speed. I can also properly adjust Major Havoc. Interestingly when I do a 5-space full turn test, a full turn with the GRS is exactly 10 spaces. The blaster isn't moving twice as fast; the blaster clicks at the same speed as this guy's setup with a turbotwist:

I wonder if the GRS is reporting a half turn as a full turn.

In any case, I'm willing to call this issue resolved to my satisfaction.

@zoura said in UI messed up after full storage:

@sleve_mcdichael That helped a bit, still very basic names and apperantly no photos for the RetroPie items, but thanks!

Try reinstalling "retropiemenu" from the setup utility under manage packages > core packages.

@chris-1 Spyro runs well on my pi zero (original model) using the standalone pcsxrearmed so pi zero 2 should have no problem. In the case of PS1 emulation I think youre better off using the RetroArch version because it's more up to date. The pi zero 2 should have more than enough overhead to handle it.

Dont worry mate. I could manage to do it. maybe not the best xml code ever (which I know almost nothing hehehe) but copying chunks from one xml to another it worked

@mitu Once again, I tip my hat to you.

@tzdig don't write/drag/put anything before certutil.

Hi @Ruidog

I got some troubles too with two DragonRise controllers and a PI3b+.
Look at this thread, it helped me:

https://retropie.org.uk/forum/topic/9259/so-close-dragonrise-arcade-sticks-and-button-sets-joystick-on-a-player-reverses/6

@dizmodawg you know what I'm looking at the Daphne documentation and it looks like it's a bit more involved than most other emulators. Usually, I would add the new <extensions> to the entry in ~/.emulationstation/es_systems.cfg, and then add the new emulator line(s) in /opt/retropie/configs/[system]/emulators.cfg.

But Daphne has that weird folder structure, where there's a roms folder with the .zip files but that's not the game entry, the *.daphne folders are the game entries. And the Daphne system doesn't read .zip files as entries but the Arcade system does, so if you merge them in this same way, then your "Arcade" system will have a weird "roms" sub-folder in it with a bunch of zip files that don't work...

In this case, I think maybe it's better off leaving it a separate system.

@adamantiumpimp said in Stuck on a splashscreen/command prompt!:

@exarkuniv Apologies for my ignorance. Is it the PlayBox part of it that is the rebuild? Sorry I'm just now getting into all of this and am unfamiliar with the lingo.

It is impractical to provide support for a system that neither you nor we know how is configured. *Pre-built, aka third-party (anyone[3] who's not you[2] or the RetroPie project[1]) systems are not supported. The only supported configurations are the official SD images available on the download page or installed on top of an existing OS using the setup script.

We will gladly help you through the process if you'd like to start over with the default image and build a system yourself. Or, you can contact the author of your custom build and ask them to provide support for the system that they have configured.

I think I got it working finally! Thanks a lot for the help, it's much appreciated!

After trial & error, I have pcsx2 libretro core up and running on Ubuntu 20.04
Hopefully somebody can turn this chaos into an unofficial script.
Keep in mind that I'm rusty with retropie configs.

Okay so.. Here we go.

sudo apt remove gcc-9 g++-9 sudo apt install cmake g++-10-multilib libaio-dev libasound2-dev libcairo2-dev libegl-dev \ libegl1-mesa-dev libgdk-pixbuf2.0-dev libgirepository-1.0-1 libgl-dev libgl1-mesa-dev \ libgl1-mesa-dri libgles-dev libgles-dev libgles2-mesa-dev libglib2.0-dev libglu1-mesa-dev \ libglu1-mesa libglvnd-dev libglx-dev libglx-mesa0 libglx0 libgtk-3-dev libgtk2.0-dev \ libharfbuzz-dev libllvm10 liblzma-dev libpango1.0-dev libpcap0.8-dev libpulse-dev \ libsdl2-dev libsamplerate0-dev libsoundtouch-dev libwxgtk3.0-gtk3-0v5 libwxgtk3.0-gtk3-dev \ libx11-xcb-dev libxext-dev libxft-dev libxml2-dev portaudio19-dev zlib1g-dev ccache sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-10 10 sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-10 10 sudo update-alternatives --install /usr/bin/cc cc /usr/bin/gcc 30 sudo update-alternatives --install /usr/bin/c++ c++ /usr/bin/g++ 30 git clone https://github.com/libretro/pcsx2.git && cd pcsx2 && mkdir build && cd build cmake .. -Wno-dev cmake .. -DLIBRETRO=ON -DCMAKE_BUILD_TYPE=Release make -j$(nproc) cd ../bin

If everything goes right, there should be a "pcsx2" folder in the "bin" folder of the root folder.

Make a "lr-pcsx2" folder in "opt/retropie/libretrocores" and move the "pcsx2_libretro.so" into it.

pcsx2-libretros bios seem to be hardcoded to one spot.. otherwise segmentation fault.

Make a "pcsx2" folder in "Home/Retropie/BIOS" and move the "pcsx2" folder from the "bin" folder into it.

Yeah its weird.. the folder tree should look like:

"Home/Retropie/BIOS/pcsx2/pcsx2/bios"

And of course have all your ps2 bios files in that last folder.

Now if you have pcsx2 stand alone installed..

Go into "opt/retropie/configs/ps2" folders, otherwise make one.

Edit your "emulators.cfg" and paste this:

lr-pcsx2 = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-pcsx2/pcsx2_libretro.so --config /opt/retropie/configs/ps2/retroarch.cfg %ROM%"

Make a "retroarch.cfg" and paste this:

system_directory = "~/RetroPie/BIOS/pcsx2"

Now load a ps2 game, be sure to set your runcommand to "lr-pcsx2" and cross fingers.

gcc-9 will be installed whenever you update your retropie emu's.
So you have to go through the compiling procedures above any time you want to update pcsx2-libretro.
Actually after a few times it seems gcc-9 and gcc-10 are installed.

Keep in mind these are alpha builds and purely x64 so no software mode.

Edit your es_systems.cfg to accept .chd in the ps2 section.

If someone can make an unofficial script out of this. It would be appreciated.

@plastyk
Try this simple tutorial here : Development of module-script generator for lr-mess and mame standalone
You will be able to run it with Lr-Mess and MAME standalone.
The name of the game folder will be svision (for supervision),