Forum Replies Created
-
AuthorPosts
-
pi-guyParticipant
Yup, that did it, I noticed that the shuf command at the command line didn’t return a error so I figured I was wrong but had already written the above and hadn’t gotten around to editing it.
sudo cp $(shuf -n 1 -e /home/pi/RetroPie/splashscreens/*.png) /opt/retropie/supplementary/splashscreen/retropie2015-blue/splashscreen.png
I also noticed you used the 00_random_splash directory instead of the one I listed above. I know I changed my default screen once so it could be that I’m wrong with the directory, but I’ve posted the one that worked for me just in case.
Thanks for the help!pi-guyParticipant@g0nz0uk
Not that I’ve seen, I keep hearing that overclocking will shorten the life of the Pi but I didn’t have any issues with overclocking the Pi2 for almost 2 years. I honestly believe that purely overclocking the Pi doesn’t reduce the life – heat does (experience: Sr. Systems Administrator for fortune 500 company) – so if you don’t have a proper cooling solution and if you don’t keep an eye on temperatures to make sure the solution is “acceptable” then you’re looking at frying it. The reason I’m trying to overclock is Rom/Emulator performance – some Roms play much better with overclocked settings especially PS, N64 and DreamCast roms. For instance Super Smash Bros on N64 and MDK II on Dreamcast can be tweaked to be pretty-playable with overclock settings – Menu’s look like garbage but game play is decent.
@raymate
I’ve been thinking of getting a cooling solution myself. I’ve seen (on Ebay) heatsinks with fans attached (yes, screwed onto the heatsink) probably best solution for my setup. You’ll definitely want to either go with a fan-in-case or a modular case (like the official rasp pi case) where you can remove the top without the case falling apart. I saw a few youtube videos, one guy does specific measurements with/without fan, with/without heatsink, and combinations of the 4. According to his results, the heatsinks are worthless but for as cheap as they are I would probably do it regardless. I noticed about a 5-10C change on my Pi2 after installing 3 heatsinks w/o fan. And the heat sinks are soo cheap – plus it kind of makes the board “look” a bit more sophisticated. No matter where you buy the heatsinks from I would almost certainly rip the tape off and replace it with double-sided thermal tape – you can remove the original tape from the heatsinks with a razor blade and alcohol. I love that they have the fans powered by the GPIO board now and provide the proper connectors for it. I’d also be curious if there’s a way to change the fan speed, I’d probably run mine at a higher RPM – the fan would probably die faster but for $5 to replace….who cares? As for push/pull – it again depends on your case IMHO, most Pi cases I’ve seen have poor ventilation, I would most likely push from outside case to inside case if your using a standard case, pulling from inside the case to the outside may decrease fan life due to lack of ventilation. My thoughts…when I get a fan/heatsink combo…is that I would create some ventilation holes/strips at strategic locations along the sides of the case using a Dremel tool. Just my two cents. Let me know what you decide to go with if you have time.pi-guyParticipant-Wireless Only Portion
Well, kind of good news for those with the steam controller. It appears that the mouse pad portion of the steam controller works with retropie – bad news is emulation station doesn’t use a mouse :)When in retropie and over wireless, if you run your finger over the right d-pad area it lightly vibrates just like on a desktop and these files show up in /dev/input/by-id:
usb-Valve_Software_Steam_Controller-event-mouse
usb-Valve_Software_Steam_Controller-mouseI did add the /lib/udev/rules.d/99-steam-controller-perms.rules file and contents, rebooted, and plugged in the steam wireless stick on reboot.
However, js0 or any js* for that matter doesn’t exist when only the steam controller is plugged in.-Wired Only Portion
So, after messing around with the wireless and getting no where, I plugged it in using a micro usb to usb cable and rebooted again. Once in emulation station I went to configure input it found the device….but as a keyboard….the ONLY buttons and pads/sticks that seem to work for me right now are:
A Button
Start Button
Select Button
Left D-Pad (I think you can also configure the stick as the same…kind of a clone thing between the stick and left d-pad)
And that’s it….no B button….give me at least the B button so I can play NES roms :)-More
FYI – I’m running a Pi3 with keyboard and built-in wifi enabled, can’t promise good performance on a Pi2 with the stuff below per the URL below.So I found this tid-bit URL
Hoped on putty and performed a
sudo pip install libusb1
(I don’t know what version of php I have or came on the retropie 3.6 image, but giving it a go anyways…remember I backed up! *My install is fairly clean, I did install the Descent I & II ports, updated RP scripts, and that’s about it (aside from adding my roms)Next, in my home directory I did a
wget https://github.com/ynsta/steamcontroller/archive/master.tar.gz
andtar xf master.tar.gz cd steamcontroller-master sudo python setup.py install
then
sudo nano /etc/udev/rules.d/99-steam-controller.rules
and added the following inside the empty file# replace game group by a valid group on your system # Steam controller keyboard/mouse mode SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", GROUP="games", MODE="0660" # Steam controller gamepad mode KERNEL=="uinput", MODE="0660", GROUP="games", OPTIONS+="static_node=uinput"
Then reloaded udev
sudo udevadm control --reload
Then
cd /steamcontroller-master/scripts sc-xbox.py start
But got a bunch of errors with a lot of “enum” words in it, so I felt lucky and installed the part of the website (above) that listed “enum” in it:
sudo pip install enum34
It said something about the requirement already being satisfied, so I figured I was s***-out-of-luck. But for giggles I did the following:sudo udevadm control --reload sc-xbox.py start
and low-and-behold no messages…looking good so far…didn’t think I’d get this far.
So, the thing is I’ve got a 70″ screen mounted to the wall with no media center underneath, everything I use is either HD antenna, PLEX, or Roku, I cut the cable years ago and prefer a clean look. So, I’m not keen on having a keyboard hanging off the Pi3 mounted behing the TV, so my next step (after testing) is to setup the python script to auto-start. So, I’m going to edit my rc.local file
sudo nano /etc/rc.local
and add the following (change your paths if needed) after all the commented lines but BEFORE the exit 0 line.
/home/pi/steamcontroller-master/scripts/sc-xbox.py start
after saving the file I stopped the process I kicked off earlier and tested the rc.local file by:sc-xbox.py stop /etc/rc.local
Just to make sure no errors popped up, kept the steam controller plugged in (hardwire) and I’m ready for a reboot to see if it started.
Wow, now when I go to Configure Input in emulation station I get a “1 gamepad detected”, I hold “A” on the joystick and it see’s it as a XBOX 360 Gamepad…that’s what I call progress.
The controller is VERY touch sensitive, and I can’t seem to get the right bottom trigger or left thumb press to be defined.
I’ll work on it a bit tomorrow, see if I’m doing something wrong and take a look at the python script…I’m a bit of a script kiddie (is that saying even still used?).
Played a quick level in Super Mario on the NES (still wired joystick), exited with start-select like normal, then unplugged joystick and plugged the wireless stick in…this is where you get all warm and creamy….even without a reboot…the joystick works great and immediately over wireless…just need to turn the controller back on after unplugging the usb cable.
I’m sooo thrilled and taken waaayy to much room in this forum…hope this helps someone.I’m thinking of writing a script to make this process much faster, I’m not the coder of the “steamcontroller-master” app, kudos to that person for making my life easier, but I can certainly make setting up a Steam Controller on a RPi much faster (I think).
*Edit:
Here’s my config file, all buttons working and configured to use the thumbstick instead of the left d-pad for moving (I don’t like the sensitivity of the pads, so I swapped the d-pad for the thumbstick), just backup and overwrite yoursudo nano /opt/retropie/configs/all/retroarch-joypads/MicrosoftX-Box360pad.cfg
with this info:input_device = "Microsoft X-Box 360 pad" input_driver = "udev" input_r_y_plus_axis = "+4" input_l3_btn = "9" input_r_x_minus_axis = "-3" input_r_axis = "+5" input_save_state_axis = "+5" input_l2_btn = "4" input_start_btn = "7" input_exit_emulator_btn = "7" input_l_y_minus_btn = "h0leftanalogup" input_l_axis = "+2" input_load_state_axis = "+2" input_up_axis = "-1" input_r_y_minus_axis = "-4" input_a_btn = "0" input_b_btn = "1" input_reset_btn = "1" input_down_axis = "+1" input_r2_btn = "5" input_l_x_plus_btn = "h0leftanalogright" input_l_y_plus_btn = "h0leftanalogdown" input_right_axis = "+0" input_state_slot_increase_axis = "+0" input_x_btn = "2" input_menu_toggle_btn = "2" input_select_btn = "6" input_enable_hotkey_btn = "6" input_l_x_minus_btn = "h0leftanalogleft" input_y_btn = "3" input_left_axis = "-0" input_state_slot_decrease_axis = "-0" input_r_x_plus_axis = "+3"
pi-guyParticipant@dank
Thanks for the pat on the back, I tried zigurana’s script too and it didn’t work for me either. Could be me, but like I said I think the “shuf” command requires another package to be installed, no point in installing additional stuff if you can work with what you got I suppose.pi-guyParticipantI know it’s been a while, I thought I’d mention that I got my PI3 a few days ago and ran MDK2 under the dreamcast emulator. Works brilliantly, the cut scenes have choppy audio – but who cares? Still haven’t gotten my hands on the playstation version of MDK but MDK2 is a start. One problem that I’ve found with the dreamcast is that the controller I have (xbox360 MadCatz/Gamestop Clone) works mostly but doesn’t allow the “enter/select” button in the system menu so I can’t set the time….researching that issue.
pi-guyParticipantI’m backing-up my SD card now to give this a shot. I’ve been drinking tonight so I know I’m much smarter than a few hours ago – I bet you nothing I get this working :)
But I’ll let you know.
Thanks for the help!pi-guyParticipantHave your tried the built-in wifi? If so, within 10min I can almost guarantee you’ll lose a ping or more especially if your CPU is busy. Though I did find that having too many devices plugged into the usb port exacerbates the issue, especially if you use a 10′ long usb extension cable like I do. Probably a power thing, my guess is if under med-high CPU load and a few peripherals (w/o external power) are plugged in it starts shutting down power to the wifi before anything else.
I’m working on finding or acquiring a powered usb hub (which I know is kind-of the golden rule with Pi’s) to see if that helps things along.
pi-guyParticipantYup, I agree it’s trivial, but problem it isn’t – it’s a “what the executives in my biz call” feature. I was reviewing the shuf command, saw it in some sample scripting but I thought I saw that it required additional packages to work. Haven’t tried your code myself but I’d declare you the winner as long as nothing else needs to be installed for shuf to work…. Thanks for playing and I’ll try it as soon as I can.
pi-guyParticipantI’m having the same issue with ssh, but I’m using wifi and I read somewhere that the built-in wifi driver is having some issues on some OS flavors…maybe this one too. Are you using wifi and if so are you using the onboard wifi or a usb stick?
pi-guyParticipantRight now I’m not using nothing fancy, an old GameStop (MadCatz) 360 wired controller with a 10′ long usb extension cable. But I bought one of the new steam controllers and would love to get that working. Haven’t found a good step-by-step guide on how to get it going yet though. Please let me know if anyone knows of one.
pi-guyParticipantI tried overclocking to the settings you specified but the pi3 would start and stall at the RetroPie Splash screen (didn’t get to emulation station splash screen). Tried multiple times.
Would you mind uploading your config.txt so I can compare yours and mine – I’m running the latest 3.6 RetroPie image (no berryboot)?
I could have done something wrong. Plus I have no heatsinks or fan…yet…just got my pi3 today – that might be it.
Also, don’t know if you wrote the github article but I don’t see a 640 X 480 16:9 option in Glide and I love me some Killer Instinct.
Thanks for the helpI must say though that the RPI3 is awesome! I used to have issues with all my roms loaded (almost 6000 across 17 emulator sections) and the menu hanging or missing images – or it may have been all the scrapping and game images that were loaded – but that problem is no longer present. I don’t know if it’s the RPI3 or the latest retropie release that I’m running that fixed it – but I’m VERY happy now with my setup even if the wifi wants to constantly drop.
I did up arm_freq to 1100 (the only setting I’ve changed in the config.txt now) and killer instinct on n64 runs much better after one level but then screen remenants and trails are present heavily on battle 2.
pi-guyParticipantI’m trying to get my hands on the Playstation version, maybe someday soon….
pi-guyParticipant@Billy
Really? That’d be great or at least attach your config files somewhere. As for MDK, it totally works on a desktop version of Dosbox but when installed within dosbox on the RPI2 it loads…does some sort of check (just like PC) then fails saying that the computer is a 486 but the system is too slow or something… I googled the error msg earlier and I’ve seen others report it (on non RPI2 forums) with no fix.I’m guessing it’s probably something to do with the settings…hence my post above.
pi-guyParticipantAny chance you guys have a guide for tweaking DOSBOX….maybe it’s not possible on RPI2. Also curious if anyone has tried the game MDK (Murder, Death, Kill) in dosbox on RPI2.
pi-guyParticipantYup, I’m finally posting back after a few weeks…figured it out too…turned volume leveling off on my 70″er and bam…all working!
At the same time I found a fix for the main menu resolution problem that I was having…it too was a aspect problem of the TV…had to set it to normal instead of wide or something like that and it fixed it w/o issues.
Thanks!pi-guyParticipantAll fixed…Found my aspect ration was off on the TV itself…nothing to do with my Pie…and found a fix for my volume constantly going up and down within the game…my TV has a volume leveling feature that I turned off…and bam…all working.
Thanks!pi-guyParticipantAnyone found “The Dark Mod” which used to be a Doom3 spinoff of the original Thief but different…for RetroPie? I’d love to get my 70″ playing Thief (one of the best games ever made)
pi-guyParticipant@betz….
I’ve got the same problem, troubleshooted the same way you did…no dice. Have you found a solution?pi-guyParticipantPartially fixed…. I found that for some reason I can see/edit the config.txt from the other OS’ I’m running but not the RP3 image that I have. I changed the config from within the berryboot loader and it fixed the resolution issue for berryboot and for RP3 boot-up but not the menu…yet…still digging.
pi-guyParticipantHi Buzz,
Unfortunately that’s not a lot of help. Berryboot (unless I’m mistaken) uses the same config.txt in the /boot directory like most OS’. The berryboot image that was provided seemed to have no /boot/config.txt. I’ve made one from a non-berryboot image and placed it in the boot directory – applying the settings for no-overscan. That didn’t help on either the main menu or the emulator. It appears that the 3.0 Retropie somehow doesn’t look at the config.txt upon boot up.
As always, any assistance is appreciated – but I don’t think a “google it” will work in this case.pi-guyParticipantIt’s weird, the /boot directory doesn’t contain a config.txt file. I’m having a slight overscan issue that I corrected in Rasplex but RetroPie has no config.txt or configuration app for it. Thinking about just copying over a config.txt and placing it in the /boot directory off of a working non-berryboot retropie image. Would that work? But everything else is working super great!
See attached for Doom (retropie) and Plex (rasplex) running on my 70″
pi-guyParticipantWell deleting the /opt/retropie and running the binary updates didn’t seem to work.
I downloaded the image buzz provided and worked like a charm except I ran into theme problems again…some backgrounds didn’t display (maybe due to my roms folder being on windows share) but the start menu didn’t display properly either.
Switched to the theme simplified_static_[canela] out of the zip file simplified_static_canela_my_red_logo_v2.0 and setup bluetooth and ps3 wireless and it all works wonderfully after I deleted the simple theme from /etc/emulationstation/simple. Hope this helps someone else.Side note…I have a ton of roms…maybe the simple theme has issues with that…but only seems to start up on rom folders like tg16, nes, sega32, etc. If I comment those out Simple theme works fine.
Thanks again for pointing me in the right direction, the kids and I are ready to have some fun!pi-guyParticipant@HerbFargus
LOL. I know when I did the initial install (about a week ago) this wasn’t up. Great minds think alike. Thanks for the assistance, I’ll give this a shot.@buzz
Just did this remotely, I’ll have to wait until I get home to see if it works. If not I suppose I can work with the image Fargus pointed me to.
Thanks a bunch!pi-guyParticipantThanks buzz, I’ll give that a go.
pi-guyParticipantUnfortunately that’s not possible as BerryBoot only (currently) allows the download for RetroPie 2.3.
pi-guyParticipant@Floob
Different guy, same problem, solution didn’t work for me.
I installed retropie 2.3 using berryboot. Proceeded to update it via the retropie_setup script (so I think I’m at retropie 3.0 but unsure how to determine that). PS3 wireless controller works fine in menu but once I start an emulator…well…no joy(stick).I deleted everything in the directory you list above, re-ran the joystick config and all it did was recreate the file.
Doing some research I have a feeling that either my Retroarch didn’t get updated or somehow it’s using the wrong retroarch install…but that’s just a feeling…something to do with capitalization in RetroArch.
Any help would be greatly appreciate.09/01/2015 at 09:01 in reply to: PS3 controller not recognized when wired but does work wireless via bluetooth #105140pi-guyParticipantI had a problem where when I was trying to pair my wireless PS3 controller, and it said to plug it in to usb, it wouldn’t detect it. Finally tried other usb adapters and found 1 of the 4 I had finally showed up.
So, maybe you’re having a problem with the cable. Does the command lsusb show the ps3 controller when plugged in?
pi-guyParticipant[quote=102320]+1
I use Plex as my Media Server and would love the ability to run RasPlex from EmulationStation. I too tried berryboot to dual boot my Pi2 but ran into tons of errors. if anyone has made any progress with this I’d love to know.
[/quote]
I’ve got it all working, I’m running latest berryboot with Ubuntu mate, Rasplex, and RetroPie 3.0 on my Pi2…..love it. Bought a small wireless keyboard, and hooked my pi up to my 70″ flat screen. Only one thing though…can’t seem to get any controllers to work in-game..but they work in menu.
Though, from what I can tell my retroarch is out of date even though I updated to 3.0 from retropie_setup.sh.It might be hard for me to just share the images because I’m running berryboot off of a SD card, the images are on a USB stick (for speed), I’m running wifi with my roms on a windows share. Let’s say this is customized…or geeked out.
pi-guyParticipantThat tutorial helps but this works well for me with file server being windows os.
1. Create a blank folder, I like my home folder
mkdir ~/roms
2. Edit /etc/fstab
sudo nano /etc/fstab
3. Enter the following on the last line of that file (change to meet your needs)
//HostnameOrIP/h$/roms /home/pi/roms cifs username=username,password=password,iocharset=utf8,sec=ntlm
4. Reboot
sudo reboot
5. Check to make sure it worked by putting something in that folder on the PC and viewing the contents of the folder on the pi
6. Copy all files and folder structure from original roms folder to mounted folder.
cp -a ~/RetroPie/roms ~/roms
7. Change es_systems.cfg and edit <path> by removing just “RetroPie/” from each object.
sudo nano /etc/emulationstation/es_systems.cfg
8. Reboot again (see step 4)
-
AuthorPosts