Installed 4.0 retropie...now no shutdown..

BuZz

@PetroRie said in Installed 4.0 retropie...now no shutdown..:

This new 4.0 version is buggy as hell. PS4 controller doesn't work in the Megadrive emulators, some Neogeo games stopped working while they did work under an older version. Before I updated it for the first time everything worked fine. And now even on an older version I cannot use the PS4 controller on Megadrive emulators. So yea as you can see I have the same problem as you.

Well, if the old version which did work now doesn't work - it's likely you have broken a config or something. If you have a problem with neogo you can open a topic - my neogeo games all play fine. Wrong romset ?

PetroRie

@BuZz Thanks for the suggestion. I will do a fresh install tomorrow, and I won't use the backup retroarch.cfg instead I will edit the new one. I'll let you guys know how it went.

Ranma

New to forum, incredible application! Thanks for the amazing work done. :)

Just wanted to say I'm having a similar issue to the OP. Fresh install on a RPi 3, couple of configs edited to get sound from my TV, bit of scraping and setting up a PS3 pad. Nothing dramatic. But when shutting down Retropie it goes to a black screen with a blinking cursor. Now if I leave it it does eventually turn off, but it is very slow indeed and didn't occur on previous releases. I hope this is useful to you. :)

BuZz

@Ranma @chippettone

I think the problem is you have a lot of meta data (eg scraped systems).

It's worth having a read through the documention on the wiki as a lot of stuff like this is already covered

https://github.com/RetroPie/RetroPie-Setup/wiki/FAQ#why-does-shut-down-and-reboot-take-ages

Older RetroPie quit without saving meta data so it was technically bugged before. You can disable meta data saving on exit if you want a fast shutdown.

@Ranma also thanks for the kind words :)

Ranma

@BuZz said in Installed 4.0 retropie...now no shutdown..:

@Ranma @chippettone

I think the problem is you have a lot of meta data (eg scraped systems).

It's worth having a read through the documention on the wiki as a lot of stuff like this is already covered

https://github.com/RetroPie/RetroPie-Setup/wiki/FAQ#why-does-shut-down-and-reboot-take-ages

Older RetroPie quit without saving meta data so it was technically bugged before. You can disable meta data saving on exit if you want a fast shutdown.

@Ranma also thanks for the kind words :)

Kind words are the very least I can offer considering the joy this project gives. :)

Thanks for the heads up re: meta data saving. I can cope with a slower shutdown as long as I don't lose my stuff. ;)

chippettone

I have disabled the metadata but does not change anything. Does not turn off. The blinking cursor remains even after 30 minutes. If I put on the sd clean image and do quick installation, when you restart the problem. If you put up the version 4.0 rc2 or 3.8.1 operating normally. It looks like a bug in version 4.0 final. Beyond this point out even the inability to configure the USB joypad xbox 360 as the trigger keys are not recognized. Furthermore some emulators do not fire up the Roma, including final burn, neogeo and mame 2003, they worked previously. Get back up without waiting for bug updates.

BuZz

@chippettone

There might be something wrong with your filesystem/image - I have not seem those problems.

What is the output of cat ~/.emulationstation/es_settings.cfg from a terminal ?

The issue with FBA/NEOGEO might be because you haven't updated your romset and we ship with a newer version of the emulator - see https://github.com/retropie/retropie-setup/wiki/FinalBurn-Alpha.

I am not aware of any problems with lr-mame2003 either - and no-one else has reported a problem - I would need to more information to help.

Xbox 360 configuration does work (I have a controller here) - I would need more information to advise. It is tricky to configure the triggers without the updated xpad driver.

Did you install from an image or did you do an upgrade ?

Please refer to https://retropie.org.uk/forum/topic/3/read-this-first as to what information to provide when getting support. thanks.

chippettone

As for the configuration of the xbox360 joypad I have eliminated xboxdrv modules, and now works perfectly. Likely joypad driver conflict. Then they also worked the controls on other emulators. I did it again but the problem remains off installation, but only on version 4.0. However the problem of joypad configuration exists only on xbox360 joypad and owner drivers. The problem is that when it prompts you to press L1 and R1 buttons and then L2 and R2 does not accept the command and jumps option. The useful thing would be to return the option and try again but you can not be reconfigured and all over again. In an old version of retropie, I think it was 3.2, the menu was an option that was made out a configuration of dos input type questions. In that configuration everything worked properly. Then it was removed as an option from the menu retropie. It would be nice to put it back in the next upgrade.

suprjami

@chippettone The X360 L2R2 configuration problem you describe is resolved in 4.0 with an xpad module option that changes the analog triggers into buttons.

If you need to add the module option, this should do it: echo "options xpad triggers_to_buttons=1" >> /etc/modprobe.d/xpad.conf and you'll need to reboot then reconfigure controllers after that.

A workaround for the old issue you describe is still documented here: https://github.com/RetroPie/RetroPie-Setup/wiki/Logitech-controllers#l2r2-top-triggers but we have removed it from the X360 config page as it is no longer required as of 4.0.

BuZz

@suprjami said in Installed 4.0 retropie...now no shutdown..:

@chippettone The X360 L2R2 configuration problem you describe is resolved in 4.0 with an xpad module option that changes the analog triggers into buttons.

If you need to add the module option, this should do it: echo "options xpad triggers_to_buttons=1" >> /etc/modprobe.d/xpad.conf and you'll need to reboot then reconfigure controllers after that.

This is set up by the xpad driver in RetroPie-Setup, but it will have no effect unless that driver is installed (the option may exist for the shipped kernel xpad driver, but it will only apply to unknown joypads. I patched the updated xpad driver to make this apply for any joypads).

If the user has updated from 4.0rc to 4.0 final, they will need to install the new driver from Manage Packages -> Drivers -> Updated Xpad Driver

I'll get back to my forum break again now :) - just wanted to clarify this in case the OP hasn't installed the updated driver (which it looks like).