[labelwhore]

Looks like there are a ton of command line options, so we should be in luck. :)

http://vice-emu.sourceforge.net/vice_3.html#SEC22

http://vice-emu.sourceforge.net/vice_3.html#SEC23

If you want to try it yourself, before I can get to it, this is basically what you’ll need to do:

You’ll need to create a vic20 rom folder. You’ll need a vic20 folder in opt/retropie/configs, with an emulators.cfg file in there. You’ll need to copy the vic20 line from the c64 emulators.cfg file, and set it as the default option.

Then you just need to add a new section to es_systems.cfg, and copy one of the current themes (probably c64) and rename it to vic20 and change the logo.

We may need to mess around with the command line options within emulatpors.cfg for vic20 once it’s saved. That’s where the magic happens. If you can get a game to luanch a from the command line, you can use that command line to make the proper changes to emulators.cfg

[labelwhore]

I definitely killed both my sd cards by pulling the plug. It happens if the card is being written to when it loses power. The symptom is that the cards always say they’re write protected after that, no matter what you do.

[labelwhore]

I’m just curious, what’s the advantage of using a dual boot setup for this, vs using the retropie Jessie image and installing Kodi to launch from ES?

[labelwhore]

There has got to be an easier way than that! Via some command line options and some edits to a handful of files, I bet we could get those to launch directly from the ES menu. It wouldn’t be too tough to make a theme for it too.

Maybe I’ll take a crack at it later tonight.

[labelwhore]

Probably not. I’ve killed a couple 64 gb cards, sadly.

Idk what your setup is like, but it’s important to always shut down the pi properly. For me, that means a button that triggers a shutdown command was a must. Otherwise, always use the power options from the menu in ES before you cut power to the PI. Never unplug the pi while it’s running. And although tempting, you should never use the reset pins for a reset switch, this is how I killed both the 64 GB cards that I mentioned. Use a button that triggers a proper ‘sudo reboot’ message, and only use the reset pins as a last resort.

Just general advice, idk if you violated any of that. ;)

[labelwhore]

Nope, but I’ve had a decent amount of success with the standalone version

PPSSPP slow? Try these settings

[labelwhore]

I use FileZilla rather than Cyberduck. Any ftp program will work that allows you to connect via SSH (SFTP). You just need the ip address of your pi, and the username/pw. If you haven’t changed it yet, that’s pi/raspberry.

[labelwhore]

It should be in the /tmp folder. How are you trying to access it?

[labelwhore]

^^ don’t upgrade just to upgrade. Wait until there is a fix you need.

[labelwhore]

If you find that 3.3 is super slow also, then find a fix. Please report back. I’ve had the issue I mentioned since 2.4 or so.

[labelwhore]

My guess is it’s just super slow. Some of my roms are on a USB HDD attached to my pi. That HDD is formatted in such a way that windows can’t see it. Since all my PCs are windows machines, I have to transfer roms to the HDD via SSH to the pi. The USB transfer speed is snail-like. lol

I’ve spent many hours on google looking for a way to speed it up, but nothing has worked.

[labelwhore]

OMG, please please please somebody add this!

I wrote music, and would absolutely love to add some original chip tunes to my pi for ES.

[labelwhore]

Alternate controller configs. So configurations for Atari800, c64, pc, etc. There are a couple extra manual steps to get it working.

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

[labelwhore]

Excellent work! I tried to do a handheld, but failed miserably. lol I’m still not all that great with my 3D printer.

[labelwhore]

Don’t shy away from the additional config stuff that I added to the wiki last night. It helps with a lot of emulators.

[labelwhore]

It’s all in the manual. It took me tons of trial an error to get these right lol. I’m not a developer, but I do test crap for a living.

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

As you can see xboxdrv is extremely flexible. It is possible to create scripts that restart xboxdrv with the correct .cfg file so that you could avoid having to use the xbox button at all, which is what the init.d start up method is good for. But I’ve never been able to get that to work correctly.

I think maybe because of the way xboxdrv handles the remapping of keys, this doesn’t work for every emulator. For example, the remapped escape key does not work in standalone PPSSPP to bring up the emulator menu. I still have to use my keyboard for that. It’s certainly a start towards a keyboardless setup though.

[labelwhore]

Yes, and there is a thread somewhere around here explaining how to do it.

I think mostly it’s been removed from the image over space concerns. Because it’s not needed by most people using retropie, that space is better used for rom storage.

Edit: here it is https://www.petrockblock.com/forums/topic/getting-raspbian-after-installing-retropie-3-3-via-the-image-file/

[labelwhore]

