@obsidianspider said in Boot Problems with Pi 3:

Running a Fan from GPIO can cause issues as they tend to draw quite a bit of current. If you have a spare SD card, try using that to see if it works before you reformat your existing SD card.

Its a really tiny fan, like the smallest you can buy, smaller than a quarter.

Anyway, I tried a spare sd card and put the newest retropie image on it with the fan and led plugged in and booted up fine, still does the text then splash then text again then into emulation station but quickly and with no issues. Never use to see the text twice, only once before the splash screen, must be new?

I guess my other sd card is corrupt somehow now.

@MennoSteenwijk said in Best raspberry pie for retropie:

After installing Retropie on my Raspberry pie 1 I encounterd some issues in the speed of the pie while trying to play for example Mario Kart N64

On the wiki, it says:
Note that you need a Raspberry Pi 2 if you want any decent N64 performance and even then it is hit and miss.
https://github.com/retropie/retropie-setup/wiki/Nintendo-64

Just arrived to RetroPie and still trying to configure my devices, after reading full topic here are my two cents:

unistalled PS3 Driver (clone) Paired Sony official PS3 bluetooth controller successfully Installed PS3 Driver (clone) Connect PS3 Clone Gamepad on USB then disconnect Push PS button to connect Gamepad. All done :)

At this point two devices works properly. I can change from retorpie to kodi and back again and all its fine. Just played some games on joypad, exit retropie onto kodi, navigate using keyboard.. all fine !

But... after reboot, bluetooth keyboard can't be paired again. I need to start over again from point 1.

the question is: It's possible on boot process, disable sixaxis while normal stack connects to bluetooth keyboard (or other devices) and after some time (maybe 1 minute) reenable sixaxis again?
How is started bluetooth device during boot? and where are the scripts?

Any advice are welcome if someone has tryed something like this.

Obocaman

@OldDucGuy I just run the parent

@Floob yeah i'v always used the crt pi shader, love it. but all those overlays, they're so.. cosy! Nostalgia is one helluva drug.

Another step forward! These are my controllers default calibration values:

jscal -s 18,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,0,0,536870912,536870912,1,0,0,0,536870912,536870912,1,255,-4208,3952,21931,21931,1,255,-4208,3952,21931,21931,1,255,-4208,3952,21931,21931,1,63,-1023,1023,87367,87367,1,63,-1023,1023,87367,87367,1,63,-1023,1023,87367,87367,1,0,0,0,0,0,1,0,960,960,559240,559240,1,0,471,471,1139853,1139853,1,0,32767,32767,16384,16384 /dev/input/js0

And this pacifies the gyroscope's axis. I don't need them and they cause endless events if not "deadzoned":

jscal -s 18,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,0,0,536870912,536870912,1,0,0,0,536870912,536870912,1,255,0,0,0,0,1,255,0,0,0,0,1,255,0,0,0,0,1,255,0,0,0,0,1,255,-0,0,0,0,1,255,0,0,0,0,1,0,0,0,0,0,1,0,960,960,559240,559240,1,0,471,471,1139853,1139853,1,0,32767,32767,16384,16384 /dev/input/js0

Unfortunately there is no way to calibrate /dev/iput/event0, but /dev/input/js0 (jstest /dev/input/js0) is completely silent now if the gamepad isn't in use. This should be good enough for me, as even SDL might be forced to use /dev/input/js0 (export SDL_JOYSTICK_DEVICE=/dev/input/js0).

Next step would be to recognize for how long /dev/input/js0 showed no action. Any ideas?

User here was able to get it configured fine in ES - they had to tweak their retroarch joypad configuration though for it to work with games - https://retropie.org.uk/forum/topic/2097/controller-does-not-work-in-games

@obsidianspider Good to know. That's the conclusion I came to. I made my backup this morning and installed a driver for a highly rated (and free) app called Unified Remote. Need to experiment with it when I have time, but it did connect briefly. Seemed to be a wifi connection issue of some kind. Will post my results here if I can get it working properly.

I just want to be able to pick up the phone and type "esc" when and if necessary, that sort of thing. Unified Remote app provides a full keyboard with command keys, arrows, etc on the phone.

Then I'll try to upgrade to version 4.0. The UI and functions have improved a lot comparing to 3.3.

@redlv mark your topic as solved then.

@meleu Do you know a other way?
If you do can you give me the commands or the steps?

Found the problem!

The PCSX-ReARMed.rmp file in /configs/psx/PCSX-ReARMed folder had only configurations for player 1, so I just duplicated the lines for player1 for player2.

Not sure where the wrong configs come from, but this overrides them.

I found a way to reset controller settings finally and now I can setup my controller from scratch :D

There is reports that the PS4 gamepads, with the latests kernels/bluetooth stacks doesn't work in Kodi. Hopefully it will work in Kodi 17 which will have oficial gamepads support for the Raspberry Pi.
Till then you can disable gamepads support in System -> System -> Input Devices, that way you should not need to disconnect that gamepads.

Try to use the correct romcheck, if doesnt work, try with load the rom with fba-next, if not too, try to load with advmame (to configure your joypad press TAB), it happened to me with Night slashers (tryed 4 rom version, .78 romset and only advmame 1.4 launch the Night slashers korean 1.3v rom).