@Clyde Could be event 0, the code itself uses just the SDL slot, so whatever SDL picks up as slot X will be picked up. There are multiple event emitting files for a single joystick (JS and evt, the code states it uses js), but thankfully SDL isolates that so that you dont have to deal with this yourself.

I did not change the general registration logic itself, the heavy lifting towards the inputs is done via sdl. All I have done is to remove the hardcoded zero to something which can be customized via a command line option, a really harmless and small fix for an annoyance which is 8 years old.

As for the original developer, I could not pull off what he did, not my area of expertise, its just that there must have been some serious personal reasons not to finish the last 0.005% of the work when he already went as far as he did.
Nevertheless, this annoyance now to some degree is fixed (I´d rather prefer to have some kind of device pattern filter instead of a number, but atm I lack time to implement such a thing)
I just fixed the number scheme for my personal needs.

@mitu

I solved by changing only the resolution with the one on the read me that you showed me ...
the problem was that I had set the resolution not compatible with that of the theme

@Furluge yeah i was the reason that raphael learned about the issue which affected a crap ton of controllers. Then he so awesomely found the bug in linux and created the fix for it. But yeah its been fixed for a long ole time. 😊

Also, thanks @simpleethat

@hansolo77 You can place a file named sshto boot directory. This will enable ssh, too. I hope that ssh is enabled by default on next release ;)

Update: Solved!

After the dist-upgrade all packages we installed but still needed to run "sudo dhclient" to get networking..

I then removed policykit-1 and reinstalled network-manager
and that did the trick!

@George-Spiggott thank you

the xml entry is the same for me

i don't know what is the problem

@taiJones00
So does the wireless work on the game girl? It would be cool to write a script to easily disable and enable it to save power.

Is the hdmi port still accessible? and then you might be able to sync a wireless controller and play on a tv.

The RPI3b+ can get hotter than any of the other models, I wonder if installing a fan would be possible. Of course that would use more power, depending on the emulations you want to use, it would be easy to down_clock the cpu and benefit as well.

it has to be a bravia

@Efriim Yep. I'll handle the rest of the research. You've done more than enough. Thanks bud

Tried it for some days now, seems to work!
Thank your very much barbudreadmon!!!

@psyke83 said in DOSBox does not detect axis 4 or 5 on PS4 and XBox 360 controller:

@JemyM said in DOSBox does not detect axis 4 or 5 on PS4 and XBox 360 controller:

@psyke83 said in DOSBox does not detect axis 4 or 5 on PS4 and XBox 360 controller:

Please test and report on whether the joystick binding patch (as well as dosbox in general) works as expected: https://github.com/RetroPie/RetroPie-Setup/pull/2646

I am not good enough. I was able to follow Dudleydes instructions above and that worked, but I do not know how to get this patch to my retropie. I tried to update "dosbox from source" but that did not work.

The PR already been merged, so update your Retropie-Setup script and then update dosbox to get the patched version.

Have you tried dosbox-sdl2? It might have better joystick handling.

I forgot about this because I updated and I can verify that it works. We are not using dosbox-sdl2 in our keyboard 2 joypad project since its not needed. The keyb2joy.pad project document and index keys assigned to functions. We basically fill in columns with the keys used for things like "jump", "move" or "fire". I have then made an utility that produce authentic DOSBox .map files with full Retropie-support based on these profiles. So far we made 550 platform games fully playable on joypad and we are 20% through the 600 shoot-em ups on the DOS platform.

@Mrtay101 One simple way would be to enter mc in the text console. This should start the file manager "Midnight Commander".

In it, you can navigate with your cursor keys, enter directories with Enter and going back to the former directory by entering the .. in the first line of the file list.

Using this, go to the directory RetroPie, then roms, then to the resp. system directory of your roms (e.g. arcade for arcade roms) and you should see your roms. Select the ones you don't need with your Insert key and delete them with F8. But be careful, deleted files can't be restored! (or not without extreme effort, if at all)

After making some space, leave mc with F10 and reboot your Pi in the console with the command sudo reboot.

