[labelwhore]

n64 and ps1 run pretty well on an overclocked Pi 2. There’s some slowdown and other issues, but I think that’s the best we’re gonna get without more cost.

[labelwhore]

Same here with Sselph’s scraper. The scraper within ES is working though, and is way faster than is used to be.

[labelwhore]

Likewise. This stuff is mostly trial an error for me, along with a healthy dose of consulting the oracle at the Google Institute of Technology.

[labelwhore]

For the ignorant (like myself) could you spell out how to install MESS? The instructions I see are from 2012, my guess is the steps have changed a little since then.

[labelwhore]

I went back to the es_systems.cfg method also. The lack of art for the 3 systems running from my HDD was driving me nuts!

[labelwhore]

I noticed that as well. I had to fix my controller last night because my settings in controller_XboxGamepad(userspacedriver).cfg got blown away. There is one thing to try; after you edit the files, change the ownership of them and/or remove write permissions.

I haven’t tried that yet myself, but it should work.

[labelwhore]

That emu.cfg doesn’t look quite right. Here’s mine. I’m also using an xbox360 controller. Notice the evdev_mapping_1 entry.

[audio]
backend = oss
disable = 0

[config]
Debug.SerialConsoleEnabled = 0
Dreamcast.Broadcast = 4
Dreamcast.Cable = 3
Dreamcast.RTC = 1543276800
Dreamcast.Region = 3
Dynarec.Enabled = 1
Dynarec.idleskip = 1
Dynarec.unstable-opt = 0
aica.LimitFPS = 1
aica.NoBatch = 0
aica.NoSound = 0
bios.UseReios = 0
pvr.MaxThreads = 3
pvr.Subdivide = 0
pvr.SynchronousRendering = 0
pvr.rend = 0
rend.UseMipmaps = 1
rend.WideScreen = 0
ta.skip = 0

[input]
evdev_device_id_1 = 8
evdev_device_id_2 = -1
evdev_device_id_3 = -1
evdev_device_id_4 = -1
evdev_mapping_1 = /opt/retropie/configs/dreamcast/mappings/controller_XboxGamepad(userspacedriver).cfg
joystick_device_id = -1

[reios]
ElfFile = 

[validate]
OpenGlChecks = 0

Now you also will need to take a look at the controller_XboxGamepad(userspacedriver).cfg file. Here’s min again for reference:

[emulator]
mapping_name = Xbox Gamepad (userspace driver)
btn_escape = 0x13a

[dreamcast]
btn_a = 0x130 
btn_b = 0x131 
btn_c = 0x136 
btn_d = 0x137 
btn_x = 0x133 
btn_y = 0x134 
btn_z = 0x13d 
btn_start = 0x13b
axis_x = 0x00 
axis_y = 0x01 
axis_trigger_left = 0x0a 
axis_trigger_right = 0x09 

[compat]
axis_dpad1_x = 0x10
axis_dpad1_y = 0x11
axis_dpad2_x =
axis_dpad2_y =
axis_x_inverted = no
axis_y_inverted = no
axis_trigger_left_inverted =
axis_trigger_right_inverted =
axis_dpad1_y_inverted = no
axis_dpad1_x_inverted = no

[labelwhore]

PSX and N64 work very well on a Pi 2, but unfortunately, not on a B+. If you hope to run those games smoothly, you should upgrade.

[labelwhore]

How did you format the usb storage device? Is it a flash drive? or HDD?

Actually, let me back up. You say all of the roms were copied from usb to the rom folder on the sd card? Have you restarted the pi, and the the emulators still don’t show up?

[labelwhore]

after the .SH on the extension line, simply add .adf .ADF

[labelwhore]

Looks like they could work. They both seem to have ARM7 processors. I’d be interested to see your results if you go with one of these, especially the odriod. That thing looks nice!

[labelwhore]

You have to start fresh, unfortunately.

[labelwhore]

