@sleve_mcdichael Awesome, many thanks! I will not bother with it further, then. Not worth the hassle, I reckon.

@geese-howard said in MAME 0.247 in RPi3:

Anyone uses it from https://stickfreaks.com/mame?

There is a spreadsheet showing a good performance using latest build - .0247, however i dont know how to install it.

If you wait a week or so the mame0.247 will be as binary in the RetroPie-Setup and you know it will work for sure without a lot of hassle.

But if you really want to try you can easily use it.
Be aware of the fact that the binary can fail with some distributions.
Not sure it will still work on Buster 10 distributions, but you can try.

If you have already mame installed earlier from the experimental section, which makes sure all dependencies and configs are installed, then you can just download and copy the files from within the zip file to :
/opt/retropie/emulators/mame

Optionally you can rename the old folder, earlier on, from :
/opt/retropie/emulators/mame to /opt/retropie/emulators/mame.bak for example.

You have to do the commands as root with sudo.

@mix_on this is not the required information you have been asked for.
Also the asked verbose-log is still missing.
Here is the link again, please open and read it: https://retropie.org.uk/forum/topic/3/read-this-first

@Threat_Craft-0 generally they are stored in the rom folder next to the game, as a .srm file.

@lukePi-0 you shouldn't be adjusting the retroarch video driver in this circumstance. info on HW rendering in duckstation are here: https://retropie.org.uk/forum/topic/30743/lr-duckstation-experimental-new-playstation-1-emulator - you cannot use duckstation HW rendering on a pi3

i believe lr-pcsx_rearmed has a core option to remove dithering.

@sleve_mcdichael

Hey. Figured it out. The answer was more or less staring me in the face.
In the "es_temporaryinput.cfg" there was a line for the hotkey, which I more or less copied.

<input name="hotkeyenable" type="button" id="8" value="1" /> <input name="x" type="button" id="0" value="1"/>

This is my solution. From what I've tested this hasn't messed up anything else even though it does share the
id="0" with one of the axis entries.

Thanks for the input. You can consider this topic "solved".

@mitu That worked perfectly - thanks!!

@nakynaw

First, try to update the ir-pcsx-rearmed core and check again . instructions:https://retropie.org.uk/docs/Updating-RetroPie/.

If after the update the problem is still there, follow this steps:

To disable the multitap:

Open the RetroArch menu while the game is running and from the options, enable the Show other input settings.
After that, restart the game and open again the RetroArch menu and from the options set to off the Mutitap1 and Multitap2 and you are ready.

@weissnix4711 said in HDMI CEC Remote support, seems there but not working:

Hey, sorry for bumping this old thread, but could I get an update on this?

There hasn't been any new code added for CEC support.

@barbudreadmon said in Asura Buster Game freezing?:

@arcadez2003 Thanks for pointing out it was an issue with m68k intf, i had looked into the game driver and couldn't find the fix.
I did a PR at https://github.com/libretro/fbalpha2012/pull/99, but i believe such change will have a performance cost, even on classic m68k games (additional condition on every cycle, and the code for 68ec020 looks like it'll be slower).

The emu gods giveth and they taketh away :)

@sibsonian said in Migrating a build from RPi3 to Rpi4?:

I know the configs dir will migrate the artwork and ES settings. Common sense would lead me to believe that I would also need to reinstall any optional packages and themes, yes?

Correct.
You will need to install the optional packages that don't come standard on the image.

@uraverageplayer What emulator/game are you starting when it's not working ?
Configuring the joysticks in EmulationStation would automatically create a configuration for RetroArch based emulators (the ones that start with lr-), but certain emulators are not auto-configured (i.e. advmame or mame4all).

Got it working, should have explored the set up more to see I needed to install the USB ROM service.

Thanks

@Shaddonai that is interesting. But I'll being using whatever board has the best performance over clocked And possibly repurposing the old one.

Alright, I've tried Ubuntu MATE 18.04 beta 1 extensively and the problem does not occur on Ubuntu at all. Must be a Raspbian issue. Definitely not my hardware. I hate to dig up a month old topic, but it is what it is. A Raspbian issue.

Please see the following thread : https://retropie.org.uk/forum/topic/18591/asking-for-retropie-login-on-boot-after-update
And don't hesitate to use the forum search engine :)

OK, this is probably my last post on this matter. It isn't solved, by any stretch of the imagination, but i do have a workaround!

I don't believe that the short has fried anything, the controlblock is still working exactly as advertised, but it DID scramble the outputs. All the outputs are still there, just in different places!

If it is possible to re-flash the firmware i think it would restore the normal operation, but that is just a hunch, and as it stands now i am not willing to take the risk.

Just in case someone out there ever has a similar problem i'm posting how i rewired the controlblock:

WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING!

THIS WON'T WORK ON YOUR SYSTEM, IT FIXED MY SYSTEM ONLY. I ONLY POST HERE TO SHOW WHAT THE SHORT DID TO MY CONTROLBLOCK!

In the end i rewired my project to match the new outputs of the scrambled Controlblock as follows:!

MyControlblockOut

Hope that helps, if anyone else finds themself in a similar situation!

END WARNING! END WARNING! END WARNING! END WARNING! END WARNING! END WARNING! END WARNING! END WARNING!

@matchaman
im using HDMI for video and jack for audio, iv' got sound set to "both". im try to change it and we'll see.

edit: i set sound to 3mm jack only and i still hear white noise.

what about alternative sound driver which was available in RP4.3.x ? it could solve the problem ;)