The documentation page needs to be rephrased - while some emulators only have a 32/64 bit version, RetroPie works on both x86 and x86_64.

@mitu said in Installation of Mamedev MAME:

@George Create a PR on the Retropie-Setup repository - github.com/retropie/Retropie-Setup.

Thanks @mitu. I just submitted a pull request. Had to do a little file cleanup to eliminate some previous versions I had committed under the same branch.

Thanks again for all the help!

- George

A lot of this functionality is built in

eg. on your ubuntu machine

sudo ./retropie_packages.sh crosscomp setup stretch

then on the rpi3 just install distcc, configure it to use Ubuntu machine.

for building:

PATH="/usr/lib/distcc:$PATH" MAKEFLAGS="-j4 PATH=/usr/lib/distcc:$PATH" ./retropie_packages.sh etc

note settings the PATH for makeflags is needed for some modules to use distcc.

retropie also includes the facility to build raspberry pi binaries on an x86 Ubuntu machine using an emulated chroot and the distcc on the host. see the "builder" module.

Doesn't matter, I worked it out. I had the <folder> tag placed in the wrong place.

Regards,

@ziggurat I got carried away by looking at neofetch and got this

b17c8604-9f05-4eec-b669-034d12abba2a-image.png

It's a bit large though for a 64x80 standard Linux console.

@sirhenrythe5th oh you didnt upset me at all. I was just voicing my opinion.

@GrandMasterLynx I've written a small script SavePath that does the work for you. Read carefully the instructions!
For the setup you want with the /home/pi/RetroPie/roms/<system>/saves/ feature you would use

SavePath.sh all "/home/pi/RetroPie/roms/$1/saves"

You need to activate the two save key in retroarch.cfg with nano /opt/retropie/configs/all/retroarch.cfg if you use the all parameter.

savefile_directory = "" savestate_directory = ""

@hhromic I think if this solution can be confirmed by others then the wiki can be updated. Yes it was my intension to conserve this with a forum entry.

I think the pairing itself does not need to be explained but the fact HOW to enable pairing mode on the controller. Because you often read just ... Hold select for more then 2 seconds.... that did never work for me. And the ZERO is a bit underestemated but is really nice for kids, pygmies and hobbits.

EDIT: Kudos for you - quick snippets are real time savers ;)

@Xabib2302 Care to give more details about this format or examples for which System/Emulator should this be added ?

Although, as being late to the party, here are my 0.02 £:

If you want to promote Retropie as project best is (IMHO) to wear a retro shirt of a popular (or your favorite) console/arcade game or brand. To this people can relate and it's easier to engage them in a conversation in which you can interweave the benefits of Retropie.

My personal experience is whenever I am on a social event with my Pac Man / Xevious / C64 / ... Shirt, people start asking me about my shirt.

To actually support the Retropie Project, either: spend them money (Patreon, Bitcoin, Paypal, aso.) (good), do testing and bugfixing, documentation (better), foster the codebase by feature extensions (best).

At the end of the day that's why the Raspberry was invented: To empower yourself by learning and doing stuff.

Plus: Preparing and merchandising Retropie specific stuff would use precious hours of the project owners, which -as a reminder- do the Retropie project as a hobby.

HTH

I got this HDMI detect or LCD working good.. It takes a while before the script kicks in.. Maybe it should go in rc.local instead?
Opinions?

What I also need to do is have a LCD profile Start Roms without game frame/boarder . Rather have it expand full LCD and use frame when using HDMI..
Any ideas?

Thanks so much

@ferhound is it hard to understand that you're asking about something that's completely not related to the topic at hand, which dates back from 2017, and try people are trying to help you based on what you initially stated ("when is this available") where you clearly didn't understand what the topic was about, and yet still expect people to have an answer for something that doesn't exist in RetroPie?

Tone was not exactly deliberate, but really: @mitu is trying to help and so was I. If you don't do your homework or participate in a clearer manner, it's hard to help you better.

You resurrected this topic, the answer you got relates to it. Don't expect that RetroPie users necessarily know what new features other projects have, so you will have to explain in more detail on occasion if you'd want to be effective at interacting here over non-RetroPie-specific topics. Not because we have anything against other projects, it's really that not a lot of people actually actively follow other very similar projects.

Long story short: that feature as you described isn't available on RetroPie. If you do have documentation or links about it, though, and would want to share, I'm certainly curious about how they do it. It does look nice from your description.

Best.

Update: Please use PR 560 (note the 6) from now on for testing. Needed to reapply PR since fork and upstream diverted too much. So:

git clone --recursive https://github.com/RetroPie/EmulationStation.git cd EmulationStation git fetch origin pull/560/head:event-scripting git checkout event-scripting cmake . && make ./emulationstation --debug

@andku85 there are a bunch of working solution already posted in this forum as @mitu already said - best way would be the officia l script from the case producer. You can search for multi switch script for another working solution but this needs some editing skills

@mitu Of cours, but then you mess up your rom set.

On the other hand some systems or naming conventions use rom sets which have names which are not unique. (I don't find one at the moment, but i saw such discs)

e.g.
"<Game>.cue"
"Track1.bin"
"Track2.bin"