You can find a more elaborate guide to mc here: https://www.thegeekstuff.com/2008/10/midnight-commander-mc-guide-powerful-text-based-file-manager-for-unix/

edit: Oh, and please change the title of this topic to a more descriptive one by editing your first post. There, you can change the title, too.

@Efriim Doing this step by step only:

https://retropie.org.uk/forum/topic/16145/retropie-upgrading-raspbian-jessie-to-stretch

After finished there are some errors in libraries that made crash emulationstation but they are easy to solve. Once it runs very well including with overclocking. With this fan “Noctua Premium Fan, Brown, NF-A4X10-FLX 5V” I could overclock and no problems.

Kinda sucks all around. I love both sides here. I've been with the RetroPie group for a couple of years now. I make one little comment about how I wish N64 games ran better on the Pi3, and I got a reply back almost instantly about trying this "Odroid XU4" and the Odroid Arena build. I'd never heard of it before, and thought I'd check them out. I myself made the assumption that this build was still in it's fragile infancy, and bolstered my arrogance around their Discord channel like I owned the place. I had thought that my growing knowledge of how RetroPie works, and how to make things work with it, would help their community advance. I thought I came across cool and helpful but it was mistaken as an arrogant attempt at making the guys over there feel inadequate in their development. Because of that, I was temporary banned from their channel, and muted from their Facebook. I was completely wrong and have come full circle. My knowledge, in fact, is primitive to what the guys over there know and have been doing from the ground up. They've taken a device and built upon it with what they have available, and have come up with a working system that is as good as (if not better in some areas than) the current release of RetroPie for Raspberry Pi's. I've become humbled by the staff and have been trying to assist that community where I can. There are issues, yes, but it's something that is being worked on daily, just like how RetroPie is. They aren't focused on developing for just one SBC either. Think of how LibreELEC is developed to provide Kodi to many devices, not just Pi's. This is where their team has gone too. Yes, RetroPie also supports other devices, but RetroPie falls short in their support. You provide simple instructions on where to start then leave the user in the dust struggling to find help by saying things like "it's YOUR problem" or "contact Odroid". The problem isn't always related to the hardware.

Anyway, I just wanted to say that I think it's great what both sides are doing for the community. Sure, better support is needed, but that's no reason to say the team is producing "ugly hacks". We need to work together, not distance ourselves further apart.

There, I've said my peace. Long Live RetroPie and Long Live TheORA!

@2fst4u
You can use the fstab to mount server shares on availability as well but I have never done this. Nor have I learned about layering filesystems.
the ubuntu fstab help page, example
//server/share /media/samba cifs user=user,uid=1000,gid=100 0 0

The PR was merged, so it's safe to go back to the master branch if you were testing. Don't forget to updateruncommandafter returning to the master branch (which is done automatically when you use the Update RetroPie-Setup script option of the script itself).

Thanks to @mitu and everybody else who helped with troubleshooting & testing.

@Efriim said in Installing Retropie on Raspian RPI3 B+:

Will the new OpenGL drivers ever be compatible, is it up to emulationstation devs? or will the emulators not work too? Does Pegasus-FE work with Opengl?

Most of the emulators (and Emulationstation) are using the - native - OpenGL ES stack available on RPI, which doesn't need an X.org and has direct hardware acceleration. IMHO there's little advantage in using OpenGL instead of the native stack, but I haven't run any benchmarks.
The downside of using the - new - OpenGL driver is that certain utilities that rely on the native driver (tvservice for instance) might not work and functionality that's right now included in RetroPie would not be available.
You can find the original discussion here.

@fastpop72 for what it's worth, i opened an issue about it last year : https://github.com/libretro/reicast-emulator/issues/232 , i think yours is related.

@Efriim no I haven’t tried that game. Thanks for finding the forum post about standalone psp exiting back to emulation station rather than the psp menu. Good to know since that was my main issue using standalone. Using the retroarch version now seems like a more viable option than it was before in terms of performance based on my testing and it is nice to have the GUI. But i will try this out on my experimental setup to try to confirm it works.