Homepage Forums Search Search Results for 'usb'

Viewing 35 results - 1,681 through 1,715 (of 3,655 total)
  • Author
    Search Results
  • mors3
    Participant

    …ok, well that hasn’t quite to plan, just finished wiping the drive and putting beta3 retro pie onto it, and same issue.

    Full info:
    used gparted on my ubuntu laptop to wipe partitions on the USBHDD and create a new flat ntfs partition (not sure this is necc as I think when you apply an image to a device it goes over all the partition info, but safer>sorry)

    downloaded a fresh version of the beta3 image to ubuntu

    used dd through ubuntu to apply the beta 3 image to the USBHDD

    booted the pi2 using the USBHDD

    first screen when retropie finishes loading is:
    WELCOME
    no gamepads connected
    hold a button..
    press f4 to quit

    pressing f4 has no effect, using a ssh terminal I then find and kill the retropie process which quits me back to commandline, where the keyboard works as expected.

    #99184
    karloss
    Participant

    It seems the controller does have the spaces as in my retorarch config and the es_inputs, they are named with a space..

    “DragonRise Inc. Generic USB Joystick ”

    So it seems the space is correct, but for some reason, its like it loads the config, then removes the blankspace? and then it cant recognize to controller, so it creates a new entry, and it kinda keeps going round and round…if u get me?

    #99181
    karloss
    Participant

    I have been watching this thread and I must say, I am really happy with what you are doing for us :)

    though, I seem to be having a problem… :(

    I am trying to use my “DragonRise Inc. Generic USB Joystick ” gamepad, it works for everything else, and start/A/B work in reicast as standard, I just updated to your latest build, and upon running reicast it has pulled out

    [DragonRise Inc.   Generic   USB  Joystick  ]
    button.0=
    axis.0=
    button.1=
    axis.1=
    button.2=
    axis.2=
    button.3=
    axis.3=
    button.4=
    axis.4=
    button.5=
    axis.5=
    button.6=
    axis.6=
    button.7=
    axis.7=
    button.8=
    axis.8=
    button.9=
    axis.9=
    button.10=
    axis.10=
    button.11=
    axis.11=
    button.12=
    axis.12=
    button.13=
    axis.13=
    button.14=
    axis.14=
    button.15=
    axis.15=
    button.16=
    axis.16=
    button.17=
    axis.17=
    button.18=
    axis.18=
    button.19=
    axis.19=
    button.20=
    axis.20=
    button.21=
    axis.21=
    button.22=
    axis.22=
    button.23=
    axis.23=
    button.24=
    axis.24=
    button.25=
    axis.25=
    button.26=
    axis.26=
    button.27=
    axis.27=
    button.28=
    axis.28=
    button.29=
    axis.29=
    button.30=
    axis.30=
    button.31=
    axis.31=
    

    To my emu.cfg file, so up updated it and added some Btn_ to check if it was working (quit seemed the obvious button to set)

    button.1=Btn_A
    button.2=Btn_B
    button.8=Quit
    button.9=Btn_Start

    But when I restart reicast my controller has no default functions than normal and if I check the config again, It has created a new entry for my controller and is not using the config I set..

    This seems to be the issue…

    When it is first created in the config it is called

    [DragonRise Inc. Generic USB Joystick ] (notice the spaces at the end)

    So I make changes to that entry and restart, when I check the config after its been renamed to

    [DragonRise Inc. Generic USB Joystick] (notice no spaces)

    and a new entry is created underneath

    [DragonRise Inc. Generic USB Joystick ] (with spaces again)

    So it seems that the one with spaces is the one I want, but it seems to rename it and create a new one each time…any ideas??

    Thanks

    Karl

    #99123
    nogre
    Participant

    I built a fully set up RetroPie game box as a gift for my brother’s birthday. He’s smart, but doesn’t have experience with the Raspberry Pi or RetroPie Project. So I wrote up a QuickStart guide so that he would be able to get gaming immediately:

    REKt QuickStart Guide

    Congratulations on your purchase of a RetroPie Entertainment Kit (REKt)! Now that you’ve gotten REKt, you can proceed to crush all your friends, and enemies, in classic arcade game style.

    Your kit includes:

    1 Raspberry Pi model 2B
    1 Raspberry Pi model 2B case
    1 32g Micro SD card
    1 USB Classic Gamepad
    1 Power Adapter
    1 HDMI cable
    various decorative stickers

    Your kit has come preinstalled and preassembled for ease of use. This still leaves only a few steps to glory:

    1. Plug the HDMI cable into your TV and REKt.
    2. Connect the USB Gamepad to REKt.
    3. Connect REKt to power. This should turn REKt on.

    If your TV is on and set to the correct input, you should see REKt loading. This can take a minute or two, mainly to load the HUGE number of games that REKt comes with. (If you don’t get to a loading screen, unplug the power, give it a few seconds and plug it back in.)

    4. Choose your game system and game of choice using the gamepad, and become a video game hero!

    Important Notes:

    • Getting back to the REKt console (emulation station) from within a game is as easy as holding the SELECT and START buttons at the same time.
    • In MAME, adding coins and player_start can be achieved by holding SELECT and pressing the L or R buttons on the top of the gamepad. START pauses the game, and START + R brings up the Advance Mame options.
    • The game systems have been unthoroughly tested and will likely work with varying success. MAME especially is prone to this, but happily the system was beta-tested with Michael Jackson’s “Moonwalker” and we can report that the last listed ROM works well.
    • There appears to be some trouble with game metadata. For instance, the game-box image and game description can be added to enhance the REKt console. However, this drastically increased the system load time. To ensure as many barriers to gaming were removed as possible, this feature was foregone.
    • The firmware at time of shipping was Version 3.0 BETA 2. So, while mostly stable and feature-rich, there could be a few bugs here and there.
    • Currently shipping systems with ROMS included: Atari 2600, NES, SNES, SEGA Genesis (Megadrive), GameBoy Advance, MAME. Many other systems are available.

    Get more info at:

    The RetroPie Project – https://www.petrockblock.com/retropie/

    Emulation Station – http://emulationstation.org/

    mheyman
    Participant

    HELLO!

    I’ve been searching everywhere for a definitive answer and have found just a lot of people hitting the same wall as I am.

    All I want to do is set up my Raspi to use a keyboard as player 1’s controls and a usb controller as player 2’s.

    Currently if I have a keyboard and a USB controller (like an XBox One controller) plugged in they both try to act as player 1 and nothing gives input to player 2.

    I have tried things like this:

    sudo ./retroarch-joyconfig -j 0 >> /opt/retropie/configs/all/retroarch.cfg
    

    No matter what I try I get this response:

    RetroArch: input_joypad_init_first: Found joypad driver: “udev”.
    Couldn’t open joystick #0.

    I’ve tried changing the number after “-j” to 0, 1 and 2 and nothing fixes this.

    Any thoughts? Ideas? step by step tutorials would be appreciated !

    #99099

    In reply to: Basic initial setup?

    herbfargus
    Member

    Run raspi-config first and expand your filesystem then reboot and then the setup script will work

    https://github.com/retropie/RetroPie-Setup/wiki/First-Installation-(RetroPie-SD-Image-2.6)

    I also have a YouTube channel (https://youtube.com/channel/UCYdB7MovoH6yCzkVjTXeiIw) going step by step through each configuration, its a bit dated but it will cover for a lot of it. Floob and techtipsta also have really helpful videos. I will update the wiki once the latest beta is released since there will be some different (but easier) configurations particularly when it comes to controllers.

    Also if you installed retropie 3.0 you need to create a folder on your USB called retropie first see here:

    https://github.com/retropie/RetroPie-Setup/wiki/How-to-get-ROMs-on-the-SD-card

    Then it will populate the ROMs folder once plugged into your pi, then you place your ROMs in the newly created folders and then plug back into the pi, once it stops blinking press f4 to refresh emulation station so your ROMs will show up or you can just reboot.

    #99097

    In reply to: Basic initial setup?

    vmsean
    Participant

    Follow up – I was able to create the ROMs directory on my USB card; and I copied all my roms. But when I start up RetroPie, it just takes me to the menu. When I choose the setup option, it sits there for a minute, and takes me BACK to the menu.

    #99096
    vmsean
    Participant

    I can’t believe there isn’t a step-by-step guide to getting started. Or, if there is, it’s pretty hard to find. I have my roms, I have my pi-2, I have my sd-card, and I have my download. I *assume* you write the retropie image to the sd-card. Score! it boots up… but it complains that there are no roms. I have my roms on another USB… there is no “roms” directory on the sd-card… can somebody point me in the right direction? What’s next??

    #99095
    sekazi
    Participant

    [quote=97712]This is what I use:

    1. sudo vi /etc/rc.local

    2. Add the following code at the end, just before the “exit 0″ line:

    echo Waiting for controller
    while ! ls /dev/js* 1>/dev/null 2>&1
    do
    sleep 1
    done
    echo Controller found

    3. Save

    4. Reboot

    What this does is wait indefinitely at bootup until a controller is connected. It works perfectly for my PS3 controller over either bluetooth or USB.

    [/quote]

    What do I need to do to get it to stop after 5 seconds of not connection? I got it to work with my RetroPie but if it does not detect I would like it to eventually skip to emulationstation.

    To get it to work I had to change /dev/js to /dev/input/js

    thebko
    Participant

    Hi,

    i plug my arcade buttons ans stick with a USB interface. All stick and buttons are recognized in mame emu. The only problem is the slowness when i maintain left or right stick.

    For example, in a shoot em up like space invaders, if i maintain left or right, the ship moves but slowly. I feel that there is a dead time between each right or each left. If i use the keyboard, the ship moves normally.

    Can you help me ?
    Thanks a lot

    #99016
    patrickm
    Participant

    Would it not be easier to just change the path option for each emulator in the es_systems.cfg so that each emulator points to the desired folder on a usb drive? This is what I’ve done, and my games load and save fine this way.

    Is there some additional stability or performance advantage to also running the emulators themselves from USB?

    #98963

    In reply to: Bluetooth Dongle issue

    goobatroopa
    Participant

    I have an update. If I remove the dongle prior to turning on, turn on the Pi and then plug in the dongle, it works. But it will not work if its already in the USB slot prior to booting. Anyone know what this could be?

    tgilly
    Participant

    Hi all,

    First of all, I love retropie !

    Pi Model: 2
    RetroPie Version Used: 3.0.0 Beta 2
    Built From: SD Image
    USB Devices connected: Keyboard, Wireless XBOX 360 Receiver, WiFi Card
    Controller used: XBOX 360 (Wireless)
    Error messages received: None
    Guide used: Wiki Guide for XBOX 360 controller (Option 3)

    I managed to get my 2 controller correctly setup in RetroArch.cfg and the emulators which use this config are working, but only when I don’t have the keyboard attached. When the Keyboard is attached, it will always be assigned as P1.

    Sometimes I need the keyboard (config of Retroarch etc..). Is there a way that I can assure that the system uses my XBOX 360 controllers as P1 and P2 AND that the keyboard can be used to change config (hotkeys …) ?

    Thanks

    #98931
    dishins
    Participant

    [quote=98884]Hmm, I should mention I am using a genuine PS3 controller over bluetooth. Haven’t tried over USB yet, it might show up a bit differently there. I’ll have to figure out how to bring the control mappings out to an ini file.

    [/quote]

    i’m using the PS3 controller over bluetooth too, however the key mapping didn’t worked fine for me :(

    #98916
    free5ty1e
    Participant

    Hi karloss!

    No worries; I added sensible controller-name-based detection that will only apply the PS3 mapping and Quit buttons if a PS3 (or Sony) controller is detected. Otherwise, the default USB gamepad map and the XBOX 360 controller maps will work as before.

    Also, that’s a bash script – you can just copy / paste that into an SSH terminal window to the Pi and have it work (minus the #!/bin/bash line), or just paste the entire thing into a new file and call it installReicastExperimental.sh or something like that. Then just run that script to build the latest Reicast.

    I’m currently rebasing these changes so they are palatable for a pull request to the master branch, as I plan to have this all fully compatible with non-Pi Reicast builds too. I want this to be easy to keep up to date with the latest enhancements from the upstream repo…

    And then yes I am going to figure out how to bring the controller mappings out to an .INI or .CFG file so they are no longer hard-coded into the damn source. :D

    smegz0r
    Participant

    Pi Model: 2B
    RetroPie Version Used: 3.0.0 Beta 2
    Built From: SD Image
    USB Devices connected: Madcatz Street Fighter 4 Xbox 360 controller
    Controller used: Madcatz Street Fighter 4 Xbox 360 controller
    Error messages received: See below
    Guide used: None, just flashed using Win32 Disk Imager
    File: /home/pi/RetroPie/roms/snes/ActRaiser.smc
    Attachment of config files: No changes from default
    How to replicate the problem:

    I’ve uploaded a few SNES roms to this installation from the downloaded 3.0.0. Beta 2 SD Image. When I try to launch any (eg. ActRaiser above) I get a blank screen asking me to press x or m to configure launch options and that the Sound Buffer has been initialised to 4096 samples. The screen hangs. /tmp/runcommand.log contains the following:

    RetroArch: rarch_log_libretro: [libretro INFO] :: Frontend supports RGB565 – will use that instead of XRGB1555.
    RetroArch [ERROR] :: load_content_dont_need_fullpath :: Could not read content file “/home/pi/RetroPie/roms/snes/ActRaiser.smc”.
    RetroArch [WARN] :: gl_glsl_init :: [GL]: Stock GLSL shaders will be used.
    RetroArch [WARN] :: udev_input_init :: [udev]: Couldn’t open any keyboard, mouse or touchpad. Are permissions set correctly for /dev/input/event*?

    Any ideas?

    #98884
    free5ty1e
    Participant

    Hmm, I should mention I am using a genuine PS3 controller over bluetooth. Haven’t tried over USB yet, it might show up a bit differently there. I’ll have to figure out how to bring the control mappings out to an ini file.

    #98851
    bwolf17666
    Participant

    Hey Sorry for the Late reply. What I have discovered and explored is using two USB trackballs ach device is recognized as it’s own input (mouse), registering as /dev/input/js0 and /dev/input/js1 then in your retroarch.cfg you just apply player 1 to js0 and player 2 to js1.

    You can also view the devices using lsusb.

    I dont really know much about marble madness so I’m not sure whats up with that.

    chickens
    Participant

    As the title states, certain buttons will not register while I’m doing SNES emulators.
    I’ve tried running the Retroarch controller setup, and it detects all the buttons on the controller. (Which is a generic USB SNES controller)
    I know that they work correctly in the NeoGeo emulator (although they’re mapped incorrectly).
    I’m running Retropie V3 B2, on a Raspberry Pi 2.

    Any thoughts?

    #98845
    chiefer
    Participant

    Hi guys first time poster :)

    Thought I wouldn’t bother with a new thread as this seems apt.

    I tried posting on the EmulationStation forums without reply, and have done as much search as I can.

    Am running Retro Pie 3 on a RPB with a NES USB controller

    I’ve mapped the retroarch buttons everywhere I can within the interface and the ‘B’ registers, but in game for some reason the B button doesn’t work.

    Any ideas?

    #98842

    In reply to: Lightgun support?

    Anonymous
    Inactive

    Naturally, this is accomplished using a PC, something with more Horsepower than a Raspberry PI, but if you have a Wiimote, a USB Bluetooth adapter, some coding know-how, and a lot of time on your hands, well, by all means, go for it…

    eldo73
    Participant

    Hi, I watched Floob’s video (all 60 minutes!) on config files in v3b2, and I’m sure the info was in there, but I’m going to have to go back and take detailed notes, I think. In the meantime, can anyone tell me how to specify a controller per emulator?

    I’ve built a small console device that has 2 sets of arcade style controls interfaced using the xin-mo usb controller. After a bunch of mucking around, it actually works pretty good. I also have a Logitech dual action usb gamepad that I’d like to use for it’s analog joysticks, basically in the n64 and psx titles. Everything works fine if I plug and unplug the appropriate controllers, but is there a way to specify that the Logitech is to be used for player 1 in those two emulators, while the xin mo is used for P1 in the others? Any help is appreciated!
    Jared

    #98756
    Anonymous
    Inactive

    My problem is when i install Retropie on Raspbian, the usb sincronization don’t work even turn on it in retropie setup. What is the problem?

    braincell
    Participant

    Ok… this is rediculous . Im going to bulk rename leaving just filename then scrape from windows …. copy to usb and see what happened

    braincell
    Participant

    Emulationstation is definately not running .

    As i said i even copied the rom folders onto a usb stick.

    I read through the xml files and couldnt aee any errors.

    What i dont understand is the freezing on the system selection screen ???????

    Its only a handful of xml files and a lot of thumbnail images. So is it a memory leak?

    Are the xml files parsed at startup or during sustem selection??

    Why does it take a few games to freeze up ????

    braincell
    Participant

    I too am having lockups after scraping with this tool.

    It lets me play 3 or 4 games then locks up , and it has also locked up on the system selection screen too ??

    have tried with rpi 1 and rpi 2 with different psus and different sd cards ….. its definately the scaping.

    i even copied the rom folders to a usb and did a fresh install then allowed ES to copy the roms back into the installation and it locks up again ?????

    what is causing this ???????

    cedifra
    Participant

    Hey guys,

    Thanks for reading.

    I am receiving a few weird error messages.

    My CPUs seem to work fine tho.

    And what means:

    map: vt01 => fb0?

    [attachment file=”error3.JPG”]

    Error

    Thanks!

    ///
    Raspberry Pi2b
    RetroPie Version Used: 2.6
    Built From: SD Image
    USB Devices connected: Keyboard, XinMo Dual Arcade
    ///

    #98693
    cedifra
    Participant

    Hello guys,

    Thanks for reading.

    ///
    Raspberry Pi2b
    RetroPie Version Used: 2.6
    Built From: SD Image
    USB Devices connected: Keyboard, XinMo Dual Arcade
    ///

    I am using a HDMI to DVI cable to connect my BenQ E900T. It works perfectly at first. I run a the SNES Emulator and can play a game. If I now exit the emulator, the screen is suddenly tinted and stays that way:

    NORMAL STILL

    TINTED RED

    It happens with: NES, SNES

    But not with GBA, which uses another BIOS.

    Thanks!!!!

    #98682
    philmw60
    Participant

    I got it working!

    I used the Wireless Gamepad F710 Connect Utility in my windows machine to do initial config between the gamepad and the receiver. Now it works with my RPI :D

    I didn’t receive any instructions with my gamepad (mail order) but seems this is a pre-req step you have to do:

    – Insert receiver into USB port
    – remove 1 battery from gamepad
    – reinsert battery into gamepad
    – Connect utility then showed connected

    Now if I press mode button the light is either on solid, or off.

    Thanks anyway

    philmw60
    Participant

    Hi,

    First of all I’m a complete newb, so apologies if I’ve missed something obvious.

    I’ve got the standard retropie / emulationstation distro up and running on my RPI B model and recently purchased a Logitech F710 wireless gamepad. Problem is I can’t configure it!

    When I go into configure input (from main emulationstation menu) it states “1 gamepad detected” but when I press and hold any button on the gamepad, nothing happens on the Pi. At the same time the “mode” button blinks a few times then goes off. I’ve seen other posts suggesting this could be due to low battery but I’ve tried other brand new batteries and still no luck.

    It’s so frustrating cos EmulationStation detects that the Wireless receiver is plugged into the USB port! I even unplug it / reconnect it while the Pi is on and I get a brief message in yellow text stating the gamepad is recognised.

    The menus in Retroarch even identify it as a Logitech Gamepad F710! Could it be that the USB port on the RPI isn’t providing enough power to the receiver?

    Has anyone had any luck getting this controller to work? I haven’t installed any additional drivers and like I say this is the standard Retropie distro I downloaded just a few weeks ago.

    Thanks so much in advance.

    Phil

    #98603
    charco
    Participant

    Seems to be the recommended power supply.

    No lock ups since I installed the clean image on the new 64GB card. I decided not to use that scraper file at all. Kinda scared to use it now!

    Have my iBuffalo SNES controllers in the post so haven’t bothered setting up controls until they arrive, just adding compatible roms etc.

    Looking forward to finally playing some games with a pal, this has not been the easiest to configure I must say.

    snorp
    Participant

    Hi,

    last post is 1 month ago but after reading tons of Tutorials and Forumposts i cant fix my Problem. So I hope if I post here you can help me.

    These are my Steps from Yesterday:

    
    ############################################################################
    
    ####
    Raspbian & Retropie Installation Protocoll
    ############################################################################
    
    ####
    
    1.   DOWNLOAD RASPBIAN IMAGE AND MOUNT IT ON MICROSD
    
    2.   EXPAND FILESYSTEM
         type   'sudo raspi-config'
         select '1 Expand Filesystem'
    
    3.   GET SYSTEM UP TO DATE AND INSTALL RETROPIE
         type   'sudo apt-get update'
         type   'sudo apt-get upgrade'
         type   'sudo apt-get install -y git dialog'
         type   'cd'
         type   'git clone git://github.com/petrockblog/RetroPie-Setup.git'
         type   'cd RetroPie-Setup'
         type   'chmod +x retropie_setup.sh'
         type   'sudo ./retropie_setup.sh'
         select 'Binaries-based installation'
    
    4.   CONFIGURATE TIMEZONE AND KEYBOARD LAYOUT
         type   'sudo raspi-config'
         select '4 Internationalisation Options'
         select 'I2 Change Timezone' > 'Europe' > 'Berlin' > 'Finish'
         select '4 Internationalisation Options'
         select 'I3 Change Keyboard Layout' > ...
    
    5.   REMOVE SPLASHSCREENS(1) AND LOGOS(2)
    5.1  type   'cd RetroPie-Setup'
         type   'sudo ./retropie_setup.sh'
         select '3 Setup / Configuration (to be used post install)'
         select '328 Configure Splashscreen'
         select '2 Disable custom splashscreen on boot'
         type   'sudo nano /boot/config.txt'
         add    'disable_splash=1'
    5.2  type   'sudo nano /boot/cmdline.txt'
         add    'logo.nologo'
    
    6    ADD PS3 CONTROLLER VIA BLUETOOTH
         Shutdown Raspberry PI and connect PS3 Controller via USB Cable
         type   'lsusb'
         check controller is connected
         type   'cd /RetroPie-Setup/'
         type   'sudo ./retropie_setup.sh'
         select '3 Setup / Coniguration (to be used post install)'
         select '315 Install PS3 controller driver'
         select 'OK' > 'OK' > 'OK'
         type   'cd /opt/retropie/supplementary/ps3controller'
         type   'sudo ./sixpair'
         check Controller Address
         type   'sudo reboot'
         type   'cd /dev/input/'
         type   'ls'
         check js0 for first controller
         pull USB Cable and push PS Button, Controller connected (No.1)
         check Controller input
         type   'jstest js0'
         DO STEP 6 FOR EVERY CONTROLLER (max.16)
    
    7    PS3 CONTROLLER KONFIGURATION
         not done yet...
    ################################################################################
    

    I can connect 2 of 4 PS3 Controller no matter wich but max. 2. The first one gets LED1 and the second LED2. But the other 2 Controller blink.

    #98541

    In reply to: Cheap Controller

    nightjar
    Participant
    pulpblogger
    Participant

    I think it would be worthwhile to look into eliminating the USB syncing service and moving to a model where configs, roms, saves, logs etc are all stored on a USB storage device and the “system” is kept to the SD card.

    -Minimize writes to the SD card, thereby minimizing wear & potential for corruption during a power dip or failure
    -Allow for optimal RPi Performance with use of a SD card that has high random read/write times for the OS/System and a USB device with large capacity and high continuous read times for ROMs or content for KODI and other applications.
    -Allow for re-flashing/image based upgrading without having to go through all the reconfiguration/customization (some would obviously still be necessary depending on what is changing)
    -Eliminate the boot lag when syncing a lot of data

    #98519
    trobba
    Participant

    I am also having problems on my raspberry pi 2 with retro pie v3.0

    I have a usb snes controller which works perfectly in the main menu. I have programmed the controller for use in retroarch but when I play a game the d pad doesn’t work but every other button does.

    Please help

Viewing 35 results - 1,681 through 1,715 (of 3,655 total)