^^ and faster than ever!

[labelwhore]

You’ll get the most games to run in lr-mame2003. The other MAME emulators aren’t even close. I’ve tried rom sets for all of them to be sure.

[labelwhore]

Yep, it installs from the retropie setup script. I had to manually update to version 15 after I installed it though, because the script installed version 14.2. Idk if that’s still the case.

[labelwhore]

If adf files don’t show up then either one of two things could be wrong, es_systems.cfg is not pointing to the correct folder, or the .adf extension is missing from the amiga section in es_systems.cfg. More than likely, it’s the later.

[labelwhore]

[quote=115521]Yup. The place I downloaded it from said it was made specifically for PiFBA, matching the correct romset version and all. Lots of others seemed to get them working there.

[/quote]Don’t trust where you downloaded them from. If you haven’t run them through clrmame, you should do so.

[labelwhore]

Thearchive works for me occasionally, but when gamesdb is up, it’s easily 10x faster, and way more accurate.

[labelwhore]

I think they would as there’s no way to tell xboxdrv which receiver to look for the controllers on.

[labelwhore]

[quote=115476]And your homepage works now, earlier, it wouldn’t load at all for me. [/quote]
Sweet! Enjoy! If you’re into techno, there are a lot of free tracks I posted there. I’m about halfway done with a new album. Whenever I decide to get back on that there will be more music up there. :)

[labelwhore]

Just agreeing with the umount bit. As a safety measure, a button to trigger a shutdown or reboot command is an absolute must with your roms on a usb drive.

[labelwhore]

[quote=115451]Well, I like to try stuff too, but always having to switch between monitors and keyboards, forwards and backwards and it’s not working .. it’s wearing me out and dampens the mood ^^

Btw … it still didn’t work. The file is still 0 byte and the settings don’t get saved even though a VICE message pops up when I do ingame. After a restart the gamepad is again useless.

All this owner settings paranoia stuff is so not my thing. [/quote]
The only thing I can come up with in that case is that perhaps your config file is pointing to another place. Because that sounds like exactly what was happening to me before I created the joystick file. Let me ask you this first though, are you saving both the specific joystick settings and the general settings? (both options are on the same menu)

The other thing you could check, is that there is another file in the /opt/retropie/configs/c64 folder. It’s the config file for VICE. There are a crap ton of options in there, but one of them is pointing to the location of the joystick config file. Perhaps that is pointing to a different location? Be careful, there are different joystick files for the various VICE emulators.

[quote=115451]P.S. Is your homepage down or do you have a typo in the link?

[/quote]It shouldn’t be down. It’s showing up on my end. However, wordpress wouldn’t allow a link, it’s just plain text in my sig.

[labelwhore]

No, but xboxdrv gives you a unique solution to that problem. Take a look at the bottom of the wiki for the xbox360 setup.

https://github.com/retropie/RetroPie-Setup/wiki/Setting-up-the-XBox360-controller#alternate-controller-configurations

The xboxdrv manual will give you a good ideo of how flexible this method is.

http://pingus.seul.org/~grumbel/xboxdrv/xboxdrv.html

[labelwhore]

[quote=115399]all I’ve done is point the es_systems.cfg to the USB drive, seems to work well enough for me, and it’s less hassle than creating symlinks. imho

also I did manually create all my gamelists so I have all artwork in the rom folder

[/quote]
I’ll probably go back to just doing it that way. I was attempting to standardize the way it works on my pi and one I’ve worked on for a friend. The symlinks are what I came up with so that I wouldn’t have to tweak anything once I copy my image for my friend.

[labelwhore]

[quote=115405]Wow, the stuff you are finding out …thanks, will try that.

[/quote]
:) experimentation like this what I love to do.

[labelwhore]

Who’s the owner of that file? try this:

sudo chown pi:pi -R /opt/retropie/configs/c64

If it’s blanking the settings, we know vice is at least looking at the file.

