@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.

Hey guys,

Thanks for the response. I formatted the SD card again and reloaded retropie. Still had the same problem so what I did was removed my wireless playstation controllers and plug my hard drive in a different usb port (because it wouldn't boot up without the hard drive in) this time I had a different error message. I turned it off, unplugged the usb then turned it back on without the USB and then everything was back to normal. It's bizarre, but I'm glad everything is back to normal.

Thanks for your help!

Hi both,

Thank you for your responses. Popped out for a couple of hours, and it seemed to have completed. This ties in with the 3-4 hours stated above

(Pi 3 Model B, Overclocked to 1.35ghz)

@Krisu not a good first response to get help here.

How about:

Because I asked you to. It may not be the same issue - cause may be different. Lots has changed in 2 years. The forum wouldn't work if everyone used one topic per type of issue.

I have RetroPie running on a Chromebook running GalliumOS and it works very well. As long as the operating system is Debian-based, you should be ok. Updates take a long time because everything recompiles from source, but aside from that it's fantastic.

When you start a rom and when in game press select + x and look at what driver it uses for audio. I had the same problem with some of the emulators after updating everything. For some the driver for audio was changed from sdl2 to alsathread. I didn't have sound and got the above mentioned underun error.

It needs to be sdl2.

Hope it helps.

@sparcx

Is the system well ventilated? Pi 3s are known for getting very hot while running...
There is a prevention on Pis that if it reaches a certain temperature, it locks up.
It's to prevent fires.

0_1486172717146_smokey.jpg

@BuZz said in Error Creating SDL Window:

The relevant information is

The RetroPie SD image is built on top of Raspbian lite (Raspbian without the PIXEL desktop environment) RetroPie can also be installed on top of the full Raspbian but you can't run Retropie and PIXEL at the same time, you will need to logout of the PIXEL desktop environment in order to run emulationstation and the emulators RetroPie installs.

You may do better with a premade image though - and then install the desktop from there.

facepalm that must be it. I read it and forgot immediately. And of course when I went back to troubleshoot I only read through the step-by-step stuff.

Okay, so excuse my noob ignorance, but how do I "logout of the PIXEL desktop environment" so I can use the terminal only?

@RetroNoob can you see that message on top of every single page of this forum?
I'm pasting here for you:
Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first