The layout is kind of funky in the player1 and player2 configs. I tried my best to keep things sane across emulators. However, it just wasn’t possible to keep everything standardized across emulators without having a ton of different config files. If anyone has a better idea for a layout than this let me know.

Interface    | Mapped to   | Atari 800/5200 |    Commodore   |
-------------------------------------------------------------
Right Analog | Arrow Keys  | Menu Nav       | Menu Nav        
Left Analog  | Mouse       | Movement       |                 
D-Pad        | Joystick    |                | Joystick port 2 
-------------------------------------------------------------
A Button     | Right Ctrl  |                | Fire            
B Button     | Num Pad 0   | Fire           | Fire            
X Button     | Enter       |                | Return          
Y Button     | Space       | Space          | Space           
-------------------------------------------------------------
L1 Button    | F4          | Start Game     |                 
R1 Button    | F7          |                |                 
L2 Button    | PAGEUP      |                |                 
R2 Button    | CAPSLOCK    |                | Start Game      
--------------------------------------------------------------
Start        | F1          | Menu           | Menu            
Back         | Esc         | Esc            | Esc  

[labelwhore]

I just added ^^ that to the wiki as well

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

[labelwhore]

the mouse emulation .cfg file is attached

[labelwhore]

Ok, so here’s what you need to do for the additional controller configs. I may make several updates to this post, so just be aware of that.

First, copy the attached files to your pi. (Remove the .txt extension first of course.) I placed them in /usr/local/ but they could go anywhere. The two attached to this post are for player 1 and player 2 for atari 800 and vice. One more is coming in the next post which is for mouse emulation.

Next, you need to edit rc.local so that xboxdrv uses the config files.

If you have this line:

xboxdrv -D i 0 --next-controller -i 1 --next-controller -i 2 --next-controller -i 3 --deadzone 4000 --dbus disabled &

change it to this:

xboxdrv -D i 0 --alt-config /usr/local/xboxdrv_player1.cfg --alt-config /usr/local/mouse.cfg --next-controller -i 1 --alt-config /usr/local/xboxdrv_player2.cfg --next-controller -i 2 --next-controller -i 3 --deadzone 4000 --dbus disabled &

if you have this line generated by the xboxdrv install from retropie_setup.sh

"/opt/retropie/supplementary/xboxdrv/bin/xboxdrv" --daemon --detach --wid 0 --led 2 --deadzone 4000 --silent --trigger-as-button ---next-controller --wid 1 --led 3 --deadzone 4000 --silent --trigger-as-button --dbus disabled --detach-kernel-driver

change it to this

"/opt/retropie/supplementary/xboxdrv/bin/xboxdrv" --daemon --detach --wid 0 --led 2 --deadzone 4000 --silent --trigger-as-button --alt-config /usr/local/xboxdrv_player1.cfg --alt-config /usr/local/mouse.cfg --next-controller --wid 1 --led 3 --deadzone 4000 --silent --trigger-as-button --alt-config /usr/local/xboxdrv_player2.cfg --dbus disabled --detach-kernel-driver

or if you are using seperate lines like this:

xboxdrv --trigger-as-button --wid 0 --led 2 --deadzone 4000 --silent &
sleep 1
xboxdrv --trigger-as-button --wid 1 --led 3 --deadzone 4000 --silent &
sleep 1
xboxdrv --trigger-as-button --wid 2 --led 4 --deadzone 4000 --silent &
sleep 1
xboxdrv --trigger-as-button --wid 3 --led 5 --deadzone 4000 --silent &

change them so they look lie this:

 xboxdrv --trigger-as-button --wid 0 --led 2 --alt-config /usr/local/xboxdrv_player1.cfg --alt-config /usr/local/mouse.cfg --deadzone 4000 --silent &
 sleep 1
 xboxdrv --trigger-as-button --wid 1 --led 3  --alt-config /usr/local/xboxdrv_player1.cfg --deadzone 4000 --silent &
 sleep 1
 xboxdrv --trigger-as-button --wid 2 --led 4 --deadzone 4000 --silent &
 sleep 1
xboxdrv --trigger-as-button --wid 3 --led 5 --deadzone 4000 --silent &

The very last step is to make the .cfg files executable.

sudo chmod +x /usr/local/xboxdrv_player1.cfg
sudo chmod +x /usr/local/xboxdrv_player2.cfg
sudo chmod +x /usr/local/mouse.cfg

Reboot.

Now, whenever you hit the xbox button on either controller 1 or 2, it will change the control scheme. For player 1, the controller starts up in normal mode. Hitting the xbox button will change to player1.cfg. Hitting it again will enable mouse emulation. One more time will bring back normal operation. Player 2 cycles between normal operation and player1.cfg. Controllers 3 and 4 are unaffected.

