Homepage Forums Search Search Results for 'usb'

Viewing 35 results - 1,296 through 1,330 (of 3,655 total)
  • Author
    Search Results
  • niftylifty
    Participant

    I see a lot of people struggling setting up these controllers with Retropie v3. (myself included). There is a lot of disjointed information floating around that relates to older versions of Retropie. Anyway, I think I’ve finally got it sorted.

    Something to note, after ALOT of head scratching I found the BT on my TV and iPhone were causing interference from time to time, turned them off and my controller was connecting consistently.

    OK, I have found I need the pad in Joystick mode for this to work with the Pi – to do this HOLD START & Right Bumper for 3 secs to start the pad in joystick mode (you must be on latest firmware for this to work).

    Another side note I’m using a SFC30 (other pads should be the same) and a generic bluetooth dongle on a Pi2.

    Let’s begin…

    1. Get latest controller firmware (plug into your PC USB) follow 8bitdo guides for this.

    2. Power on Pi then Putty (ssh) to the Pi from PC or press F4 in emulationstation to get to command line.

    3. Type the following: (agree to any prompts)

    sudo apt-get install bluetooth bluez-utils blueman

    sudo apt-get install bluez python-gobject

    sudo nano /usr/bin/bluez-simple-agent

    EDIT THIS FILE: Once in you need to look for ‘KeyboardDisplay’ and change it to ‘DisplayYesNo’ (please type it as you see it here) Now hit Ctrl + x to save

    Now reboot the Pi with

    sudo reboot

    *************************************************************************

    4. HOLD START & Right Bumper (IMPORTANT) on your SFCS30 controller for 3 secs until it comes on

    Wait a for like 5 secs, then type:

    hcitool scan

    should then get your mac ID (XX:XX:XX:XX:XX:XX),

    type:

    sudo bluez-simple-agent hci0 XX:XX:XX:XX:XX:XX

    sudo bluez-test-device trusted XX:XX:XX:XX:XX:XX yes

    sudo bluez-test-input connect XX:XX:XX:XX:XX:XX

    Now there should be a solid blue light on your controller

    *************************************************************************** ****

    5. Now hold the START on your controller until it turns off

    then reboot your raspberry pi

    At the RetroPie splashscreen loading hold START + RB on your controller to turn it back on

    your blue light should go solid when you get into emulation station

    Run the emulation station configure input wizard, if it doesn’t start automatically plug in a usb controller and click start to get to the configure input wizard.

    Then run RetroArch control input process (Under retropie menu in Emulation Station)

    ******If you want to start fresh or you feel it’s gone wrong:

    REMOVE BLUETOOTH PAIRING only type:

    bluez-test-device remove XX:XX:XX:XX:XX:XX

    REMOVE BLUETOOTH SOFTWARE PACKAGE:

    sudo apt-get --purge remove bluez

    This seems to be the only way I could get it to work properly. I have not tried with multiple bluetooth controllers yet, however I do use mine along with 2 other wired USB pads with no problems.

    #105054
    phoenix
    Participant

    I had the same issue. I don’t think you can really bind buttons from your joystick controller to keyboard inputs.

    I have made two different consoles, one with a USB “zero delay” encoder, and one with arcade controls wired directly to the GPIO.

    I added 3 buttons to the first one, (wired direct to the GPIO) and used GPIOneer to map them (one to ESC, one to “5”(coin), and a couple for pinball. GPIOneer has a nice web interface to change them once you have wired them. It is completely compatible with Retropie.
    http://piplay.org/forum/discussion/1891/gpioneer-a-side-project-compatible-with-piplay/p1?post#Form_Body
    On the other arcade, I used mkjoystick to map the controls and extra buttons to the GPIO: https://github.com/digitalLumberjack/mk_arcade_joystick_rpi

    hope this helps. let me know if you have questions.

    #105048
    fuzzweed
    Participant

    Hi, got an Aimtrak light gun that ‘should’ operate as if it were a mouse. It’s plug and play in windows, and I think it shows up as a USB mouse during boot on the RPi, but it’s not recognised by either Emustation (no game pad/keyboard detected), or MAME (but an actual mouse works fine). Any thoughts on how to get this working?
    Thanks
    I should add that there’s some setup info on the manufacturers website that mentions activating the light gun in mame.ini, but I can’t find this file or equivalent (I guess it’s maybe referring to the windows version?) in RetroPie

    #105046
    Anonymous
    Inactive

    I have a similar issue with a USB arcade stick. Check the axis detection on the pi console. I believe the command is /dev/input/js0 this will let you test the axis, for some reason min had 9 axis and went from 1000 to -1000 and I think that is why it wont pick up for me. But I would try that first.

    #105045
    jakehoms
    Participant

    Hello all,

    My issue is both controller & new-setup related, but since I haven’t really gotten anything to work, I decided we’ll post in this forum.

    My setup:
    RPI Model B
    2 player home built arcade hooked up to a MiniPac (pre-2015)

    I am successful setting up the SD card, and it boots up into emulation station’s main ‘No gamepad detected’ screen. So far so good. I only intend to use the MiniPac, so I hold down on a button (it recognizes the keyboard input) to do the configuring part. This is where I get stuck. Most times, I can map a few buttons, but it’ll eventually freeze and not allow any input from the keyboard and I have to fully reboot the RPi. I have even tried connecting just a basic usb keyboard and it happen as well. I truly just want to get past this configuring section but so far I’ve been stuck here for days trying to figure it out. Here’s what I’ve tried so far (all to no avail):

    – USB keyboard into a USB hub, which runs into the RPi (in case it was a power issue.)
    – Swapping for another RPi (I have two Model B’s)
    – Changing USB keyboards.
    – Re-installing on a new SD card.
    – Changing power adapters for the RPi.

    Right now, I am stuck. I’m confident this can be fixed, either with modifying the script or the resulting config file, but I wasn’t sure what location to modify (I found something in /opt/retropie/all/retroarch.cfg, somewhere like that) but it was more than I wanted to adjust. Also, I don’t think it’s the MiniPac because even when I connect it via just a keyboard, I have an issue.

    Any help I can get would be appreciated. I have this nice arcade all built, but am stuck at this final silly part.

    Thanks,
    Jake

    vertpingouin
    Participant

    Hi everyone !

    I try to add custom buttons in my project. Those button should allow access to save state, loadstate etc… function in retroarch. I plugge my buttons on the GPIO a like described here for example
    http://blog.thestateofme.com/2012/08/10/raspberry-pi-gpio-joystick/

    Then I wrote a little python script in order to map my buttons and trigger some uinput keyboard events.

    from time import sleep
    import RPi.GPIO as GPIO
    import uinput
    
    keypad = uinput.Device([uinput.KEY_N])
    
    GPIO.setmode(GPIO.BCM)
    GPIO.setup(4, GPIO.IN)
    
    pause = .1
    
    while True:
            if (GPIO.input(4)):
                    keypad.emit_click(uinput.KEY_N)
                    sleep(pause)
    

    I launch the script as admin (needed for GPIO python lib).
    The button press detection works without problem.
    When I’m in console, I can see ‘n’ ar input. ‘n’ key is mapped to the “next shader” function in retroarch, this works with a usb keyboard… But not with my buttons.

    Somehow, my script is only effective in console. As long as I launch emulstation or retroarch, it fails.

    Help would be much appreciated. I can’t figure it out and I really want to implement this with python which should bring a great flexibility to my project !

    #105033
    Anonymous
    Inactive

    I get this:

    total 352K
    drwxr-xr-x 2 pi pi 4.0K Aug 28 15:08 .
    drwxr-xr-x 3 pi pi 4.0K Aug 27 12:04 ..
    -rw-r–r– 1 pi pi 546 Aug 27 12:14 2Axes11KeysGamePad.cfg
    -rw-r–r– 1 pi pi 1.4K Aug 27 12:14 8Bitdo-FC30-GamePad-Bluetooth-Mode(START)-Mode(START+R).cfg
    -rw-r–r– 1 pi pi 2.3K Aug 27 12:14 8Bitdo-FC30-Pro-GamePad-Bluetooth-Mode(POWER)-Mode(POWER+R1).cfg
    -rw-r–r– 1 pi pi 2.3K Aug 27 12:14 8Bitdo-FC30-Pro-GamePad-USB.cfg
    -rw-r–r– 1 pi pi 944 Aug 27 12:14 8Bitdo-NES30-GamePad-Bluetooth-Mode(START).cfg
    -rw-r–r– 1 pi pi 1.1K Aug 27 12:14 8Bitdo-NES30-GamePad-Bluetooth-Mode(START+R).cfg
    -rw-r–r– 1 pi pi 1.8K Aug 27 12:14 8Bitdo-NES30-Pro-GamePad-Bluetooth-Mode(POWER).cfg
    -rw-r–r– 1 pi pi 1.9K Aug 27 12:14 8Bitdo-NES30-Pro-GamePad-Bluetooth-Mode(POWER+R1).cfg
    -rw-r–r– 1 pi pi 2.3K Aug 27 12:14 8Bitdo-NES30-Pro-GamePad-USB.cfg
    -rw-r–r– 1 pi pi 944 Aug 27 12:14 8Bitdo-SFC30-GamePad-Bluetooth-Mode(START).cfg
    -rw-r–r– 1 pi pi 1.1K Aug 27 12:14 8Bitdo-SFC30-GamePad-Bluetooth-Mode(START+R).cfg
    -rw-r–r– 1 pi pi 962 Aug 27 12:14 8Bitdo-(S)FC30-GamePad-USB.cfg
    -rw-r–r– 1 pi pi 945 Aug 27 12:14 8Bitdo-SNES30-GamePad-Bluetooth-Mode(START).cfg
    -rw-r–r– 1 pi pi 1.1K Aug 27 12:14 8Bitdo-SNES30-GamePad-Bluetooth-Mode(START+R).cfg
    -rw-r–r– 1 pi pi 962 Aug 27 12:14 8Bitdo-(S)NES30-GamePad-USB.cfg
    -rw-r–r– 1 pi pi 631 Aug 27 12:14 ControlBlockArcadeGamepad.cfg
    -rw-r–r– 1 pi pi 549 Aug 27 12:14 ControlBlockSNESGamepad.cfg
    -rw-r–r– 1 pi pi 889 Aug 27 12:14 Defender_Game_Master_Gamepad.cfg
    -rw-r–r– 1 pi pi 457 Aug 27 12:14 DragonRise_Inc._Gamepad.cfg
    -rw-r–r– 1 pi pi 926 Aug 27 12:14 DragonRise_Inc.___Generic___USB__Joystick__.cfg
    -rw-r–r– 1 pi pi 1.8K Aug 27 12:14 EA_SPORTS_PS3_Football_Club_Wired_Controller_PL-6416.cfg
    -rw-r–r– 1 pi pi 955 Aug 27 12:14 G27_Racing_Wheel.cfg
    -rw-r–r– 1 pi pi 928 Aug 27 12:14 Gamtec.,Ltd_SmartJoy_PLUS_Adapter.cfg
    -rw-r–r– 1 pi pi 860 Aug 27 12:14 Generic_X-Box_pad.cfg
    -rw-r–r– 1 pi pi 876 Aug 27 12:14 Gravis_Destroyer_Tiltpad.cfg
    -rw-r–r– 1 pi pi 919 Aug 27 12:14 GreenAsia_Inc.______USB__Joystick__.cfg
    -rw-r–r– 1 pi pi 857 Aug 27 12:14 GreenAsia_Inc.____USB_Joystick_____.cfg
    -rw-r–r– 1 pi pi 904 Aug 27 12:14 HORI_CO.,LTD__PAD_A.cfg
    -rw-r–r– 1 pi pi 648 Aug 27 12:14 Hori_Fighting_Stick_Ex2.cfg
    -rw-r–r– 1 pi pi 948 Aug 27 12:14 HuiJia__USB_GamePad.cfg
    -rw-r–r– 1 pi pi 955 Aug 27 12:14 iBuffalo_Classic_Usb_Gamepad.cfg
    -rw-r–r– 1 pi pi 478 Aug 27 12:34 INNEXSNESControllerUSB.cfg
    -rw-r–r– 1 pi pi 918 Aug 27 12:14 JessTechColourRumblePad.cfg
    -rw-r–r– 1 pi pi 918 Aug 27 12:14 Jess_Tech_Dual_Analog_Rumble_Pad.cfg
    -rw-r–r– 1 pi pi 932 Aug 27 12:14 kadevice.com_KADE_-_Kick_Ass_Dynamic_Encoder.cfg
    -rw-r–r– 1 pi pi 912 Aug 27 12:14 Logitech_Gamepad_F310.cfg
    -rw-r–r– 1 pi pi 864 Aug 27 12:14 LogitechGamepadF710.cfg
    -rw-r–r– 1 pi pi 878 Aug 27 12:14 LogitechLogitechCordlessRumblePad2.cfg
    -rw-r–r– 1 pi pi 1.8K Aug 27 12:14 Logitech_Logitech_Dual_Action.cfg
    -rw-r–r– 1 pi pi 910 Aug 27 12:14 Logitech_Logitech(R)_Precision(TM)_Gamepad.cfg
    -rw-r–r– 1 pi pi 1.7K Aug 27 12:14 Logitech_Logitech_RumblePad_2_USB.cfg
    -rw-r–r– 1 pi pi 1.6K Aug 27 12:14 Mayflash-GC-to-USB-Adapter_Nintendo-GameCube-Controller.cfg
    -rw-r–r– 1 pi pi 929 Aug 27 12:14 Mega_World_Thrustmaster_dual_analog_3.2.cfg
    -rw-r–r– 1 pi pi 859 Aug 27 12:14 Microntek______________USB_Joystick__________.cfg
    -rw-r–r– 1 pi pi 1.1K Aug 27 12:14 Microsoft(R)Sidewinder(R)_Game_Pad_USB.cfg
    -rw-r–r– 1 pi pi 1020 Aug 27 12:14 Microsoft_Sidewinder_Dual_Strike_USB_version_1.cfg
    -rw-r–r– 1 pi pi 1.8K Aug 27 12:14 Microsoft_X-Box_360_pad.cfg
    -rw-r–r– 1 pi pi 915 Aug 27 12:14 Microsoft_Xbox_Controller_S.cfg
    -rw-r–r– 1 pi pi 1.8K Aug 27 12:14 Microsoft_X-Box_One_pad.cfg
    -rw-r–r– 1 pi pi 627 Aug 27 12:14 MOSIC______USB_2A8K__GamePad__________.cfg
    -rw-r–r– 1 pi pi 1.7K Aug 27 12:14 MP-8800_Quad_USB_Joypad.cfg
    -rw-r–r– 1 pi pi 1.7K Aug 27 12:14 MP-8866_Dual_USB_Joypad.cfg
    -rw-r–r– 1 pi pi 919 Aug 27 12:14 MY-POWER_CO__LTD__2In1_USB_Joystick.cfg
    -rw-r–r– 1 pi pi 1.8K Aug 27 12:14 Nintendo_Wii_Pro_Controller.cfg
    -rw-r–r– 1 pi pi 832 Aug 27 12:14 Play_SEGA_USB_HL-F2412.cfg
    -rw-r–r– 1 pi pi 833 Aug 27 12:14 Qnix_SNES_Replica.cfg
    -rw-r–r– 1 pi pi 438 Aug 27 12:14 raphnet.net_4nes4snes.cfg
    -rw-r–r– 1 pi pi 732 Aug 27 12:14 Retrolink_Nintendo_64_Classic_USB.cfg
    -rw-r–r– 1 pi pi 565 Aug 27 12:14 Retrolink_USB_SEGA_Saturn_Classic_Controller.cfg
    -rw-r–r– 1 pi pi 793 Aug 27 12:14 Saitek_P880.cfg
    -rw-r–r– 1 pi pi 860 Aug 27 12:14 Saitek_P990.cfg
    -rw-r–r– 1 pi pi 888 Aug 27 12:14 Saitek_PLC_P2600_Rumble_Force_Pad.cfg
    -rw-r–r– 1 pi pi 921 Aug 27 12:14 Saitek_X52_Flight_Control_System.cfg
    -rw-r–r– 1 pi pi 947 Aug 27 12:14 SLS-Sega-Saturn-USB-Gamepad.cfg
    -rw-r–r– 1 pi pi 546 Aug 27 12:14 SNES-to-GamepadDevice.cfg
    -rw-r–r– 1 pi pi 1.8K Aug 27 12:14 Sony-PlayStation3-DualShock3-Controller-Bluetooth.cfg
    -rw-r–r– 1 pi pi 1.8K Aug 27 12:14 Sony-PlayStation3-DualShock3-Controller-USB.cfg
    -rw-r–r– 1 pi pi 1.8K Aug 27 12:14 Sony-PlayStation4-DualShock4-Controller.cfg
    -rw-r–r– 1 pi pi 920 Aug 27 12:14 Thrustmaster_Dual_Trigger_3-in-1.cfg
    -rw-r–r– 1 pi pi 874 Aug 27 12:14 THRUSTMASTER_FireStorm_Dual_Analog_2.cfg
    -rw-r–r– 1 pi pi 841 Aug 28 15:08 ThrustmasterThrustmasterdualanalog3.2.cfg
    -rw-r–r– 1 pi pi 907 Aug 27 12:14 Thrustmaster_T_Mini_2.cfg
    -rw-r–r– 1 pi pi 868 Aug 27 12:14 Thrustmaster_T_Mini_Wireless.cfg
    -rw-r–r– 1 pi pi 711 Aug 27 12:14 THRUSTMASTER_Top_Gun_Fox_2_Pro.cfg
    -rw-r–r– 1 pi pi 686 Aug 27 12:14 TOMEE_N64_USB_CONTROLLER.cfg
    -rw-r–r– 1 pi pi 883 Aug 27 12:14 Twin_USB_Joystick.cfg
    -rw-r–r– 1 pi pi 553 Aug 27 12:14 USB_2-axis_8-button_gamepad.cfg
    -rw-r–r– 1 pi pi 594 Aug 27 12:14 USBgamepad.cfg
    -rw-r–r– 1 pi pi 1.1K Aug 27 12:14 USB_Gamepad_.cfg
    -rw-r–r– 1 pi pi 886 Aug 27 12:14 USB_Vibration_Joystick.cfg
    -rw-r–r– 1 pi pi 634 Aug 27 12:14 Xarcade-to-Gamepad-Device.cfg
    -rw-r–r– 1 pi pi 1.8K Aug 27 12:14 Xbox_360_Wireless_Receiver.cfg
    -rw-r–r– 1 pi pi 1.8K Aug 27 12:14 Xbox_360_Wireless_Receiver_Chinese01.cfg
    -rw-r–r– 1 pi pi 853 Aug 27 12:14 XboxGamepad(userspacedriver).cfg
    -rw-r–r– 1 pi pi 867 Aug 27 12:14 Zeemote_SteelSeries_FREE.cfg
    -rw-r–r– 1 pi pi 1.8K Aug 27 12:14 Zeroplus_PS_Vibration_Feedback_Converter_.cfg

    #105024
    steven009
    Participant

    Did you come up with a solution? I am having the same issue.

    New pi2b, downloaded and booted the sd image. It gives me “Welcome, No gamepads detected” screen. I hold a button on the keyboard and it gives me the “Configuring Keyboard” screen. I assign buttons for everything, and then it highlights “OK” at the bottom. I can use the up/down keys to scroll up and down the list of keys, but nothing I press will get past the screen (except F4, but it doesn’t seem to save the config).

    I don’t think it’s an issue with the keyboard; I have tried more than one, and I don’t have anything else plugged into USB so I doubt there’s an issue with the power draw.

    I have tried manually editing es_input.cfg but either it isn’t loading or my file is invalid (does anyone have a working example?)

    #105017
    niksteve70
    Participant

    Awesome, one last thing is there anyway I can move the downloaded images file (i.e. Where the game covers are located) to my USB hard drive, so I don’t fill up my sd card. I already am able to play my roms from the usb hard drive

    Anonymous
    Inactive

    Hi,
    I’m trying to make my USB Gamepad Controller (Thrustmaster) work in mame4all but I can’t do it. It’s weird… When I press “TAB” key and enter in the menu, I go to the UP, Down, Right, Left options with enter and then push the pad and nothing happen, the buttons works great but not the pad… anyone knows what could be happening?
    The pad works great on SNES, the emulstation menu, even FBA.

    thehoff
    Participant

    Hi all,

    I’m experiencing an odd issue with psx/emulationstation. Whenever I start emulation station directly from the command line (through SSH on my pc) everything works fine:
    $ emulationstation
    However, when I start it through a homemade script the games from the psx emulator (and likely also all other emulators) won’t load. The screen will just go black for a few seconds and return to the emulator menu. I’ve made a very simple example in which it fails. A script called emulation.sh with the following content:

    #!bin/sh
    /usr/bin/emulationstation
    

    I then execute this script:
    $ sh emulation.sh

    Additional information:
    Pi Model: 2B
    Built from: binary
    Retropie version used: I suppose it’s version 3.0 since I’ve downloaded and ran the script just 2 days ago.
    USB devices connected: 2TB external harddisk, 2 usb playstation controllers
    controller used: playstation controller
    Error messages received: None

    I have absolutely no clue what could possibly go wrong at this point. Any advice on what to look for?

    #104997

    In reply to: 2.6 pi2 Mame No Sound

    Anonymous
    Inactive

    I am a noob to the Raspberry pi and Retropie and i dont know where to add it. Do you have to write script on the raspberry, or edit it on the usb? If so where do i need to edit it? Just type it on the end?

    ronearp
    Participant
      I’m a unix idiot so I need to state that upfront.

    I have previously setup a few systems with retro pie and older versions of emulation station though.

    I’m running the new Emulation Station 3 beta on Rpi B+. I need to get my ROMs copied over from USB stick to the SD card but I don’t know how to do it. I understood that when I booted this new version with a USB stick some unix utility would create directories on the USB stick that I could then populate from my PC. That doesn’t seem to happen though.

    With the older Emulation Station / RetroPi I used to use “StartX” and I could use that graphical user file manager to move the files from USB. But StartX doesn’t seem to work on the new v3 beta image.

    My understanding is that the unix system needs to mount the USB drive but my guess that isn’t happening. I don’t actually know how to check if that is occurring or not from the command line.

    I have run the Midnight Commander file manager under EmulationStation but I don’t see the USB stick there either.

    Any help you can offer would be very welcome.

    #104985

    In reply to: ROM Trouble

    zelphy
    Participant

    Nope, all unzipped and synced via the auto USB stick updater. I reinstalled RetroPie but still having trouble :/

    #104950
    mikegold
    Participant

    I have noticed so far that disabling overscan removes the black bars on all screens I have at home (65”, 32”, 24”). All full HD and all Samsung.

    I was wondering what would be the perfect resolution for the emulators. I guess You are right setting the resolution this low. But what about the Street Fighter, X-man etc. from arcade machines? Are those also only native 640p?

    I didn’t had the chance to check yet, but is Your build of OpenElec supporting advanced subtitles in the mkv files (on my old basic system I had to do this: sudo apt-get install libass-dev to get subs in mkv) ?

    With Your newest build my old nemesis came back – Xbox 360 wired gamepad setup. Basically after installing xbox pad driver I can have either working in retroarch pad with blinking led (by setting it up according to retropie guide), or properly lighted pad working only in emulationstation. In the end I gave up, used my old basic pi backup and copied the “all” folder with all retroarch settings. Now it works as it should again :).

    The error I mentioned before with missing files is visible on attached photo (the beginning of the message is cut, but it says lvl0: in each line.

    Lastly… Is it possible to lower the space available on OpenELEC partition? I’ve noticed that I had to sacrifice a good few games for it, and if I’ll ever use Media Center, I’ll either use LAN or USB stick.

    Thanks for Your help again!

    #104933
    Anonymous
    Inactive

    I’m having exactly the same issue. What I did:

    in /opt/retropie/configs/all/retroarch.cfg

    input_enable_hotkey = alt
    input_load_state = f4
    input_save_state = f2
    input_exit_emulator = escape

    and commenting out in /opt/retropie/configs/all/retroarch-joypads/GenericUSBJoystick.cfg

    #input_enable_hotkey_btn = “7”
    #input_exit_emulator_btn = “9”
    #input_reset_btn = “8”
    #input_load_state_btn = “4”
    #input_save_state_btn = “5”
    #input_state_slot_increase_btn = “h0right”
    #input_state_slot_decrease_btn = “h0left”
    #input_menu_toggle_btn = “0”

    Basically I’m saving and exiting my n64 emulator via keyboard.
    Unfortunately I haven’t found a better solution. :-(

    #104926
    petrockblog
    Keymaster

    re-install emulationstation from binary via menu 5 of retropie-setup and it will reset its input configuration.

    However it sounds like you might have another issue, as it should be able to pick up the keyboard despite your changes. With USB devices not working as they should, the first thing to check is PSU and USB cable – as if the pi isn’t getting enough power than can cause problems.

    #104918

    In reply to: USB audio device

    renrom
    Participant

    Tested it, and the /etc/asound.conf is realy neccesary to make the usb sound work with ES.

    #104909
    time
    Participant

    Hi!

    I installed Retropi 3.0 with USB keyboard and it was working while ago.

    I wasn’t happy the way keyboard was mapped in the first run and I tried to do remapping by deleting the es_input.cfg file found in:

    /.emulationstation/es_input.cfg

    Now when I press a key from the keyboard, the emulation station shows up that in can recognize the keyboard, but this time I’m not able to map any keys (the OK button just stays grayed out and it just displays the text “Hold a button on your device to configure it…”).

    Is there a way to proceed from this to somehow? I can connect the device via SSH, would I be able to get some default es_input.cfg from somewhere and edit that?

    Thanks already…

    #104898

    In reply to: Usb hub, a necessity?

    krauthaus
    Participant

    I bought the Controller and Buttons in a set at ultracabs, a uk Company.

    http://www.ultracabs.co.uk/usb-interface–standard-joystick-set-109-p.asp

    <- They have a really good Service and the Prices are ok:)

    sonofabit
    Participant

    Hi!
    I´ve just started my first arcade project but got some problem with the controllers that I hope you guys could have a solution to. ;-)
    Built an prototype and attached all the Sanwa buttons och the joystick to the USB-controller board. After that I installed RetroPie on my Raspberry Pi 2 Model B and everything works fine. The joystick and all the controller buttons works fine in the RetroPie OS. But when I start the NES or SNES emulator the Start/Select buttons doesn´t work and the A/B buttons are no longer on the right place as I set in the configuration. What´s up with that? :-) Do I have to change something in the configuration file to set up the controllers for each emulator?

    Best regards,
    Anders

    #104893

    In reply to: Usb hub, a necessity?

    krauthaus
    Participant

    I run a self-build bartop arcade without a hub.

    This is plugged in my pi2:

    -Wlan Stick
    -USB Joystick (Xin Mo Controller)
    -Wireless Keyboard
    -VGA-HMI Adapter Usb Power Cable.

    In my opinion a hub is not necessary.

    Raspberry/Retropie Arcade Gaming Cabinet

    #104892
    ron-a-tron
    Participant

    I’m planning my ipac 2 console build and was wondering should i factor in a powered usb hub. I only planned to have a ipac controller and a pi powered by a power cable.

    Will a powered hub be a necessity?

    Thanks

    Anonymous
    Inactive

    Hello everyone!
    Im pulling my hair out trying to fix this lol
    Im building a weecade clone and have purchased a zippy joystick and buttons kit from ebay which included a xin mo clone (JUYA0 Dual arcade) usb controller.

    This one here

    http://fr.aliexpress.com/item/Xin-Mo-Arcade-to-USB-controller-2-player-MAME-Multicade-Keyboard-Encoder-USB-to-Jamma-game/1375035840.html?recommendVersion=1

    The device is plug n play in windows and works fine.
    But retropie and emus cannot detect the device.

    im using raspberry pi 2 B on retropie 3.0.0 rc1 (beta 2 tried also)

    When i run the device list command i get this result

    I: Bus=0003 Vendor=0314 Product=0126 Version=0110
    N: Name=”Arcade Controller JUYA0 Dual Arcade”
    P: Phys=usb-bcm2708_usb-1.3/input0
    S: Sysfs=/devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/input/input0
    U: Uniq=
    H: Handlers=mouse0 event0
    B: PROP=0
    B: EV=1b
    B: KEY=fff ffff0000 0 0 0 0 0 0 0 0 0
    B: ABS=f00ff
    B: MSC=10

    The handler is set to mouse instead of joystick.

    I’ve searched the net for days and saw only one guy had this problem but no one helped him out.

    Can anyone help me please? Id be greatly appreciated.

    Thanks. Daniel.

    #104885

    In reply to: Autofire on the axis

    krauthaus
    Participant

    My solution yesterday:

    1st Step: Fresh new 3.0 Retropie Installation (with the boot/config entry a few Posts above -> usbhid.quirks=0x16c0:0x05e1:0x040 )

    2nd Step: Added Games and Scraped them

    3rd Step: A Backup of the SD with Win32DiskImager

    4rd Step: Applied feederchains Kernel Patch (I had the same Problem like you. In snes games, for example, Both Joysticks moved Player one because they had the same axis entrys.)

    Step 5: Modded the “all” config file like this:

    input_player1_joypad_index = 0
    input_player1_a_btn = 2
    input_player1_b_btn = 1
    input_player1_y_btn = 0
    input_player1_start_btn = 6
    input_player1_up_axis = -1
    input_player1_down_axis = +1
    input_player1_left_axis = -0
    input_player1_right_axis = +0

    input_player2_joypad_index = 0
    input_player2_a_btn = 10
    input_player2_b_btn = 9
    input_player2_y_btn = 8
    input_player2_start_btn = 14
    input_player2_up_axis = -3
    input_player2_down_axis = +3
    input_player2_left_axis = -2
    input_player2_right_axis = +2

    Step 6: PLAYING! After this steps every SNES Game worked for both Players.

    I wired the Buttons and Joysticks a few months ago. But i think i wired the second Joystick not like it should be. I reversed the cables. (I wired “up” to “down”, “left” to “right” and so on.)

    :D

    And again: THANK YOU AWESOME GUYS FOR THIS! :D :D :D

    #104871

    In reply to: USB audio device

    lilbud
    Participant

    Use this website http://plugable.com/2014/11/06/how-to-switch-to-usb-audio-on-raspberry-pi works perfectly, and it automatically switch depending on if the adapter is plugged in on boot.

    #104851
    darksavior
    Participant

    USB xbox 360 stick for arcade games
    USB PC-Engine controller for pce/nes games (soldered a usb chip inside)
    Soldered sfc controller ports to gpio so I can use original snes/sfc controllers
    For kodi I use the yatse remote control app for android

    #104842

    In reply to: USB audio device

    renrom
    Participant

    Ok, after digging around a bit, this seem to work:

    Creating a file /etc/asound.conf with the following:

    ctl.!default {
    type hw
    card 0
    }
    pcm.usb
    {
    type hw
    card "U012529205"
    format S16_LE
    }
    
    pcm.!default {
    type asym
    playback.pcm
    {
    type plug
    slave {
    pcm "hw:0"
    format S16_LE
    }
    }
    capture.pcm
    {
    type plug
    slave.pcm "usb"
    }
    }
    

    and comment the line ‘options snd-usb-audio index=-1’ in the /etc/modprobe.d/alsa-base.conf

    Only part what still dont have sound is the splashvideo, will try figure out that one aswell. :)

    #104839
    renrom
    Participant

    Hi,

    I want to use an USB audio device with the Pi2. After installing it, no games are started anymore. The following error i can see quickly on the screen:

    lvl0: VolumeControl::init() – Failed to find mixer elements

    In the /tmp/runcommand.log this error is showing up:
    ALSA lib pcm.c:7431:(snd_pcm_set_params) Rate doesn’t match (requested 44100Hz, get 0Hz)

    If i try to play a sound from the commandline with aplay /usr/share/sounds/alsa/Front_Left.wav it does play the sound.

    Any idea to fix this?

    dashizzle
    Participant

    Does anyone know how the synchronization usb drive works? Is it true sync? Which one is the master, the sd card or the usb drive? I don’t want it to delete roms accidentally as well as if I delete roms on the sd card I would like that it would sync and delete them from the usb drive.

    daweze
    Participant

    i also found that ps3 over Bluetooth is not working in Mame4All but it you plug up the usb cable to the same ps3 controller and reboot it works perfect over usb. I also found if you user the ir-iMame4All emu instead the controller works fine over Bluetooth. the same goes for FBA.

    #104809
    gonzothegreat
    Participant

    this guide is good too..
    InsecureSpike has mentioned this in a few of this posts….

    i use it and always the extended procedure… it uses the usb device’s Partition unique GUID & Filesystem UUID incase you have any other usb storage on your Pi, for example if your using it for Retropie & another OS/distro also from what i gather its safer than just assigning drive names

    https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=44177&hilit=move%2broot%2bfs%2busb%2btutorial&sid=2503f9ffe9afaa2edb49aef4537a862a

    #104807
    tgilly
    Participant

    Perhaps some more information or another or the same approach https://www.petrockblock.com/forums/topic/how-to-run-from-usb-the-best-method/

    #104796
    momaw27
    Participant

    http://mardell.me/blog/how-to-load-roms-from-a-usb-drive-on-retropie/

    I think this is what I used to play off of my thumb drive.

    niksteve70
    Participant

    Hey everyone
    I was wondering if you can help me with a problem, I am trying to play my roms and psx games through my Expansion Drive but cannot figure out how to get the roms to show up in Emulation Station. I have a Raspberry Pi 2, am using RetroPie 3.0, and I am trying to play my games off of a Seagate 2TB expansion drive. It would great if you could help me with this.

Viewing 35 results - 1,296 through 1,330 (of 3,655 total)