RetroPie 4.3.17 Stretch images

itsmedoofer

You are not alone:-

https://retropie.org.uk/forum/topic/17049/lr-prboom-weapons-keep-cycling

mroy1300

Any update on the Shanwan controller problem?

Sano

@mroy1300
You sir, are maybe lucky :
https://github.com/RetroPie/RetroPie-Setup/commit/91377a63f5a58a89d9c5b23c1f49ac9bea41c6b4
I don't know if it's the issue you have, but there sure has been recent improvements.

itsmedoofer

@jlachniet

I've found a hack to fix this until it is sorted properly...

Replace :-
/opt/retropie/libretrocores/lr-prboom/prboom_libretro.so
With the one located here....

https://buildbot.libretro.com/nightly/linux/armhf/2018-04-10_cores/prboom_libretro.so.zip

Not extensively tested but it seems to work OK....

mroy1300

@sano
At the risk of sounding like an idiot...

I'm not sure what to make of the link. I see that people are using the psyke83 4.14.30 PR but I'm not even sure how to use that to be honest :(

Is there a tutorial on it? My google-fu seems to be lacking... Or there is no info out there on GitHub Pull Requests but I doubt that lol

Sano

@mroy1300
I would say just update retropie, and install customhidsony from the driver packages. You may need to reboot.

mroy1300

@sano

Thanks I'm currently flashing my 128GB image that I updated to stretch. I'll see if it's listed in the driver packages when it's done. Otherwise I'll check the 4.3.17 fresh install for it.

I appreciate your time. Hopefully this helps more noobs before the official 4.4 image gets released :)

Update:
I got the PS3 Shanwan controllers working. It's worth mentioning that after installing the driver you need to pair the controllers by going into the bluetooth menu and searching. While your Pi is searching you connect the USB and Disconnect pressing the PS button.

The "customhidsony" driver can be installed to stop the controller from vibrating when connected with USB.

Much thanks to "Sano" for helping me figure out my issues.

hooperre

Just wanted to say I've been running this on my B+ for about 2 weeks now and haven't come across any hiccups!

matchaman

There's a serious problem I'm experiencing with composite output. Once omxplayer starts within ES (NOT before via shell), heavy system-wide slowdown begins...

I explain the whole situation (including some videos I took) here:

https://retropie.org.uk/forum/topic/17107/bug-omxplayer-on-stretch-based-builds-stutters-on-composite

jlachniet

Is the beta image going to be updated before release?

herb_fargus

@jlachniet all you gotta do is open the setup script, update and tada!

hooperre

I actually have found a (likely) very specific issue.

I'm using a DS4 that now pairs wirelessly with the RP3B+ (yay!). Randomly, the inputs will change from my X button being the input 0 to the Circle button in ES. (Edit: I'm 87% certain this change stays in the runcommand screens and Mupen64plus as well.) I have an image file saved that I'm able to revert to that makes things okay (I can upload it somewhere if necessary) but after rebooting and pairing a handful of times it will connect with different default inputs. This has happened to me twice now.

I'm working off of the Stretch beta image and then using the update (all) feature in RetroPie-Setup. After updating, it takes between 3 and 5 shutdowns and pairs for it to randomly connect differently.

The interesting part to me is that, typically, when connected wired/bluetooth with my normal inputs, the light on top of my DS4 lights up a faint blue. I can tell when the DS4 has connected in a way that will cause these input changes because the DS4 will light up a more intense blue color.

If there is more testing I can do/information I can provide, let me know because I have replicated the issue twice. I'll need to do it a third time though to help, because I panic reflashed my SD. Haha.

Edit: Actually, what files would be most helpful in locating the change? I'm assuming it would be the Wireless Controller.cfg file and the es_input.cfg before and after?

JasonBigham

This post is deleted!

Matt-Teix

Im having an interesting issue with the 4.3.17 stretch image on my raspberry pi 3 B. When accessing the retropie-setup or even raspi-config from the retropie menu the screen will go black. Ive also noticed if I'm ssh'd into the pi when the screen goes black the setup options will be displayed on my ssh machine. If i exit the menu from my ssh machine the pi will then display the retropie menu. This seems to happen straight from a boot. I think it started after pairing ps4 controllers through bluetooth or changing themes. Ive tried just using a keyboard and original carbon theme but found it to still occur. I hope this makes sense, thanks!

mitu

@matt-teix That happens when you start ES from your SSH session, but does not happen in regular use.

Matt-Teix

This will happen even if I’m not sshd into my Pi. Well at least the black screen does.

mitu

@matt-teix How is your display configured ? Are you using the normal HDMI video output or other type of screen/connection ? Does it happen with the jessie image also ?

Matt-Teix

@mitu I’m using normal HDMI. It just recently started happening after about 2 weeks of using this image. I think it’ll have to do with something I recently installed. I’ll dig into it tonight and see if I can pinpoint it to something. I’ve never had it happen with my Jessie install but I’ve also have done more with the stretch one. I’ll let you know what I find but thought I’d run it past your brains first.

mitu

@matt-teix If it worked ok after install, then stopped working, there must be a configuration issue. Re-trace your steps and you might find out why - and if in doubt, save your ROMs/metadata/music and re-image the card.

matchaman

Anyone using composite here? As I previously stated, omxplayer within ES is completely busted and verified on clean setups on several devices (3B/3B+) :(