Here’s a little explanation of xboxdrv_player1.cfg. player2 is similar:

Hopefully this looks ok…

Interface    | Mapped to   | Atari 800/5200 |    Commodore   |
-------------------------------------------------------------
Right Analog | Arrow Keys  | Menu Nav       | Menu Nav        
Left Analog  | Mouse       | Movement       |                 
D-Pad        | Joystick    |                | Joystick port 2 
-------------------------------------------------------------
A Button     | Right Ctrl  |                | Fire            
B Button     | Num Pad 0   | Fire           | Fire            
X Button     | Enter       |                | Return          
Y Button     | Space       | Space          | Space           
-------------------------------------------------------------
L1 Button    | F4          | Start Game     |                 
R1 Button    | F7          |                |                 
L2 Button    | PAGEUP      |                |                 
R2 Button    | CAPSLOCK    |                | Start Game      
--------------------------------------------------------------
Start        | F1          | Menu           | Menu            
Back         | Esc         | Esc            | Esc  

[labelwhore]

huh, seems odd but I bet you’re right.

[labelwhore]

From the commandline sudo killall emulationstation, or just quit to commandline.

Then edit the gamelist.xml manually.

It’s a PITA, but that’s what I’ve done in a handfull of cases.

[labelwhore]

If anyone is struggling to set up controls for vice on an xbox 360 controller, I’m gonna update the xbox 360 controller page on the wiki tonight with some config files that may help.

My way basically bypasses all of the above.

[labelwhore]

Do you have to set these up per game? I’m just curious because I’ve been using a special config for my xbox 360 controller that works really well without needing to do any of the in emulator configuration.

…and sorry for raising the dead (thread).

[labelwhore]

Ok, I’m at work at the moment, so it’ll have to be later tonight, but I’ll post them for you then.

Basically there are 3 files, one for a mouse config for the pc type systems, then one for player 1 and one for player 2 that emulate keystrokes. I have it set up so that only the player 1 controller can use the mouse config.

…as a matter of fact, I think I’m gonna update the wiki with my controller configs. I’ve been using them for quite a while now, and they work pretty well.

[labelwhore]

They all work for me, so I must have the right version. I always rebuild my mame roms before I load them onto the pi, so I’m going with my folders are labeled wrong. lol

sorry for any misdirection.

[labelwhore]

[quote=114514]My issue with the xbox controller is also solved thanks to this great community. Thanks everyone!

My only issue left is trying to figure out how to get it to work with the new default mupen64plus emulator which doesn’t use Retroarch. (Retropie 3.3)

[/quote]
I haven’t played with that particular emulator, but if you’re having control issues, take a look at the xboxdrv documentation. There are some really handy features for the controller. (IMO the xbox 360 controller is hands down the best controller for the pi.) In particular, look into creating some extra config files and the --next-config option. The default behaviour of the xbox button is to change controller modes. I use this to be able to control atari 5200, 800, and ST, as well as c64 and Amiga. If you want more details I can provide some of my controller config files, and what you need to modify in rc.local to get that working.

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

[labelwhore]

[quote=114458]Thanks, I have wifi for my Pi but haven’t set it up yet. Could I just pull the miniSD card out of the Pi, put it in my Mac and load the files into the rom folder that way? Just do it manually?

[/quote]
You’ll have to use either SSH or transfer the roms via USB. It’s easy enough to use SSH, honestly.

[labelwhore]

Huh, that IS what the wiki says, but I swear I have version .106 roms working flawlessly in lr-mame2003. Perhaps I just have them labeled incorrectly.

[labelwhore]

Well, at least that file is correct now. That choose emulator screen is ok, you should just be able to select the default option for the emulator, uae4arm, then select launch. The next time around the game should just launch using that emulator, unless you change it by hitting a button.

Is there anything in tmp/runcommand.log?

[labelwhore]

Those files don’t really look right to me. Take a look at this thread where a few people were having the same problem, including me.

Dreamcast

[labelwhore]

Glad to hear it! :)

[labelwhore]

I’ve never really played with loading roms that way, so I can’t help there. I’ve just been using Filezilla and transferring roms via SSH.

[labelwhore]

The BIOS will come with the roms.

That’s right lr-mame2003 is one of the other options for mame. Just as an FYI, I had the easiest time finding the .155 rollback roms, rather than grabbing the very latest set, I looked for the latest rollback set I could find first, then looked for the working rom set to match it.

[Author]

Posts