I think I screwed something up on the pre-made retroie image. Because I re-flashed the pi and set I2C to be loaded through sudo raspi-config, now when I reboot it does detect my I2C. One step closer to my mobile retropie!

Don't use pre-made images, they're terrible. Plus you won't get any support here or anywhere. Since I like to help anyway, I'll give you a hint: the most likely issue is that the init file is missing, the image is corrupted and you can't do much unless you reinstall over (and completely mess the messed up setup). Another possibility is that there's an easier fix by running e2fsck on Putty but I hightly recommend to give up and build your own fruity cake :)

@mitu Thanks for the help, without your help I would have been stuck in the kiosk mode

@Thorr69 said in The Neo Geo emulator does not find the bios: @Rubencn1234 Put it in the same directory as the roms. If you put it in the BIOS directory, it doesn't seem to find it. I had to put it in the roms directory (with the correct name) in order for it to work. Which emulator are you using? FBA works fine without "neogeo.zip" in the roms folder. I have it just in the BIOS folder. @Rubencn1234 Check to make sure you have the right BIOS file. neogeo.zip needs to be ~1.5 MB and CRC-32 should be 20F12195

@bagoflaxia said in mpg123 player works fine for BGM, but kills game audio.: Is there a command I can put in to the mpg123 config to stop this from happening? There is a topic on how to set this up in RetroPie - https://retropie.org.uk/forum/topic/9133/quick-and-easy-guide-for-adding-music-to-emulatonstation-on-retropie-noob-friendly. Follow the instructions in the topic and add the commands to stop mpg123 when a game starts by editing the runcommand-onstart.sh script, this should stop the music from playing while the game runs.

@jonnykesh I apologize. I was in a hurry and it kept telling me I needed someone else to

OK, so I've been googling up a storm looking at the options. I think I'm either going to go with a piglow, and use some code folks have already put together. Seems like the three arms can show something like Temp, CPU Load, something else (I can't remember). But what really looks like it'd be cool is the Displayotron. Seems I could set it up to show the system and ROM running on Retropie. And I figure the backlights could be setup to have a color that'd match the system (like Red for Nintendo or something). And then use the bargraph to show CPU load. But what I'd love to do is use the joystic on the Displayotron as a safe shutdown button. Could I do that? Does it sound at all reasonable?

@ithortureu alternatively you can just use a program like WinSCP to add roms etc. https://github.com/retropie/retropie-setup/wiki/Transferring-Roms

@mitu @davidgrohl Thank you guys! Unfortunately I have already ported from scatch

@reeebs said in [Rpi3] NDS touchscreen: I don’t expect nothing in particular, as the two positions - the real one of my finger and the one of the pointer - are completely wrong: if I move, it moves too, but when I am in a corner it starts from the center and so on That's very telling behavior and explains why the Dolphinbar wasn't recognized. The touchscreen is apparently being read in this case as a standard relative coordinates mouse. If it were being read as an absolute coordinates pointer device, the cursor would snap to wherever it was you touched at. Needless to say, this limitation combined with the wide area required to receive input really hinders precision.

@dankcushions Thank you !!

You could also just add them to the gamelist entries for each game?

Hope it helps someone! I tried to get the mouse to work as a Zapper. It just wouldn't work. End of the story: I had to unplug the USB-dongle of my remote control, because it had a mouse functionality. I think it had a conflict with my wireless USB mouse. Afterwards I changed mouse index to 0 in lr-fsceumm under Controller 2 Input and changed the type to Zapper. That's it!

@edmaul69 alright tnx guys i attempted this and it work :) tnx for the help guys i guess i didn't clean it well the first time

took your advise, made just one partition. thanks a lot programing pinn or noobs needed more work (https://github.com/procount/pinn/wiki/How-to-Create-a-Multi-Boot-SD-card-out-of-2-existing-OSes-using-PINN) Followed this fella on you tube who tells you how to boot from the sd card without a boot program, just rewriting a file, and the image is now working, now i'am enabling the unallocated space that's left in the drive to add more roms and media. () thanks mitu !

@swd120 Not sure about Hotline Miami, but those other two games run absolutely fine on the Pi 3. I was playing Powerstone only the other night funnily enough. Very impressive on the Pi. Not to be a Pi fanboy (well OK maybe a bit!) but the problem for me with buying these alternative boards is we think we need more power to run emus for N64 and Dreamcast or that that would improve things, but ultimately it won't offer a dramatic improvement to the end user over a Pi 3. N64 is not really a friend of anyone unless you are running GlideN64 on a fairly powerful device and even then it's not that great (trust me I know). I agree GlideN64 is driving N64 emu right now, but you have to realise that it is becoming more demanding as development continues. Going on my own experiences it has had a very chequered history on my Android devices, where it used to run well on a decent spec device (Tegra 4, 2Gb RAM, but now is beginning to show slowdown even on the lower settings and after user amendments to settings. Heck it used to run OK on the Pi 3 when it was Glupen but not really so much now. I assume this will not get easier over time and ever more powerful devices will be needed to run it. Reicast simply hasn't had an update in many years and is again not really worth changing over from a Pi 3 for. Until this sees a considered update it's again not worth chasing. Just imho.

@julianconde https://retropie.org.uk/forum/topic/3/read-this-first

@retrofreak89 said in Is it better to have a fan blowing on the pi or blowing out?: @xeon my case has holes at the bottom so it blows onto the arm CPU then the air goes underneath and out the case When it sucks the flow is spread over a large area. When it blows the flow is aimed directly at the cpu. So a larger amount of air hits and pushes away heat when blowing directly on the cpu. However blowing increases dust build up and sucking decreases it. Choose wisely.