Retroarch cores crash on trigger press (Mouse Click) with overlay active

WarC0zes

@SuperJim I'm a beginner for compile. It's possible to share your compiled retroarch with the fix?

SuperJim

I don't think I can upload files here.

roslof

@SuperJim your steps worked like a charm. Feels amazing to finally be able to play trackball games w/overlays. Thanks Jim & all for helping make this fix a reality after so long...

maxbeanz

Does anyone know if this has been fixed yet or do we still have to manually do @SuperJim 's fix above ? I'm about to redo my Pi setup.

mitu

@maxbeanz It has only been fixed upstream, but the fix is not yet part of the RetroArch package in RetroPie.

maxbeanz

@mitu So it's safe to just update RetroArch from source ?

mitu

@maxbeanz No and no. The source update would still get you the 1.7.6 version (before the fix was added) and removing the version tag from the source script would not be able compile the latest dev/master (due to https://github.com/libretro/RetroArch/issues/8448).
I suggest to either apply the patch to the 1.7.6 build or wait for the next RetroArch package release.

maxbeanz

OK thanks, i'll bookmark this page.

One last thing, he says 'enable neon' should be added but it doesn't work for him. Is this going to make much difference for Raspberry Pi 3 ?

mitu

@maxbeanz said in Retroarch cores crash on trigger press (Mouse Click) with overlay active:

One last thing, he says 'enable neon' should be added but it doesn't work for him.

Because the configuration script needs some CFLAGS set to enable NEON for the compiler. These are added automatically by the RetroPie setup script so --enable-neon would work and NEON would be enabled by the configuration script. See here.

Is this going to make much difference for Raspberry Pi 3 ?

IMHO yes.

SuperJim

It's the configure command that fails, with the following message,

Checking presence of predefined macro __ARM_NEON__ ... no
Build assumed that __ARM_NEON__ is defined, but it's not. Exiting ...

I googled around for it, and it sounds like the specific name for this macro may have changed? In any case, the command worked with 1.7.5, but not with 1.7.6; I'm guessing there's a simple change that would fix it. I also don't think the mali option is actually needed on the pi.

mitu

@SuperJim You'll need to run configure with

CFLAGS="..." ./configure <arguments>

and the value of CFLAGS is the one from the link I posted earlier. The RetroPie scriptmodule automatically adds those, since the default compiler options on a Raspbian are more conservative (supporting all PI models).

SuperJim

@mitu thanks for that! I've updated the instructions above.

dudumaroja

hello, @SuperJim `s fix works great fix the freezing when using overlay but break the mame2003 use,, you cant use the full screen somehow the cursor only cover a 1/4 of the screen ( when using dolphin bar ) nes and snes are working great for me.

holto

I also had the issue and am worked through the instructions to compile and copy the patched RA version. Since I couldn't think of a way to cut and past, the long command beginning with cflags was a bit tricky. After several failed attempts I realized the -O2 was a letter "O" and not a zero. Thanks for the instructions none the less. The fix worked with tests in scummvm and arcade(lr-mame-2003 emulated centipede) using a mouse. I have not tried the fix yet on my home arcade which has a trackball instead of a mouse. I expect it will work fine. I thankfully did not experience the problem mentioned above with lr-mame-2003. Thank you all for the work on this issue.

punchout

Hey guys!
I've tried the steps above without any luck.. my apologies.. but I must be missing something. I am using PuTTY!! Any help would be great! Really would like to get rid of the crashing on left click.

punchout

@punchout Sorry where do I find this file.. "using whatever editor you prefer, edit input/drivers/udev_input.c, line 991 and replace," I am using FileZilla

SuperJim

@punchout the error is pretty self-explanatory, you seem to have something called "RetroArch" in your home directory already (could be a file or directory).

Once you resolve that problem, the file mentioned is located in /home/pi/RetroArch/input/drivers/udev_input.c

SuperJim

Unfortunately this issue still seems to exist in RetroPie 4.5

BuZz

@SuperJim yep. It was fixed in retroarch 1.7.7 which we haven't updated to yet.

ChuckyP

Just checking in to see if the fix has made its way into the public release? I have very little experience compiling, but am ready to tackle the task if there is no easy route to update. Thanks.