[labelwhore]

To save the controller mapping you need to create an empty file named sdl-joymap-VIC20.vjm in the /opt/retropie/configs/c64 folder. VICE will do the rest the next time you map your controller and save the joystick map from within the emulator.

[labelwhore]

That way makes me a little nervous. It’s harder to undo. You need to delete the /home/pi/RetroPie/roms folder first, because the symlink will take it’s place.

[labelwhore]

I’m working on breaking out C-128 tonight using the method I posted above. If anyone’s interested, here’s the emulators.cfg file that I’m playing with. I’m just toggling the various command line options for each image type. You have to play around with the emulator setting for each rom individually. There weren’t many games for the 128, so it’s not that big of a deal. There are some homebrews out there though.

vice-x128-stndrd="/opt/retropie/emulators/vice/bin/x128 %ROM%"
default="vice-x128-stndrd"
vice-x128-prgmode="/opt/retropie/emulators/vice/bin/x128 -autostartprgmode %ROM%"
vice-x128-autoload="/opt/retropie/emulators/vice/bin/x128 -autoload %ROM%"
vice-x128-cartcrt="/opt/retropie/emulators/vice/bin/x128 -cartcrt %ROM%"
vice-x128-cartap="/opt/retropie/emulators/vice/bin/x128 -cartap %ROM%"
vice-x128-auto="/opt/retropie/emulators/vice/bin/x128 -autostart %ROM%"

Edit: The attached is messed up. Use the code above.

[labelwhore]

So, I just set this up on my end the other day and have problems displaying the art for each game. ES is throwing errors complaining that the roms are outside the system path. How might I fix that?

Everything else is working perfectly here. I only set this up for 3 emulators, so it’s not a huge deal, just a little annoying.

[labelwhore]

you can create a symlink using the ln command like this:

ln -s {target-filename} {symbolic-filename}

so for me that command looked like this for psp:

ln -s /media/usb0/psp /home/pi/RetroPie/roms/psp/usb0

Why did I place the symlink inside the psp folder? I can hear you asking yourself. I did that because I ran this multiple times to cover multiple usb drives. To cover all the bases like I did, you’ll want to run this up to 8 times; usb0 through usb7.

I did usb0 through usb3.

[labelwhore]

All I’ve needed to do was point es_systems.cfg to the new rom location. Another possible solution is to create a symlink in place of or inside the default rom folder that points to the media/usb0. I’ve used both methods.

One thing I did notice is that you need to format the drive or usb stick in such a way that it’s fast enough. (and I assume you want to be able to read and write to the drive via windows) I used ext4 on a 1 TB usb drive I recently starting using with my pi.

[labelwhore]

When logged in via filezilla as the pi user, you’ll run into some issues editing files not owned by that user. It used to be that you only had to set a password for the root user to be able to login with it, but now there’s another setting that needs to be changed first.

I had forgotten about this piece last time. From the wiki:

before setting a root password, the following must be edited

sudo nano /etc/ssh/sshd_config

look for

PermitRootLogin without-password

change it to

PermitRootLogin yes

then ctrl+x to save, next set your root password & restart your Pi

sudo passwd root

sudo reboot

[labelwhore]

Something that fouled me up recently when creating a new emulators.cfg file for another emulator was that I created the file on my windows machine. I used textpad to create it. When I saved the file, I forgot to save it as a UNIX file. What that did was add a hidden carriage return at the end of the first line in the file. THat carriage return caused the emulator to not start. Maybe there’s something like that going on. Try opening the file with textpad then re-saving it as a UNIX based file, if you previously edited it in windows.

https://www.textpad.com/

[labelwhore]

huh, ok. What controller are you using? I may be able to help with that as well, if you’ve got an xbox 360 controller. I’ve got a workaround via an alternate controller config that I made for retropie 2.6. I haven’t done much testing with it on 3.3 so far though.

[Author]

Posts