Forum Replies Created
- atimminsParticipant12/22/2015 at 15:32Post count: 59atimminsParticipant12/14/2015 at 17:28Post count: 59
Maybe it is something specific to mame. I have used backups for consoles and haven’t had any problems. One thing I did notice through, was that the overclock settings that run smoothly on one raspberry pi made a second one freeze and crash. I had to lower the overclock settings for the second one to get it to work. If your trying both the original and the backup on the same pi, then I don’t have any help for you. Sorry.atimminsParticipant12/12/2015 at 01:42Post count: 59atimminsParticipant12/06/2015 at 00:46Post count: 59atimminsParticipant12/06/2015 at 00:44Post count: 59
I thought there was a way to load roms from a USB drive, but I don’t know how since I have never done it. It seems like maybe that was an added feature of one of the more recent updates. search around the forum and you might find something.atimminsParticipant12/03/2015 at 05:14Post count: 59
I have noticed that with win32disk imager when I choose the file I want to backup to or restore a backup from, I have to type .img the end of the file or else it doesn’t work. Try creating a backup of the working card and then writing that backup to the new card. It works for me as long as I don’t forget the .imgatimminsParticipant12/02/2015 at 17:37Post count: 59
I only looked at it long enough to see that it reset everything instead of simply updating, but I did notice these things.
1. I lost all previously configured controllers (I’m assuming I would have to go through the whole process again of configuring my 8bitdo bluetooth controller)
2. Unused emulators were added back to the home screen
3. Emulator specific configs (ie shaders etc) were overwritten with defaults
I’m not sure if this is the case, but suspect it is, that it also removed Kodi and my lirc settings which allowed me to use a ir remote control. It is not worth “updating” if I have to reconfigure every little thing that I have changed to get it the way I want it.atimminsParticipant12/02/2015 at 00:14Post count: 59
I just tried following the instructions on the link that herbfargus gave, but it did not keep any of my settings or adjustments. It did not even keep the controllers I had configured. Good thing I made a backup first. Please, anyone thinking of updating their retropie don’t it if you have made any changes at all. You may as well start with a new image and start over.atimminsParticipant11/20/2015 at 00:49Post count: 59atimminsParticipant11/17/2015 at 04:59Post count: 59atimminsParticipant11/17/2015 at 04:57Post count: 59
I have given up on this. It was a nice idea but I can’t make it work. I can successfully mount a windows folder and I can add files to the windows side and see them show up on the pi and add files on the pi and see them show up on windows, but RetroPie seems to have a problem moving the save locations to a network folder. I can move the save location to another folder on the sd card fine, but if I try to move it to a different computer on the network it defaults back to the original save location and won’t look in the network folder despite changes to the opt/retropie/configs/all/retroarch.cfg file.
Perhaps this is something that can be ironed out for future versions of RetroPie.atimminsParticipant11/13/2015 at 05:21Post count: 59atimminsParticipant11/12/2015 at 01:44Post count: 59atimminsParticipant11/10/2015 at 02:58Post count: 59
Okay so I started over with a backup and was able to change the save directory to a new raspberry pi folder. However, once I turned that new folder to a network folder on my windows computer, it gave me the same error messages as before. Were you able to make it work with a network folder on another computer? What does your /etc/fstab file look like?atimminsParticipant11/09/2015 at 02:40Post count: 59
Here is the relevant section of the config file (if you need other sections please let me know):
# Save all save files (*.srm) to this directory. This includes related files like .bsv, .rtc, .psrm, etc …
# This will be overridden by explicit command line options.
savefile_directory = /home/pi/RetroPie/saves
# Save all save states (*.state) to this directory.
# This will be overridden by explicit command line options.
savestate_directory = /home/pi/RetroPie/saves
The message I get when I try to load a save state is :
Failed to load state from “/home/pi/RetroPie/roms/nes/Contra.state”.
As you can see, it is still trying to find the save state file in the default location, but it is unable since I moved them all over to /home/pi/RetroPie/saves. I suspect that if I copied the save file and pasted it back in the default location it would work fine. Does it not allow roms and save files to be stored in different folders?atimminsParticipant11/08/2015 at 22:51Post count: 59atimminsParticipant10/06/2015 at 01:05Post count: 59
You have to set up hotkeys in your controller config file. You should add the following lines:
input_enable_hotkey_btn = “0”
input_exit_emulator_btn = “9”
This would exit the emulator when you press start while holding down select. If preferred you can change either value to any other button you would rather use.atimminsParticipant09/24/2015 at 15:32Post count: 59
As far as I know, Street Fighter doesn’t use button combinations involving start and select. The whole point of hotkeys is that you hold down a button and then press down another button to perform the action you want. If the hotkey you are trying to set up is to exit the emulator, just set it so you hold down select and then push a shoulder button or something.atimminsParticipant09/23/2015 at 05:36Post count: 59
I was able to update the firmware on my controller with a Windos 7 computer, however, ever since the update, it will not connect over Bluetooth. I tried repeating step 4 of Floob’s guide, but it tells me that device already exists and fails to connect. I even tried uninstalling bluez-utils blueman and bluez python-gobject and reinstalling them, but it made no difference. any ideas?atimminsParticipant09/22/2015 at 23:07Post count: 59atimminsParticipant09/22/2015 at 16:44Post count: 59atimminsParticipant09/21/2015 at 18:38Post count: 59
For those of us who are inexperienced, can you please explain how you fixed the issue in RetorArch? I have the same issue. I have a wireless bluetooth controller I would like to always be detected as player 1, regardless of whether or not other controllers are plugged in.atimminsParticipant09/21/2015 at 18:22Post count: 59atimminsParticipant09/21/2015 at 16:11Post count: 59
To the original poster, did you ever get this to work? I just got my 8bitdo SNES30 controller set up last night. I used the guide found at https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-a-Bluetooth-controller.
I had the controller connect via bluetooth within about 20 minutes. That was the easy part. The trouble that I had was that the buttons seem to be different for controlling emulationstation (selecting games and systems) than for controlling the actual games.
The trick I found was that the config for emulationstation is found at /home/pi/.emulationstation/es_input.cfg and uses the button numbers you got from step 5 of the guide. For whatever reason, I was unable to program the d-pad directions, but they just worked already. The config for actual games is found in /opt/retropie/configs/all/retroarch-joypads and is created in step 6. Don’t try to use the same button numbers in the two config files or it won’t work.
I am still having trouble trying to get the shoulder buttons to work as hotkeys for loading/saving save states, but otherwise it works great. Hopefully this helps.atimminsParticipant09/21/2015 at 15:23Post count: 59
I have the SNES30 controller which works fine in emulationstation and in games, but I can’t seem to get the hotkeys to work for saving and loading save states. The controller config file at opt/retropie/configs/all has the following lines but they don’t seem to work;
input_save_state_btn = “18”
input_save_state_btn = “17”
I know hotkeys have been enabled because it works to push select + start to exit the emulator. All the hotkeys for my original SNES controllers plugged in to a usb adapter still work fine.
Is there some reason that I can’t use the shoulder buttons on the SNES30 controller for hotkeys? I saw a post on some other forum where someone said he could never get the shoulder buttons to work either, so he had to re-map the hotkeys to something else.
Also, if my usb controller is plugged in and I used the 8bitdo controller, it will select the game from emulationstation, but I lose control once in the game. I’m guessing that it assumes the usb controller is player 1. Is there a way to make the 8bitdo controller have priority for player 1?atimminsParticipant09/09/2015 at 03:20Post count: 59
I have been working on this tonight and wanted to say that you guys were right and I was wrong. Adjusting the overscan values and adding overscan_scale=1 seems to have fixed my problem. It seems that in my ignorance of raspberry pi and Linux that I set my initial overscan settings incorrectly. I assumed that I was supposed to make the command line text flush with the edges of the screen. I can see now this was incorrect. Thank you all for your suggestions and help.atimminsParticipant09/08/2015 at 18:12Post count: 59
Okay, two questions. First, are you saying that I need the overscan_scale=1 line four times, one for each overscan value (top, bottom, left, right)? Second, if I change the overscan values to correct emulationstation, am I doing at the expense of having correct overscan values for the command line interface? The values I originally posted are what work for my TV to get the correct screen size for command line. I figured that since I was able to see all of the command line image without borders then emulationstation should work the same. Obviously that isn’t true.atimminsParticipant09/08/2015 at 15:47Post count: 59
I tried working on this over the weekend. I tried adjusting the frame buffer values and tried disabling overscan without success. I found that removing the line “overscan_scale=1″ from my config.txt file helped a little bit. Now I can see about half of the emulationstation menu. It seems like adding this line is the only thing that has helped everyone else, so I am out of ideas.
you need to add overscan_scale=1 in conjunction with the various overscan_left/etc settings. your settings from above:
if ES is running OVER the edge of the screen, you should be using positive numbers. negative numbers exacerbate the problem – they’re for when you have a black border around ES. so it makes sense to me that if you remove overscan_scale=1, you see more, assuming you’re still using the above set up.
overscan_bottom=20 (rather than -10)
if that works i’d probably do the same with the other overscan_’s – you’ll probably find they all need the same number.
The config file you quoted isn’t mine. It was posted by someone else. As I mentioned in my last two posts, I have already tried overscan_scale=1 in conjunction with overscan left, right, etc values and it makes no difference. In my particular setup, overscan_scale=1 seems to make the problem worse. Removing that line allowed me to see a little more of the screen, but I still have an overscan problem.atimminsParticipant09/08/2015 at 15:23Post count: 59atimminsParticipant09/08/2015 at 15:12Post count: 59
I tried working on this over the weekend. I tried adjusting the frame buffer values and tried disabling overscan without success. I found that removing the line “overscan_scale=1” from my config.txt file helped a little bit. Now I can see about half of the emulationstation menu. It seems like adding this line is the only thing that has helped everyone else, so I am out of ideas.atimminsParticipant09/03/2015 at 19:20Post count: 59atimminsParticipant09/03/2015 at 18:13Post count: 59
I don’t think the /boot/config.txt file has been changed by lirc. What is really bothering me is that the overscan problem is only within Emulationstation and individual emulators. The command line interface shows up fine and follows the overscan settings in the config.txt file. The RetroPie splashscreen and Emulationstation loading screens look fine, but once Emulationstation opens up, I can’t see the entire screen. I had this problem previously with RetroPie version 2.4. I did a fresh install of version 3.0 and things looked fine until lirc started working. Now it is behaving exactly like it did previously.atimminsParticipant09/02/2015 at 19:57Post count: 59
It is hooked up to a 65″ mitsubishi DLP TV with HDMI. I have tried 480p and 1080p hdmi modes and haven’t noticed any change. Would installing lirc have anything to do with this? I can’t imagine that it would, but it was weird that the problem only showed up after getting lirc running. I also noticed overscan in Kodi (xbmc) right after lirc started working. That was easy enough to fix with video calibration settings in Kodi though.
I have also tried modifying the full screen settings in the retroarch.conf file like this:
video_fullscreen_x = 0
video_fullscreen_y = 0
Supposedly this is supposed to force it to use the desktop resolution, but it doesn’t make any difference.