RetroPie 4.3.17 Stretch images
-
I'm having some difficulty with lr-prdoom. It works mostly fine and goes in game, but for some reason, my weapon is constantly being swapped out, even when I remap those controls.
-
@gomisensei what size of USB did you use?
Makes me wonder if its possible to have a small as hell sd card for boot only, with the USB having all the retropie and kernal data
-
4.3.17 images are now on the first post.
-
@buzz thanks. What are the high level changes between 15 and 17?
-
@pjft you would need to check GitHub history sorry. Not at home.
-
This has probably already been answered so apologies in advance but -
Can I put 4.3.17 on my 3B as well or is this a 3B+ only build?
-
@classicgmr You can put this on your 3B.
https://drive.google.com/open?id=1ZV-PzX1VBSKqtqAxWl5FE6wh5PRaohxU
-
Hey guys, Im fairly new to the pie scene. Just bought myself a pi3 Bplus, i was just wondering if wifi is able to work or can I plug it into a router to transfer my games?Edit: Just read the post regarding wifi, gonna try that to see if it worksThanks,
Duck -
You are not alone:-
https://retropie.org.uk/forum/topic/17049/lr-prboom-weapons-keep-cycling
-
Any update on the Shanwan controller problem?
-
@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. -
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....
-
@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
-
@mroy1300
I would say just update retropie, and install customhidsony from the driver packages. You may need to reboot. -
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.
-
Just wanted to say I've been running this on my B+ for about 2 weeks now and haven't come across any hiccups!
-
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:
-
Is the beta image going to be updated before release?
-
@jlachniet all you gotta do is open the setup script, update and tada!
-
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?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.