Emulationstation issue - idle game selection change

mitu

@ilpappa said in Emulationstation issue - idle game selection change:

What are your thoughts?

What did testing with jstest / evtest showed up ?

ilpappa

@mitu said in Emulationstation issue - idle game selection change:

What did testing with jstest / evtest showed up ?

Jstest showed nothing suspicious, no input reported unless I was touching something. I also have the suspect that if I stay on upper level on system selection the issue would be gone. It happens only if I’m inside a system game list.

EDIT: I'm right, being on upper level does not create any issue, the selected system remains the same and no input is registered as expected.

I recently updated all my scraps via skraper, will try rolling back with old image/video sets to see what happens. I'd say the issue is within emulationstation and media sets. I'm also enclosing below last log from tonight, where even a game was launched so it's actually not only random selection but sometimes also game launch.

New log with Game Launch

Starting point at```
Jan 21 03:05:36 lvl3: fireEvent: game-select neogeo /home/pi/RetroPie/roms/neogeo/19yy.zip

mitu

@ilpappa Did you test both joysticks ? The ES log shows input from both joysticks.
EDIT: EmulationStation uses SDL for input processing. The equivalent utility to jstest for SDL input diagnosis is SDL-Jstest. My guess is that if you use it it will show the same symptoms ('ghost' inputs).

ilpappa

@mitu said in Emulationstation issue - idle game selection change:

@ilpappa Did you test both joysticks ? The ES log shows input from both joysticks.
EDIT: EmulationStation uses SDL for input processing. The equivalent utility to jstest for SDL input diagnosis is SDL-Jstest. My guess is that if you use it it will show the same symptoms ('ghost' inputs).

Tested both, no issues. Will now start testing with SDL-Jtest.

Strange thing is that being on upper level does not create any issue, the selected system remains the same and no input is registered as expected.

ilpappa

@mitu I could not install sdl-jstest as I had following errors so I went for jstest-sdl.

I could not see any ghost input during the several hours of test, from both joysticks, so all went fine. Apparently other people are suffering same issue by looking online, of course only in emulationstation Emulation Station menu phantom scrolling .

Not sure at this point what to do, other than drestroying my cab :D

pi@retropie:~/sdl-jstest $ cmake .
-- Could NOT find tinycmmc (missing: tinycmmc_DIR)
-- tinycmmc module path: /home/pi/sdl-jstest/external/tinycmmc/modules/
-- ProjectVersion: sdl-jstest 0.2.2-20-ga73cfcb
-- Configuring done
CMake Error at CMakeLists.txt:64 (add_executable):
  Target "sdl-jstest" links to target "SDL::SDL" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?


-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.
pi@retropie:~/sdl-jstest $ make
[ 50%] Built target sdl2-jstest
[ 75%] Building C object CMakeFiles/sdl-jstest.dir/src/sdl-jstest.c.o
/home/pi/sdl-jstest/src/sdl-jstest.c:24:10: fatal error: SDL.h: File o directory non esistente
 #include <SDL.h>
          ^~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/sdl-jstest.dir/build.make:63: CMakeFiles/sdl-jstest.dir/src/sdl-jstest.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:105: CMakeFiles/sdl-jstest.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

mitu

@ilpappa said in Emulationstation issue - idle game selection change:

I could not see any ghost input during the several hours of test, from both joysticks, so all went fine.

OK. Do you get the same behavior if you disconnect the gamepads completely or use a different gamepad ?

Apparently other people are suffering same issue by looking online, of course only in emulationstation Emulation Station menu phantom scrolling .

A 7 years old post where 2 of the posters identified the issue as hardware/controller related (see here for a a similar issue caused by faulty controllers reported in the forums). I'm not sure there's a bug since I can't reproduce this and I imagine if it were a widespread issue the forums would have been full of similar reports.

Not sure at this point what to do, other than drestroying my cab :D

Not sure either. If it's a bug, it's related somehow to your configuration, but can't think of anything that would cause this outside of ghost inputs from the controller themselves.

ilpappa

First of all a BIG thank you @mitu for the time you're dedicating for my issue.

I'm back after several fix attempts which were unsuccessfull. I tried to:

Replace pi4 with brand new -> same issue
Replace JammaPi with brand new -> same issue
Disconnect all USB devices from the pi (I have three extension cables + keyboard receiver) -> same issue
Re-wired my Jamma making some improvements (ie finally fixing the ground loop, bridging GND points together, using video ground, etc.) -> no ground loop anymore + better images but same issue as above
Changed microswitches with cheap china (I have good DX44) -> same issue

Now the cherry on the cake is that I actually disconnected Joystick 1 except the axis and all buttons of Joystick 0 except axis, x, start and coin 1, but got same issue. Curios thing is that in the log I see many ghost Joystick 1 inputs despite being disconnected...how is this possible?
Another wierd thing is that my phisical buttons go from 4 to 10, but log shows input for buttons 1 and 2...where does this come from?

Log here, check from Jan 24 00:43:33 lvl3:

I could not think of anything else...I'm going to receive a new PSU with better quality, will try that as well but I've basically rebuilt the whole thing.

Any ideas?

EDIT: forgot to mention that with the above improvements my stable build on buster gets issues only after >10mins of video snaps running, while the test build on bullseye take couple of mins to show the issue.

mitu

Sorry, I have no further ideas besides what I've already written before.

My idea of disconnecting was to completely disconnect the devices and use a keybooard or an USB controller only just to see if any ghosting still shows up.

ilpappa

@mitu

Thanks. I can do full disconnection but need to do couple of modification on the wires. Nothing complicated but at this point what this test could tell us?

Many thanks again.

mitu

@ilpappa said in Emulationstation issue - idle game selection change:

Nothing complicated but at this point what this test could tell us?

Whether the 'ghost' inputs are caused by your inputs or there's a bug in EmulationStation caused by your config/rom list.

ilpappa

@mitu
Completely disconnected both controllers and used Keyboard, but issue persists. We can def agree that this is a bug somewhere then.

ES Log

Is there any setting in emulationstation I should consider doing? All video snaps/screens have been fetched via Skraper, is there any particular setting I should be using there as well (I'm not super familiar of the skraper but was quite intuitive on how to be used)?

Many thanks

mitu

@ilpappa said in Emulationstation issue - idle game selection change:

Completely disconnected both controllers and used Keyboard, but issue persists. We can def agree that this is a bug somewhere then.

From the log, I see the joysticks are still detected and there's still input being processed from them. Are these (JammaPi) using a special driver ? How did you configure them in Linux ?

ilpappa

@mitu

Probably they’re still detected because the microcontroller sits within the GPIO->Jamma board and of course I’m not able to disconnect that.

I’m not sure about the configuration, this is the script used for the installation where I’m sure the answers are. Apologies but my linux knowledge is quite basic. If you visit the link you’ll be able to see the code which seems not complicated.

https://github.com/vince87/JammaPi/blob/master/install.sh

Images of the board here:

https://www.arcadeitalia.net/viewtopic.php?t=30495

Thanks

mitu

Try removing the kernel module joypi with

sudo rmmod joypi

maybe this stops any processing done for the inputs.

ilpappa

@mitu

that command solved the issue. No more ghost inputs. But of course no joystick input.

Is there anything I could do more to fix the root cause?

Many thanks

mitu

Is there anything I could do more to fix the root cause?

At this point I think the bug is in the joypi module - you should report this to the author of the module and ask them for further support. Maybe there's some additional configuration that would fix this behavior or even a patch to stop the ghost inputs.

ilpappa

@mitu
Thanks. The project seems abandoned but I’ll try to seek for some support.

I just realized I have a coin counter connected to my two coin purses which has a diode on the 12v which seems to be shorted. You might recall that some users reported long time ago ghost inputs due to issues connected to 12v. You think the diode is a path worth to be explored? Many thanks!

mitu

@ilpappa unfortunately I'm not the one to give advice about electronics - I don't have enough knowledge/experience.