Homepage Forums Search Search Results for 'usb'

Viewing 35 results - 2,696 through 2,730 (of 3,655 total)
  • Author
    Search Results
  • stynik
    Participant

    I’ve noticed when playing most (if not all) roms on nay system that the sound is really laggy. Chrono Trigger on the snes for me at this moment in time is practically unplayable due to the sound lag.

    I’m running the Pi with a HDMI cable, A wall charger for a phone and I have it over clocked to “High” setting though the raspi-config but it still refuses to fix sound issues.

    Is there any simple fix for this?

    I am also using RetroPie 2.3 and using my PS3 controller via USB. I have herd that the PS3 controller could be causing this but my SNES controlelr refuses to work properly due to it being cheaply made

    dcbone
    Participant

    Good morning,

    Brand new here and still working out the kinks with my firsr rEtro console rpi.

    I’ve got my iBuffalo controller to work with the emu station but not in any of the games. I read another post which had the following

    [quote]Autoconfig file
    /opt/retropie/emulators/RetroArch/configs/USB,2-axis8-buttongamepad.cfg

    RetroArch config file
    /opt/retropie/configs/all/retroarch.cfg[/quote]

    Whenever I type the stuff above it says directory not found, not sure if I’m doing something wrong or not putting the correct command before the first / but I can’t seem to access the controller config files. Again, I’m brand new to this whole deal, but I’m relatively Tech savvy. Not used to this OS is all.

    Also, does the USB only xfer a certain amount of rom files at a time? I got about 50% to transfer and all the files are the correct extension etc. although I did have to run fsck so not sure if I should format the USB and load the missing roms.

    Lastly, all the mames just flicker a black screen and exit to emu station.

    Any help is appreciated.

    dover19
    Participant

    When I first got started testing out EmulationStation I used an old PS1 controller with a USB converter and everything worked fine. I ordered 2 Tomee USB SNES controllers from amazon and I seem to be having random issues. Oddly enough they work fine in-game. The problem is with the menu. Sometimes EmulationStation loads up and it’s as if my controller is stuck on LEFT D-PAD, the menu just keeps scrolling left. Sometimes it loads up fine. When I’m able to get into an emulator’s game list it I can load ROMs and play just fine, but while I’m in the list, sometimes it automatically scrolls down non stop until I press up.

    I seem to have more problems when 2 controllers are plugged and I have even more problems when I have an LED hooked up to the GPIO. FYI, I am using this circuit from Mausberry Circuits to be able to use the POWER and RESET buttons as well as the LED from an old NES.

    Do you think this could be a power issue? Could a stronger power supply fix this? I’m currently uing a power supply from a Motorola phone:
    INPUT: 100-240V~ 50/60Hz 0.15A
    OUTPUT: 5.0V — 500mA

    #83742
    pianobrad
    Participant

    [quote=82074]UPDATE: I’ve managed to make the exit btn work.
    All I had to do was put those lines in /opt/retropie/config/snes/*.cfg file.

    input_enable_hotkey_btn = “3”
    input_exit_emulator_btn = “2”

    It’s strange, but for some reason, my Zero Delay USB encoder reads from snes config file for ALL emulators.

    The only emulator that I can’t manage to work exit buttons is MAME-PI.
    [/quote]

    escher, thank you! I’ve just set up RetroPie within the last few days and couldn’t, for the life of me, figure out how to get those hotkeys and exit buttons enabled. I had a look around in the default config and “input_enable_hotkey” as a parameter, but that wasn’t working at all. Your 2 lines did the trick.

    As you’ve indicated, most emulators control fine. The one issue I’d like to resolve seems to be with MAME. Does anyone have any experience adding controller configurations, specifically mapping an snes-style usb controller, to the MAME arcade emulator under RetroPie 2.3?

    Cheers!

    #83741
    gizmo98
    Participant
    koala33
    Participant

    koala33
    Participant

    Need some help and I am getting tired, so here goes. I am not sure if anyone has one of these or has tried to use one, but I am having some success with a minor set back.

    I am interested in getting NES, SNES, and Sega Genesis working (classic 3 button Genesis controller).

    I have the latest 2.3 installed correctly running on a revision B pi. I went through the initial retroarch controller setup with an SNES controller. Here is my layout.

    I have a 4 hub (NES, SNES, Sega, & N64 [do not plan on using N64]) that allows me to use all retro original controllers. That hub runs (via gamecube connector) to another hub (allow for 2 4 port hubs to be connected for 2 player games) which then runs to USB. Following me?

    Anyways, regardless of which controller I plug into the 4 port hub, they ALL register as a Huijia USB Gambepad. The SNES AND the NES both are using the same mapping buttons, so that works out really well. Since I initially set up retroarch gamepad in the beginning with the SNES, the NES (which has less buttons) also works perfectly.

    SNES Mappings:

    up 12
    down 14
    left 15
    right 13
    a1
    b2
    start 9
    select 7
    left up 4
    right up 5
    y3
    x0

    NES Mappings:

    b 2
    sel 7
    start 9
    u 12
    d 14
    l 15
    r 13
    a 1

    Sega is not working right though – I have not mapped out all of the buttons yet because I need to go to sleep, but what I do know is that C is registering as 0 and from what I can tell (playing Alladin) it is not working (C should throw apples I think). I believe A and B and working right – the D-pad and start works perfect.

    My question…

    Because each of the 3 controllers will ALWAYS register as the same type because of the hub, is there a way to fix the Sega?

    If not, I guess I am happy with NES and SNES, and I may try and enclose everything including the pi in some sort of 3D mold when I am all finished.

    Any help is appreciated!

    I have been through files and folders to try and edit, but again, all the controllers show as the same type.

    Anonymous
    Inactive

    Hello, in the next day i’ll buy a rasberry to try the retropie and i want to know if is possible to use it at the 640×480 resolution and how to change it. it is optimized for this resolution too?

    neogeo and psx games are running perfectly or not? retropie works with zipped roms?

    i can configure more controllers to work with the same emulator and it will recognized automatically that controller? example a psx controller usb at player 1 and another arcade controller usb for player 1 too? i change often controllers…can be done?

    works with xbox360 wireless receiver? or ps3 or ps4 controller?

    it is possible to install other os on the same sd card like linux and xbmc and choose what to load at startup or i must use different sd cards?

    thanks a lot

    #83665

    In reply to: Issues with the B+

    buzzertnl
    Participant

    Nope the B+ works perfect. It is acctualy the best model to get (best powermangement, more GPIO headers, micro-sd, more usb ports)

    #83648

    In reply to: USBGAMEPAD.CFG Problem

    stynik
    Participant

    I don’t think the player two line is needed. I am using a USB SNES controller and a PS3 controller and I didn’t need to put any player two lines in. Altho RetroPie thinks my PS3 controller is a Xbox controller due to some kinda driver mishap? But leave the .cfg files as default and should be fine.

    Floob
    Member

    As there are a lot of posts about controllers at the moment I thought I’d post my files that may help.
    Obviously the button codes are specific to my controller, but you get the idea.

    Autoconfig file
    /opt/retropie/emulators/RetroArch/configs/USB,2-axis8-buttongamepad.cfg

    RetroArch config file
    /opt/retropie/configs/all/retroarch.cfg
    Obviously the reference to use the autoconfig file above is enabled in here.

    This setup happily detects two controllers that are the same, or I can configure another auto file and it would see that.
    The alternative is to manually edit the retroarch.cfg file and enter the button codes directly in there which works fine as well.

    Also, the only content in the system specific retroarch.cfg files relate to shaders, so you can ignore those for this purpose.

    jp24s
    Participant

    Hi,

    newbie here who’s put a good couple of hours over a couple of days trying to get this to work. I’m using usb snes controllers Almost everything is good except the following:

    1) Exit emulator through Start + Select doesn’t work HOWEVER
    whenever I press down + x, I exit the emulator

    2) Can’t save, but I figure these problems are linked

    3) Controller bugs out and starts scrolling through list of roms sometimes.

    Any help is appreciated, I may have to do a clean wipe but that’s ok. I love this thing, just really want to get it going properly.

    THANKS! =]

    derrabe
    Participant

    Hi,

    I just got my first raspberry pi yesterday and I bought with the
    intention to run retropie on it and play all the games from my
    childhood. I bought 2 usb generic snes controllers off amazon for
    this. So far I seem to have gotten it configured and have roms
    transferred to it an playable. I currently have 2 problems.

    1. I have managed to get the controllers to work in the games and playable on several NES and SNES games and also 1 or 2 mame games. I bought this with the hope that I wont need a keyboard once I have it configured. The biggest hurdle for that so far is the inability to exit out of a game and select another with out having a keyboard plugged in. I have spent several hours today searching this forum and google to try to fix this and so far no luck. I think I found the right file but maybe not. /opt/retropi/emulators/Retroarch/configs/

    
    input_device = "2Axes 11Keys Game  Pad"
    input_driver = "udev"
    input_b_btn = "2"
    input_y_btn = "3"
    input_select_btn = "8"
    input_start_btn = "9"
    input_up_axis = "-1"
    input_down_axis = "+1"
    input_left_axis = "-0"
    input_right_axis = "+0"
    input_a_btn = "1"
    input_x_btn = "0"
    input_l_btn = "4"
    input_r_btn = "5"
    
    input_enable_hotkey_btn = "8"
    input_exit_emulator_btn = "4"
    input_save_state_btn = "0"
    input_load_state_btn = "1"

    2. The other ting I would like and not even sure where to look is when I was a kid I remember these games being a little more crisp. I know i am on a hd 1080p tv and not an old tube tv but some of the things are so blurry if you didnt know what they were in the original then you would have no clue what it is now. Is there any way to crispen up the graphics to make it closer to what I remember. I have no idea where to look for this.

    Thanks in advance

    #83601

    In reply to: USBGAMEPAD.CFG Problem

    Floob
    Member

    When I use 2 controllers (that are the same), it seems to happily detect both with just the first set of lines. i.e.

    input_device = “USB Gamepad ”
    input_driver = “udev”
    input_b_btn = “2”
    input_y_btn = “3”
    input_select_btn = “8”
    input_start_btn = “9”
    input_up_axis = “-1″
    input_down_axis = “+1″
    input_left_axis = “-0″
    input_right_axis = “+0″
    input_a_btn = “1”
    input_x_btn = “0”
    input_l_btn = “4”
    input_r_btn = “5”

    When you start a rom it should have some yellow text at the bottom of the screen confirming detection of the controllers.

    If you wanted to specify both controllers, I’d disable the autoconfig and just manually add the lines to the retroarch.cfg

    This may help a bit:

    #83581

    In reply to: will this work?

    Anonymous
    Inactive

    I did a NES case’d setup. I modded the plugs in the NES to simply pass through the 4 usb wires. then made a little Female USB to male NES dongle. for my SNES controllers to USB i use something that looks just like that. NO reason that wouldn’t work. But I’ve spent the day working on a gift for a friend’s husband, and she bought one of these http://www.amazon.com/SNES-Controller-Adapter-USB-Super-NES/dp/B002IXZ5DE/ref=sr_1_1?ie=UTF8&qid=1418536917&sr=8-1&keywords=usb+snes+adapter

    2 adapters in 2 cable? good deal in my book.

    the power button turns on and off the PI, and I want to wire up the reset button to the Reset Emulator button. I could do the GPIO, but after having done a RetroPie Mame cabinet and just doing a $3 keyboard hack…I think I’ll do that. I need 1 button to do 1 thing, and a keyboard hack is REALLY cheap and REALLY easy..and I’ve got a free usb port inside…so….should be real easy.

    Haven’t done a GPIO adapter….but like I said..if you’re putting it in a big enough case (the keyboard encoder isn’t big, but it won’t fit in a standard raspberry pi case) …keyboard hack is the way to go..IMHO

    jonny
    Participant

    I am wanting to make a setup using original SNES or N64 controllers and hopefully a reset/go-back button so I don’t need a keyboard. First of all will something like this work? http://www.ebay.com/itm/Super-Nintendo-Gtron-SNES-PC-USB-Controller-Adapter-Converter-Free-Shipping-/271565579200?pt=LH_DefaultDomain_0&hash=item3f3a91e3c0

    Secondly what about the GPIO adaptor? What else do you need and how hard is it to add this and where do you get the female plugs??

    Now is there a easy way to use N64 controllers and if so what is the easiest way?

    Thanks~

    copious
    Participant

    First thanks to all who posted the how to guides on controller configs. I have the 2-USB retrolink controllers and have used retroarch to configure player 1. When I edit USBGAMEPAD.CFG for the second controller everything breaks.

    This is my current working single controller file

    input_device = “USB Gamepad ”
    input_driver = “udev”
    input_b_btn = “2”
    input_y_btn = “3”
    input_select_btn = “8”
    input_start_btn = “9”
    input_up_axis = “-1”
    input_down_axis = “+1”
    input_left_axis = “-0”
    input_right_axis = “+0”
    input_a_btn = “1”
    input_x_btn = “0”
    input_l_btn = “4”
    input_r_btn = “5”
    input_enable_hotkey_btn = 8
    input_exit_emulator_btn = 9

    ##input_joypad_index = “0”
    ##input_joypad_index = “1”
    ##input_player2_device = “USB Gamepad ”
    ##input_player2_driver = “udev”
    ##input_player2_b_btn = “2”
    ##input_player2_y_btn = “3”
    ##input_player2_select_btn = “8”
    ##input_player2_start_btn = “9”
    ##input_player2_up_axis = “-1”
    ##input_player2_down_axis = “+1”
    ##input_player2_left_axis = “-0”
    ##input_player2_right_axis = “+0”
    ##input_player2_a_btn = “1”
    ##input_player2_x_btn = “0”
    ##input_player2_l_btn = “4”
    ##input_player2_r_btn = “5”
    ##input_player2_enable_hotkey_btn = 8
    ##input_player2_exit_emulator_btn = 9

    Am I supposed to register both controllers? Somehow?

    stynik
    Participant

    So I have a USB SNES controller. I’ve registered it via the retropie_setup.sh and it worked perfectly well (and still does). I have installed recently the Xbox drivers for a USB Xbox controller I have coming and I have noticed when I load up games it says

    “Joyport #0 (USB game pad) configured” (This is the one I want to use as I have set it up so when I press start and select it exits to ES)

    How ever after a couple of seconds it changes to

    “Joyport #1 (XboxGamepad(userspacedriver)

    How do I make it so that the Xbox pad does not load up unless it is plugged in or as a second controller for a second player (I intend to use my RetroPie for my game development course to aid my teachers in showing new people what games used to be like)

    Thank you so much in advance :) As some extra info I am using RetroPie 2.3

    retrorednek
    Participant

    I just received my Mausberry Shutdown circuit (use your own switch, direct-plug, micro-USB), but I’m having troubles to get it work with my NesPi project. As I press NES power button, the Raspberry Pi will power ok, but if I press power again, nothing happens. If the power button is engaged and I press reset, the Pi will perform hard reset. If the Pi is on, and I press the power button off and then press reset, the Pi will shutdown.

    I have wired power to Mausberry (brown +, red -), then reset also goes to Mausberry (yellow +, orange -). With led I cut the other lug and put it to 3.3v GPIO. For led GND I used the white wire from Nes power/reset circuit.

    Did I happen to buy the wrong circuit from Mausberry – was the momentary the one that I should have bought? Or maybe there’s something I’m missing..?

    I appreciate all your help!

    #83533
    Floob
    Member

    Seems odd that Mame isnt detecting a USB keyboard.
    Usually pressing tab would bring up the GUI menu and you can configure in there.

    Is it using mame4all-pi – that should work fine

    migouet
    Participant

    Hi

    I’ve installed Retropie v2.3 and I have configured the xbox controller for all the emulators, it functions correctly with all the emulators: snes, genesis, turbografx…
    Nevertheless with mame emulator I couldńt use the controller, how can I configure it? I tried to configure it in the mame’s menu but it didn’t detect the controller or the usb keyboard. Roms are loaded correctly but I can t play. Any suggestions?

    I’ve read something about changing the emulator of mame in retropie for other that functions better, how can I do it?

    Thanks

    davidesm
    Participant

    Alright, having some trouble getting this figured out now.

    I had been using a USB SNES controller and had it configured properly. Now I have built a little bartop cabinet and have 8 Happ buttons and a Happ joystick running through a Zero Delay Encoder to use as a “usb gamepad”.

    Upon launching I can easily set up the joystick and buttons to work in the emulation station controller configuration but when I launch games it goes back to thinking there should be a USB SNES controller plugged in and nothing works.

    I assume I have to reset some commands somewhere or what not. Looking for a little help.

    ldjstyle
    Participant

    Apologies for the one millionth controller issue post. This is the second retro pie I have made but the first using version 2.3.

    What I am attempting is to have 4 controllers plugged into a raspberry pi B+ and the controllers are slightly different. I would like to use certain ones for specific emulators and am not sure how to do this.

    I have 2 cheap usb style snes controllers and 2 original nes controllers with retro usb adapters.

    Right now all 4 controllers are recognized by emulation station, but only one is working for emulators.
    I’ve gone through tutorials on this site and elsewhere but no luck. The most common solution seems to be to copy and paste the inputs in the config file and change ‘player 1 to player 2’ this is what I successfully did on my first retro pie version 1, but in version 2.3 its not working for me as my config file has no player distinction.
    Also I read to run the auto setup for each controller but this only overwrites the first file and still leaves me with just one working controller, whichever was the last one to auto set up.

    Is there anyone that has advice to get more than one controller working and to find a way to have the nes controllers read player 1 and player 2 for emulators like atari and nes, while the snes controllers to be player 1 and 2 for snes and genesis?

    #83495
    tool212
    Participant

    This is what I want mine to do. I am Working on one for a Xmas gift and I am 99% complete. Everything works including the power button on the NES. I am stuck on the shutdown I have everything soldered to the mausberry switch and I am using gpio 23 and gpio 24. on boot up i can see error erc/switch.sh line9, line 11 echo write error device not responding or busy.
    In your code it appears you are using 23 24 and 25. could you send me a pic or diagram on how you have it wired.
    Thanks

    sludwig
    Participant

    New to Retropie here. I setup my first Retropie a weekend ago, and I got it to where everything worked fine and I had no issues with it. My problems came in when I decided to get a Bluetooth dongle and setup my PS3 sixaxis controller.

    I originally was able to save all my games and load them with hotkeys by tweaking this into my retroarch.cfg file under the /opt/retropie/configs/all/ location:

    input_enable_hotkey_btn = "0"
    input_exit_emulator_btn = "3"
    input_save_state_btn = "16"
    input_load_state_btn = "5"

    I wanted a wireless controller since I hate sitting close to the TV. So I followed this guide to get my ps3 controller to work:

    After my ps3 controller was recognized by retropie, I realized that my old configurations for my xbox360 usb controller were making it difficult to navigate around. So I ended up deleting the various “input_player” lines in the bottom of the retroarch.cfg file in WINSCP, alt F4ed, and then ran this, which ran me through the process of setting up my ps3 controller mappings:

    sudo chown pi /opt/retropie/configs/all/retroarch.cfg
    cd /opt/retropie/emulators/RetroArch/installdir/bin
    sudo ./retroarch-joyconfig -j 0 >> /opt/retropie/configs/all/retroarch.cfg

    The controller works fines for games and in emulation station. I have no problems with it in terms of functioning as a controller and playing games. My only problem is saving and loading my saved games. When I save a game I seem to get the correct message of “Saved state to slot #0”. But, every time I try load a game I get this message on the bottom of the screen:

    “Failed to load state from “/home/pi/RetroPie/(XYZgame/whatever game I’m playing here, and it cuts off screen so i’m not sure if there’s anything else after that)”

    I also notice that if I attempt to load the game, then proceed to try to save again, the save slot # moves up.

    Also, I don’t see any .srm files being created in my rom folder like I use to. I don’t know what’s going on there. I’m thinking maybe this issue has something to do with permissions but I’m not sure.

    Here is my retroarch.cfg:

    ## Skeleton config file for RetroArch
    
    # 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/savestate
    
    # Save all save states (*.state) to this directory.
    # This will be overridden by explicit command line options.
    # savestate_directory = /home/pi/RetroPie/savestate
    
    # If set to a directory, Content which is temporarily extracted
    # will be extracted to this directory.
    # extraction_directory =
    
    # Automatically saves a savestate at the end of RetroArch's lifetime.
    # The path is $SRAM_PATH.auto.
    # RetroArch will automatically load any savestate with this path on startup if savestate_auto_load is set.
    # savestate_auto_save = false
    # savestate_auto_load = false
    
    # Load libretro from a dynamic location for dynamically built RetroArch.
    # This option is mandatory.
    
    # Path to a libretro implementation.
    # libretro_path = "/path/to/libretro.so"
    
    # A directory for where to search for libretro core implementations.
    # libretro_directory =
    
    # Sets log level for libretro cores (GET_LOG_INTERFACE).
    # If a log level issued by a libretro core is below libretro_log_level, it is ignored.
    # DEBUG logs are always ignored unless verbose mode is activated (--verbose).
    # DEBUG = 0, INFO = 1, WARN = 2, ERROR = 3.
    # libretro_log_level = 0
    
    # Enable or disable verbosity level of frontend.
    # log_verbosity = false
    
    # Enable or disable RetroArch performance counters
    # perfcnt_enable = false
    
    # Path to core options config file.
    # This config file is used to expose core-specific options.
    # It will be written to by RetroArch.
    # A default path will be assigned if not set.
    core_options_path = /opt/retropie/configs/all/retroarch-core-options.cfg
    
    # Path to content load history file.
    # RetroArch keeps track of all content loaded in the menu and from CLI directly for convenient quick loading.
    # A default path will be assigned if not set.
    # game_history_path =
    
    # Number of entries that will be kept in content history file.
    # game_history_size = 100
    
    # Sets the "system" directory.
    # Implementations can query for this directory to load BIOSes, system-specific configs, etc.
    system_directory = /home/pi/RetroPie/roms/../BIOS
    
    # Sets start directory for menu content browser.
    # rgui_browser_directory =
    
    # Content directory. Interacts with RETRO_ENVIRONMENT_GET_CONTENT_DIRECTORY.
    # Usually set by developers who bundle libretro/RetroArch apps to point to assets.
    # content_directory =
    
    # Assets directory. This location is queried by default when menu interfaces try to look for
    # loadable assets, etc.
    # assets_directory =
    
    # Sets start directory for menu config browser.
    # rgui_config_directory =
    
    # Show startup screen in menu.
    # Is automatically set to false when seen for the first time.
    # This is only updated in config if config_save_on_exit is set to true, however.
    # rgui_show_start_screen = true
    
    # Flushes config to disk on exit. Useful for menu as settings can be modified.
    # Overwrites the config. #include's and comments are not preserved.
    config_save_on_exit = false
    
    # Load up a specific config file based on the core being used.
    # core_specific_config = false
    
    #### Video
    
    # Video driver to use. "gl", "xvideo", "sdl"
    # video_driver = "gl"
    
    # Which OpenGL context implementation to use.
    # Possible ones for desktop are: glx, x-egl, kms-egl, sdl-gl, wgl.
    # By default, tries to use first suitable driver.
    # video_gl_context =
    
    # Windowed xscale and yscale
    # (Real x res: base_size * xscale * aspect_ratio, real y res: base_size * yscale)
    # video_xscale = 3.0
    # video_yscale = 3.0
    
    # Fullscreen resolution. Resolution of 0 uses the resolution of the desktop.
    # video_fullscreen_x = 0
    # video_fullscreen_y = 0
    
    # Start in fullscreen. Can be changed at runtime.
    # video_fullscreen = false
    
    # If fullscreen, prefer using a windowed fullscreen mode.
    # video_windowed_fullscreen = true
    
    # Which monitor to prefer. 0 (default) means no particular monitor is preferred, 1 and up (1 being first monitor),
    # suggests RetroArch to use that particular monitor.
    # video_monitor_index = 0
    
    # Forcibly disable composition. Only works in Windows Vista/7 for now.
    # video_disable_composition = false
    
    # Video vsync.
    # video_vsync = true
    
    # Attempts to hard-synchronize CPU and GPU. Can reduce latency at cost of performance.
    # video_hard_sync = false
    
    # Sets how many frames CPU can run ahead of GPU when using video_hard_sync.
    # Maximum is 3.
    # video_hard_sync_frames = 0
    
    # Inserts a black frame inbetween frames.
    # Useful for 120 Hz monitors who want to play 60 Hz material with eliminated ghosting.
    # video_refresh_rate should still be configured as if it is a 60 Hz monitor (divide refresh rate by 2).
    # video_black_frame_insertion = false
    
    # Use threaded video driver. Using this might improve performance at possible cost of latency and more video stuttering.
    video_threaded = true
    
    # Use a shared context for HW rendered libretro cores.
    # Avoids having to assume GL state changes inbetween frames.
    # video_shared_context = false
    
    # Smoothens picture with bilinear filtering. Should be disabled if using pixel shaders.
    video_smooth = false
    
    # Forces rendering area to stay equal to content aspect ratio or as defined in video_aspect_ratio.
    # video_force_aspect = true
    
    # Only scales video in integer steps.
    # The base size depends on system-reported geometry and aspect ratio.
    # If video_force_aspect is not set, X/Y will be integer scaled independently.
    # video_scale_integer = false
    
    # A floating point value for video aspect ratio (width / height).
    # If this is not set, aspect ratio is assumed to be automatic.
    # Behavior then is defined by video_aspect_ratio_auto.
    video_aspect_ratio = 1.33
    
    # If this is true and video_aspect_ratio is not set,
    # aspect ratio is decided by libretro implementation.
    # If this is false, 1:1 PAR will always be assumed if video_aspect_ratio is not set.
    # video_aspect_ratio_auto = false
    
    # Forces cropping of overscanned frames.
    # Exact behavior of this option is implementation specific.
    # video_crop_overscan = true 
    
    # Path to shader. Shader can be either Cg, CGP (Cg preset) or GLSL, GLSLP (GLSL preset)
    # video_shader = "/path/to/shader.{cg,cgp,glsl,glslp}"
    
    # Load video_shader on startup.
    # Other shaders can still be loaded later in runtime.
    # video_shader_enable = false
    
    # Defines a directory where shaders (Cg, CGP, GLSL) are kept for easy access.
    video_shader_dir = /opt/retropie/emulators/RetroArch/shader/
    
    # CPU-based video filter. Path to a dynamic library.
    # video_filter =
    
    # Path to a font used for rendering messages. This path must be defined to enable fonts.
    # Do note that the _full_ path of the font is necessary!
    # video_font_path = 
    
    # Size of the font rendered.
    # video_font_size = 32
    
    # Enable usage of OSD messages.
    # video_font_enable = true
    
    # Offset for where messages will be placed on screen. Values are in range 0.0 to 1.0 for both x and y values. 
    # [0.0, 0.0] maps to the lower left corner of the screen.
    # video_message_pos_x = 0.05
    # video_message_pos_y = 0.05
    
    # Color for message. The value is treated as a hexadecimal value.
    # It is a regular RGB hex number, i.e. red is "ff0000".
    # video_message_color = ffffff
    
    # Video refresh rate of your monitor.
    # Used to calculate a suitable audio input rate.
    # video_refresh_rate = 59.95
    
    # Allows libretro cores to set rotation modes.
    # Setting this to false will honor, but ignore this request.
    # This is useful for vertically oriented content where one manually rotates the monitor.
    # video_allow_rotate = true
    
    # Forces a certain rotation of the screen.
    # The rotation is added to rotations which the libretro core sets (see video_allow_rotate).
    # The angle is <value> * 90 degrees counter-clockwise.
    # video_rotation = 0
    
    #### Audio
    
    # Enable audio.
    # audio_enable = true
    
    # Audio output samplerate.
    # audio_out_rate = 48000
    
    # Audio resampler backend. Which audio resampler to use.
    # Default will use "sinc".
    # audio_resampler =
    
    # Audio driver backend. Depending on configuration possible candidates are: alsa, pulse, oss, jack, rsound, roar, openal, sdl, xaudio.
    # audio_driver =
    
    # Override the default audio device the audio_driver uses. This is driver dependant. E.g. ALSA wants a PCM device, OSS wants a path (e.g. /dev/dsp), Jack wants portnames (e.g. system:playback1,system:playback_2), and so on ...
    # audio_device =
    
    # Audio DSP plugin that processes audio before it's sent to the driver. Path to a dynamic library.
    # audio_dsp_plugin =
    
    # Will sync (block) on audio. Recommended.
    # audio_sync = true
    
    # Desired audio latency in milliseconds. Might not be honored if driver can't provide given latency.
    # audio_latency = 64
    
    # Enable audio rate control.
    # audio_rate_control = true
    
    # Controls audio rate control delta. Defines how much input rate can be adjusted dynamically.
    # Input rate = in_rate * (1.0 +/- audio_rate_control_delta)
    # audio_rate_control_delta = 0.005
    
    # Audio volume. Volume is expressed in dB.
    # 0 dB is normal volume. No gain will be applied.
    # Gain can be controlled in runtime with input_volume_up/input_volume_down.
    # audio_volume = 0.0
    
    #### Overlay
    
    # Enable overlay.
    # input_overlay_enable = false
    
    # Path to input overlay
    # input_overlay =
    
    # Overlay opacity
    # input_overlay_opacity = 1.0
    
    # Overlay scale
    # input_overlay_scale = 1.0
    
    #### Input
    
    # Input driver. Depending on video driver, it might force a different input driver.
    # input_driver = sdl
    
    # Joypad driver. (Valid: linuxraw, sdl, dinput)
    # input_joypad_driver =
    
    # Keyboard layout for input driver if applicable (udev/evdev for now).
    # Syntax is either just layout (e.g. "no"), or a layout and variant separated with colon ("no:nodeadkeys").
    # input_keyboard_layout =
    
    # Defines axis threshold. Possible values are [0.0, 1.0]
    # input_axis_threshold = 0.5
    
    # Enable input auto-detection. Will attempt to autoconfigure
    # joypads, Plug-and-Play style.
    input_autodetect_enable = true
    
    # Directory for joypad autoconfigs (PC).
    # If a joypad is plugged in, that joypad will be autoconfigured if a config file
    # corresponding to that joypad is present in joypad_autoconfig_dir.
    # Input binds which are made explicit (input_playerN_*_btn/axis) will take priority over autoconfigs.
    # Autoconfigs can be created with retroarch-joyconfig, manually, or with a frontend.
    # Requires input_autodetect_enable to be enabled.
    joypad_autoconfig_dir = /opt/retropie/emulators/RetroArch/configs/
    
    # Enable debug input key reporting on-screen.
    # input_debug_enable = false
    
    # Sets which libretro device is used for a player.
    # Devices are indentified with a number.
    # This is normally saved by the menu.
    # Device IDs are found in libretro.h.
    # These settings are overridden by explicit command-line arguments which refer to input devices.
    # None: 0
    # Joypad (RetroPad): 1
    # Mouse: 2
    # Keyboard: 3
    # Generic Lightgun: 4
    # Joypad w/ Analog (RetroPad + Analog sticks): 5
    # Multitap (SNES specific): 257
    # Super Scope (SNES specific): 260
    # Justifier (SNES specific): 516
    # Justifiers (SNES specific): 772
    
    # input_libretro_device_p1 =
    # input_libretro_device_p2 =
    # input_libretro_device_p3 =
    # input_libretro_device_p4 =
    # input_libretro_device_p5 =
    # input_libretro_device_p6 =
    # input_libretro_device_p7 =
    # input_libretro_device_p8 =
    
    # Keyboard input. Will recognize letters ("a" to "z") and the following special keys (where "kp_"
    # is for keypad keys):
    #
    #   left, right, up, down, enter, kp_enter, tab, insert, del, end, home,
    #   rshift, shift, ctrl, alt, space, escape, add, subtract, kp_plus, kp_minus,
    #   f1, f2, f3, f4, f5, f6, f7, f8, f9, f10, f11, f12,
    #   num0, num1, num2, num3, num4, num5, num6, num7, num8, num9, pageup, pagedown,
    #   keypad0, keypad1, keypad2, keypad3, keypad4, keypad5, keypad6, keypad7, keypad8, keypad9,
    #   period, capslock, numlock, backspace, multiply, divide, print_screen, scroll_lock,
    #   tilde, backquote, pause, quote, comma, minus, slash, semicolon, equals, leftbracket,
    #   backslash, rightbracket, kp_period, kp_equals, rctrl, ralt
    #
    # Keyboard input, Joypad and Joyaxis will all obey the "nul" bind, which disables the bind completely, 
    # rather than relying on a default.
    input_player1_a = x
    input_player1_b = z
    input_player1_y = a
    input_player1_x = s
    input_player1_start = enter
    input_player1_select = rshift
    input_player1_l = q
    input_player1_r = w
    input_player1_left = left
    input_player1_right = right
    input_player1_up = up
    input_player1_down = down
    # input_player1_l2 =
    # input_player1_r2 =
    # input_player1_l3 =
    # input_player1_r3 =
    
    # Two analog sticks (DualShock-esque).
    # Bound as usual, however, if a real analog axis is bound,
    # it can be read as a true analog.
    # Positive X axis is right, Positive Y axis is down.
    # input_player1_l_x_plus =
    # input_player1_l_x_minus =
    # input_player1_l_y_plus =
    # input_player1_l_y_minus =
    # input_player1_r_x_plus =
    # input_player1_r_x_minus =
    # input_player1_r_y_plus =
    # input_player1_r_y_minus =
    
    # If desired, it is possible to override which joypads are being used for player 1 through 8.
    # First joypad available is 0.
    # input_player1_joypad_index = 0
    # input_player2_joypad_index = 1
    # input_player3_joypad_index = 2
    # input_player4_joypad_index = 3
    # input_player5_joypad_index = 4
    # input_player6_joypad_index = 5
    # input_player7_joypad_index = 6
    # input_player8_joypad_index = 7
    
    # Joypad buttons.
    # Figure these out by using RetroArch-Phoenix or retroarch-joyconfig.
    # You can use joypad hats with hnxx, where n is the hat, and xx is a string representing direction. 
    # E.g. "h0up"
    # input_player1_a_btn =
    # input_player1_b_btn =
    # input_player1_y_btn =
    # input_player1_x_btn =
    # input_player1_start_btn =
    # input_player1_select_btn =
    # input_player1_l_btn =
    # input_player1_r_btn =
    # input_player1_left_btn =
    # input_player1_right_btn =
    # input_player1_up_btn =
    # input_player1_down_btn =
    # input_player1_l2_btn =
    # input_player1_r2_btn =
    # input_player1_l3_btn =
    # input_player1_r3_btn =
    
    # Axis for RetroArch D-Pad. 
    # Needs to be either '+' or '-' in the first character signaling either positive or negative direction of the axis, then the axis number. 
    # Do note that every other input option has the corresponding _btn and _axis binds as well; they are omitted here for clarity.
    # input_player1_left_axis =
    # input_player1_right_axis =
    # input_player1_up_axis =
    # input_player1_down_axis =
    
    # Holding the turbo while pressing another button will let the button enter a turbo mode
    # where the button state is modulated with a periodic signal.
    # The modulation stops when the button itself (not turbo button) is released.
    # input_player1_turbo =
    
    # Describes the period and how long of that period a turbo-enabled button should behave.
    # Numbers are described in frames.
    # input_turbo_period = 6
    # input_turbo_duty_cycle = 3
    
    # This goes all the way to player 8 (*_player2_*, *_player3_*, etc), but omitted for clarity.
    # All input binds have corresponding binds for keyboard (none), joykeys (_btn) and joyaxes (_axis) as well.
    
    # Toggles fullscreen.
    # input_toggle_fullscreen = f
    
    # Saves state.
    # input_save_state = f2
    # Loads state.
    # input_load_state = f4
    
    # State slots. With slot set to 0, save state name is *.state (or whatever defined on commandline).
    # When slot is != 0, path will be $path%d, where %d is slot number.
    # input_state_slot_increase = f7
    # input_state_slot_decrease = f6
    
    # Toggles between fast-forwarding and normal speed.
    # input_toggle_fast_forward = space
    
    # Hold for fast-forward. Releasing button disables fast-forward.
    # input_hold_fast_forward = l
    
    # Key to exit RetroArch cleanly. 
    # Killing it in any hard way (SIGKILL, etc) will terminate RetroArch without saving RAM, etc.
    # On Unix-likes, SIGINT/SIGTERM allows a clean deinitialization.
    input_exit_emulator = escape
    
    # Applies next and previous shader in directory.
    input_shader_next = m
    input_shader_prev = n
    
    # Hold button down to rewind. Rewinding must be enabled.
    input_rewind = r
    
    # Toggle between recording and not.
    # input_movie_record_toggle = o
    
    # Toggle between paused and non-paused state
    # input_pause_toggle = p
    
    # Frame advance when content is paused
    # input_frame_advance = k
    
    # Reset the content.
    # input_reset = h
    
    # Cheats.
    # input_cheat_index_plus = y
    # input_cheat_index_minus = t
    # input_cheat_toggle = u
    
    # Mute/unmute audio
    # input_audio_mute = f9
    
    # Take screenshot
    # input_screenshot = f8
    
    # Netplay flip players.
    # input_netplay_flip_players = i
    
    # Hold for slowmotion.
    # input_slowmotion = e
    
    # Enable other hotkeys.
    # If this hotkey is bound to either keyboard, joybutton or joyaxis,
    # all other hotkeys will be disabled unless this hotkey is also held at the same time.
    # This is useful for RETRO_KEYBOARD centric implementations
    # which query a large area of the keyboard, where it is not desirable
    # that hotkeys get in the way.
    
    # Alternatively, all hotkeys for keyboard could be disabled by the user.
    input_enable_hotkey = escape
    
    # Increases audio volume.
    # input_volume_up = kp_plus
    # Decreases audio volume.
    # input_volume_down = kp_minus
    
    # Toggles to next overlay. Wraps around.
    # input_overlay_next =
    
    # Toggles eject for disks. Used for multiple-disk content.
    # input_disk_eject_toggle =
    
    # Cycles through disk images. Use after ejecting.
    # Complete by toggling eject again.
    # input_disk_next =
    
    # Toggles menu.
    # input_menu_toggle = f1
    
    # Toggles mouse grab. When mouse is grabbed, RetroArch hides the mouse,
    # and keeps the mouse pointer inside the window to allow relative mouse input
    # to work better.
    # input_grab_mouse_toggle = f11
    
    #### Menu
    
    # Menu driver to use. "rgui", "lakka", etc. 
    # menu_driver = "rgui"
    
    #### Camera
    
    # Override the default camera device the camera driver uses. This is driver dependant.
    # camera_device =
    
    # Override the default privacy permission for cores that want to access camera services. Is "false" by default.
    # camera_allow = false
    
    #### Location
    
    # Override the default privacy permission for cores that want to access location services. Is "false" by default.
    # location_allow = false
    
    #### Netplay
    
    # When being client over netplay, use keybinds for player 1.
    # netplay_client_swap_input = false
    
    # The nickname being used for playing online.
    # netplay_nickname = 
    
    # The amount of delay frames to use for netplay. Increasing this value will increase
    # performance, but introduce more latency.
    # netplay_delay_frames = 0
    
    # Netplay mode for the current user.
    # false is Server, true is Client.
    # netplay_mode = false
    
    # Enable or disable spectator mode for the player during netplay.
    # netplay_spectator_mode_enable = false
    
    # The IP Address of the host to connect to.
    # netplay_ip_address = 
    
    # The port of the host IP Address. Can be either a TCP or an UDP port.
    # netplay_ip_port = 55435
    
    #### Misc
    
    # Enable rewinding. This will take a performance hit when playing, so it is disabled by default.
    rewind_enable = false
    
    # Rewinding buffer size in megabytes. Bigger rewinding buffer means you can rewind longer.
    # The buffer should be approx. 20MB per minute of buffer time.
    rewind_buffer_size = 10
    
    # Rewind granularity. When rewinding defined number of frames, you can rewind several frames at a time, increasing the rewinding speed.
    rewind_granularity = 2
    
    # Pause gameplay when window focus is lost.
    # pause_nonactive = true
    
    # Autosaves the non-volatile SRAM at a regular interval. This is disabled by default unless set otherwise.
    # The interval is measured in seconds. A value of 0 disables autosave.
    # autosave_interval =
    
    # Path to XML cheat database (as used by bSNES).
    # cheat_database_path =
    
    # Path to XML cheat config, a file which keeps track of which
    # cheat settings are used for individual games.
    # If the file does not exist, it will be created.
    # cheat_settings_path =
    
    # Directory to dump screenshots to.
    # screenshot_directory =
    
    # Records video after CPU video filter.
    # video_post_filter_record = false
    
    # Records output of GPU shaded material if available.
    # video_gpu_record = false
    
    # Screenshots output of GPU shaded material if available.
    video_gpu_screenshot = true
    
    # Block SRAM from being overwritten when loading save states.
    # Might potentially lead to buggy games.
    # block_sram_overwrite = false
    
    # When saving a savestate, save state index is automatically increased before
    # it is saved.
    # Also, when loading content, the index will be set to the highest existing index.
    # There is no upper bound on the index.
    # savestate_auto_index = false
    
    # Slowmotion ratio. When slowmotion, content will slow down by factor.
    # slowmotion_ratio = 3.0
    
    # The maximum rate at which content will be run when using fast forward. (E.g. 5.0 for 60 fps content => 300 fps cap).
    # RetroArch will go to sleep to ensure that the maximum rate will not be exceeded.
    # Do not rely on this cap to be perfectly accurate.
    # A negative ratio equals no FPS cap.
    # fastforward_ratio = -1.0
    
    # Enable stdin/network command interface.
    # network_cmd_enable = false
    # network_cmd_port = 55355
    # stdin_cmd_enable = false
    
    input_player1_joypad_index = "0"
    input_player1_b_btn = "13"
    input_player1_y_btn = "12"
    input_player1_select_btn = "0"
    input_player1_start_btn = "3"
    input_player1_up_btn = "4"
    input_player1_down_btn = "6"
    input_player1_left_btn = "7"
    input_player1_right_btn = "5"
    input_player1_a_btn = "14"
    input_player1_x_btn = "15"
    input_player1_l_btn = "10"
    input_player1_r_btn = "11"
    input_player1_l2_btn = "8"
    input_player1_r2_btn = "9"
    input_player1_l3_btn = "1"
    input_player1_r3_btn = "2"
    input_player1_l_x_plus_axis = "+0"
    input_player1_l_x_minus_axis = "-0"
    input_player1_l_y_plus_axis = "+1"
    input_player1_l_y_minus_axis = "-1"
    input_player1_r_x_plus_axis = "+2"
    input_player1_r_x_minus_axis = "-2"
    input_player1_r_y_plus_axis = "+3"
    input_player1_r_y_minus_axis = "-3"
    
    savefile_directory = /home/pi/RetroPie/
    savestate_directory = /home/pi/RetroPie/
    
    input_enable_hotkey_btn = "0"
    input_exit_emulator_btn = "3"
    
    input_enable_hotkey_btn = "0"
    input_save_state_btn = "16"
    
    input_enable_hotkey_btn = "0"
    input_load_state_btn = "5"
    #83476
    Anonymous
    Inactive

    Hello, Escher!
    facing same problem: I have every emu configured with USB logitech gamepad , but in deep troubles with my diy zeroDelay 12 buttons console.
    Could you please quote your retroarch .cfg file for zeroDelay and especially aside emulators .cfg s as well. Thank you!
    PS: did not find PM way here, sorry. However it is really interesting for everybody as zeroDelay is a good choice because of its price/

    uselessrascal
    Participant

    Dear All,
    I have this controller :Speedlink 1.9m Strike USB Gamepad for PC – Black

    I have got retropie up and running. Emulation Station works great with the controller. I have transferred roms which seem to work fine (SNES ROMS). I get to the point where I have launched the game and at that point the only button on the controller that seems to work is the “start” button. I have gone through the retroarch command line thing multiple times in slightly different ways. From the script and from just calling it from the command line. It all seems to work up until he point where I try and play a game… then nothing. I don’t know where to go from here. Suggestions?
    thanks in advance.

    collectedrubbish
    Participant

    1) Wifi. When setting up my xbmc i messed with command line stuff for hours and didn’t get anywhere with the wifi. Is there a gui/wizard on the Retropie to help with wifi? I haven’t seen one. Then ssh is likely $ ssh pi@ip…. eh?

    2) I have a ps3 controller but no bluetooth dongle. I ran the ps3 driver script from the gui. I ran the configure retro arch controller. It found some axes and seemed to log neutral positions but timed out when it was looking for any buttons. I suspect there may be problems with my controller. Is there a simple way to test that on a linux Mint system?

    3) Keyboard. I will settle to using the keyboard for some games. When I try to configure it i can map all of the keys but when I get to ‘OK’ none of the keys will work.

    4) I have the 6666 game iso that is giving me problems. Is there another good cache of games I should look into, or some known solution for the problematic iso?

    Thanks all.

    #83416
    davem666
    Participant

    Figured it out… The B+ wasn’t getting enough power due to a crummy micro-usb cable… That was a fun one to troubleshoot :-).

    #83398
    powerpoint45
    Participant

    Both can be started from emulationstation. But you can only exit mupen64plus-libretro with escape. See also –> https://www.petrockblock.com/forums/topic/mupen64plus-ricrpi-branch/page/2/

    OK I did get it to run via emulation station but controlling the game via keyboard does not work. Does it only work with a USB game controller? I’m ordering one so I can’t test right now.

    louishelpits
    Participant

    Hi Everyone, I’ve been battling all afternoon and have a number of problems – most likely due to my incompetence.

    I’m running retropie 2.3 after downloading / installing via berryboot.

    I have copied some roms over via samba and have a PS3 controller connected with a USB cable that seems to work in so far as I can configure it using the retropie GUI.

    However, my problems start when I actually try to play some ROMs, i have 3 different issues:

    1: try to play a N64 ROM, it displays loads of command line code and then goes back to the N64 screen within retropie. nothing happens

    2: try to play an Amiga ROM, the screen just goes black

    3: try to play a SNES ROM, the game loads but the PS3 pad isn’t recognised, having mucked around with the keyboard it looks like the game is recognising some keyboard input, e.g. cursor keys make the character move

    If anyone has any advice, I would be most grateful, i feel like i am almost there… also, please bear with me, my linux / command line knowledge is nil so really need step by step help

    Many thanks,

    Louis

    piquestions
    Participant

    Hi Guys,

    I searched but couldn’t find instructions. I was hoping someone could help me out in setting up a PS3 remote, wired USB to the RaspberryPi B+. I have downloaded the drivers but it seems to only be for Bluetooth. Any help you guys could give would be greatly appreciated.

    Thanks.

    #83370
    cmvac
    Participant

    Actually you can use Retroarch with Openelec and play emulated games directly from Openelec and XBMC.

    Follow this guide: http://openelec.tv/forum/128-addons/72972-retroarch-addon-arm-rpi?limitstart=0

    I have it installed and it works like a charm. The only issue I found was everytime you start a game, you have to configure your controller. Maybe there’s a way to get around this, but I still haven’t found it.

    I also have build my Hyperion ambilight set with a USBTV007 EasyCAP capturing my TV output. I want it to capture also the Retroarch but I don’t know what is the priority given to Retroarch for the v4l driver. Can anyone help me?

    toontje
    Participant

    Hi all!

    First message on this forum, first time i install RetroPie.
    My idea is to have my Pi hidden away in a cupboard, a Bluetooth adapter hanging on a cable outside of the cupboard and me (or probably my kids) sitting in the couch with just a controller playing on the TV.

    So i installed RetroPie. No problems.
    Updated everything on the distribution with apt-get update and apt-get upgrade.
    I hooked the PS3 controller up to the Pi and it gets detected by Emulation Station. Buttons configured and all working well. So now bluetooth.

    Installed bluetooth drivers.
    Now the idea was to use a PS3 controller so i went to the shop and got myself a “compatible” one. A Gioteck VX-2 wireless controller for PS3 and PC.
    I had an old noname bluetooth adapter which is recognized by the OS, but i am not able to pair the controller.
    At first i thought it was the adapter since the adapter only supports BT2.0. So i went to the shop again and bought a Belkin BT4.0 adapter.
    However, that doesn’t solve my problem.
    I am following this manual: https://github.com/retropie/RetroPie-Setup/wiki/Setting-up-a-PS3-controller
    I get stuck at the point where i run sixpair as root.

    pi@retropi ~ $ sudo ./sixpair
    No controller found on USB busses.

    I have been reading all over the web. I actually read a whole bunch of other websites before i found the article on Github. But i cannot get my head around what is wrong here.

    I am looking for hints how to troubleshoot this.

    Here is some info:
    pi@retropi ~ $ lsusb
    Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
    Bus 001 Device 006: ID 050d:065a Belkin Components
    Bus 001 Device 010: ID 25f0:83c4

    pi@retropi ~ $ hciconfig
    hci0: Type: BR/EDR Bus: USB
    BD Address: 00:02:72:DA:1C:BB ACL MTU: 1021:8 SCO MTU: 64:1
    UP RUNNING PSCAN
    RX bytes:916 acl:0 sco:0 events:43 errors:0
    TX bytes:947 acl:0 sco:0 commands:43 errors:0

    pi@retropi ~ $ jstest /dev/input/js0 (this is when the joystick is connected over USB)
    Driver version is 2.1.0.
    Joystick (Goodbetterbest Ltd Gioteck VX2 BT Controller) has 6 axes (X, Y, Z, Rz, Hat0X, Hat0Y)
    and 12 buttons (BtnX, BtnY, BtnZ, BtnTL, BtnTR, BtnTL2, BtnTR2, BtnSelect, BtnStart, BtnMode, BtnThumbL, BtnThumbR).
    Testing … (interrupt to exit)
    Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0:-32767 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0:-32767 1:-32767 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0:-32767 1:-32767 2:-32767 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0:-32767 1:-32767 2:-32767 3:-32767 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0:-32767 1:-32767 2:-32767 3:-32767 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:offAxes: 0:-32767 1:-32767 2:-32767 3:-32767 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off

    pi@retropi ~ $ /etc/init.d/bluetooth status
    [ ok ] bluetooth is running.

    pi@retropi ~ $ tail /var/log/messages
    Dec 5 14:48:56 retropi kernel: [ 4909.383105] usb 1-1.2: New USB device found, idVendor=050d, idProduct=065a
    Dec 5 14:48:56 retropi kernel: [ 4909.383164] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    Dec 5 14:48:56 retropi kernel: [ 4909.383186] usb 1-1.2: Product: BCM20702A0
    Dec 5 14:48:56 retropi kernel: [ 4909.383208] usb 1-1.2: Manufacturer: Broadcom Corp
    Dec 5 14:48:56 retropi kernel: [ 4909.383225] usb 1-1.2: SerialNumber: 000272DA1CBB
    Dec 5 14:49:04 retropi kernel: [ 4917.725787] usb 1-1.3: new full-speed USB device number 7 using dwc_otg
    Dec 5 14:49:04 retropi kernel: [ 4917.832764] usb 1-1.3: New USB device found, idVendor=054c, idProduct=0268
    Dec 5 14:49:04 retropi kernel: [ 4917.832825] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    Dec 5 14:49:04 retropi kernel: [ 4917.832849] usb 1-1.3: Product: PLAYSTATION(R)3 Controller
    Dec 5 14:49:04 retropi kernel: [ 4917.832868] usb 1-1.3: Manufacturer: Sony
    Dec 5 14:49:04 retropi kernel: [ 4917.996756] usb 1-1.3: USB disconnect, device number 7
    Dec 5 14:49:05 retropi kernel: [ 4918.235646] usb 1-1.3: new full-speed USB device number 8 using dwc_otg
    Dec 5 14:49:05 retropi kernel: [ 4918.342249] usb 1-1.3: New USB device found, idVendor=25f0, idProduct=83c4
    Dec 5 14:49:05 retropi kernel: [ 4918.342352] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    Dec 5 14:49:05 retropi kernel: [ 4918.342409] usb 1-1.3: Product: Gioteck VX2 BT Controller
    Dec 5 14:49:05 retropi kernel: [ 4918.342430] usb 1-1.3: Manufacturer: Goodbetterbest Ltd
    Dec 5 14:49:05 retropi kernel: [ 4918.404891] input: Goodbetterbest Ltd Gioteck VX2 BT Controller as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/input/input1
    Dec 5 14:49:05 retropi kernel: [ 4918.416945] hid-generic 0003:25F0:83C4.0003: input,hidraw0: USB HID v1.11 Gamepad [Goodbetterbest Ltd Gioteck VX2 BT Controller] on usb-bcm2708_usb-1.3/input0
    Dec 5 14:49:15 retropi kernel: [ 4928.748970] usb 1-1.3: USB disconnect, device number 8
    Dec 5 14:49:16 retropi kernel: [ 4929.755708] usb 1-1.3: new full-speed USB device number 9 using dwc_otg
    Dec 5 14:49:16 retropi kernel: [ 4929.863759] usb 1-1.3: New USB device found, idVendor=054c, idProduct=0268
    Dec 5 14:49:16 retropi kernel: [ 4929.863856] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    Dec 5 14:49:16 retropi kernel: [ 4929.863885] usb 1-1.3: Product: PLAYSTATION(R)3 Controller
    Dec 5 14:49:16 retropi kernel: [ 4929.863900] usb 1-1.3: Manufacturer: Sony
    Dec 5 14:49:16 retropi kernel: [ 4930.028863] usb 1-1.3: USB disconnect, device number 9
    Dec 5 14:49:17 retropi kernel: [ 4930.276078] usb 1-1.3: new full-speed USB device number 10 using dwc_otg
    Dec 5 14:49:17 retropi kernel: [ 4930.381736] usb 1-1.3: New USB device found, idVendor=25f0, idProduct=83c4
    Dec 5 14:49:17 retropi kernel: [ 4930.381836] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    Dec 5 14:49:17 retropi kernel: [ 4930.381863] usb 1-1.3: Product: Gioteck VX2 BT Controller
    Dec 5 14:49:17 retropi kernel: [ 4930.381923] usb 1-1.3: Manufacturer: Goodbetterbest Ltd
    Dec 5 14:49:17 retropi kernel: [ 4930.445204] input: Goodbetterbest Ltd Gioteck VX2 BT Controller as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/input/input2
    Dec 5 14:49:17 retropi kernel: [ 4930.453649] hid-generic 0003:25F0:83C4.0005: input,hidraw0: USB HID v1.11 Gamepad [Goodbetterbest Ltd Gioteck VX2 BT Controller] on usb-bcm2708_usb-1.3/input0
    D

    ldjstyle
    Participant

    So this is my 2nd retropie project and my 1st since version 2.3. I am having a few issues, some that I did not have in my 1st attempt.

    To start I am having difficulty getting a second controller to work for emulated games. I am using 2 different usb snes style controllers. After getting my first one to work by using retroarch-setup my second one will not register. If I run the program again it simply will not register inputs from the next controller but RetroArch recognizes the first controller just fine, any attempt to register another just overwrites the first config file leaving me with one working controller. Any subsequent attempt to copy paste config files has not worked as they do not match the first file I have Input.
    Is there a tutorial for setting up controllers for version 2.3? I got it to work in version 1, but no luck using the same methods.
    My goal is to have 2 snes style controllers and 2 nes style controllers all plugged into a raspberry pi b+. I have edited the config file and no luck, many suggestions have been to copy paste the file and change player 1 to player 2. This has not worked for me since my file does not even differentiate a player, it instead registered 4 different config files, all of which control retroarch, but only one registers as player one in game.

    Secondly. I am searching for a list of rom folders that retroarch uses. I have seen people utilize turbografx 16 roms, but i have no idea which folder to put the roms in, not all of them are intuitive like nes, or snes. After searching I have yet to find a simple list of what each rom folder correlates to in terms of roms to put in.

    Any help would be greatly appreciated. I will happily supply any additional info.

Viewing 35 results - 2,696 through 2,730 (of 3,655 total)