Homepage Forums Search Search Results for 'usb'

Viewing 35 results - 911 through 945 (of 3,655 total)
  • Author
    Search Results
  • #110344
    HoustoneD
    Participant

    Gizmo- My iPazzPort has its own usb dongle. I am not sure what wireless protocol it is using. i guess it is possibly bluetooth, but not connecting through my rocketfish BT dongle. Could this still be the issue?

    #110337
    mojoe
    Participant

    @pizzafaceassn

    I had to temporarily remove my wifi dongle to make room for a second controller during the end of the process.

    In order to keep the Internet connection, I used a hard wired Ethernet cable.

    So in addition to the Ethernet cable, I had:
    1. A Logitech wired controller
    2. Keyboard
    3. Bluetooth dongle
    4. PS3 controller wired with USB

    I then ran “lsusb” and verified that the PS3 pad was lower on the list of USB devices than the other controller. (I don’t know if that’s actually necessary. I’m just guessing. I’m a beginner at coding)

    Next I ran “install/pair PS3 controller” from the setup menu.

    The response was exactly the same. So no change there.

    Then I just rebooted into game mode. Once everything loaded, I disconnected the PS3 controller from its wired connection and pressed the “PS3” button.

    At that point, it paired as player 2.

    Then I removed the Logitech controller and rebooted again.

    Finally, the PS3 pad paired as player 1

    rdhanded2
    Participant

    I do not use any external usb for roms, all roms are on the sd card which still has plenty of memory.

    #110324
    mrco123
    Participant

    okay and thank you !

    OK mkdir test
    OK cd test
    OK git clone –depth=1 https://github.com/gizmo98/RetroPie-Setup.git
    OK cd RetroPie-Setup
    OK git pull
    OK git checkout ps3-gasia-hack
    OK sudo ./retropie_setup.sh

    after :
    setup / configuration
    ok
    install / pair ps3
    ok
    remove ps3 controller
    ok
    install / pair ps3

    a message say me to connect controller via usb
    ok
    restart ( ctrl C )
    emulationstation
    I disconnect cable and I press p3 button …

    but nothing !

    #110321
    Anonymous
    Inactive

    That’s what I did install/pair then it will do its thing and come up with a message saying to connect controller via usb etc etc hit ok, restart and load into ES then disconnect cable and press p3 button wait few seconds and it should be ok, if not go to menu and configure control and it should say 1 gameplay detected then press and hold p3 button ☺

    mikaou
    Participant

    Hi,

    I’ve managed to use 2 players with pifba but…the 2nd player axis are controlling the 1P axis too :(

    I’ve used jstest and I saw that all buttons are present but there is only 2 axis (0 and 1) and both joysticks uses that same axis.

    Is that a xin mo driver problem ? Anyone has the same thing ?

    Thanks ;)

    oleguer
    Participant

    If you connect one or more usb stick with roms ((unmounted)) the system automatically make a backup of the rute and roms you have in flash drive to access more quickly and this files have your disk space (if you unplug the usb stick you see the same roms tittles on emulators for this files reason)
    Solution:
    1-If you connect the raspberry with wifi use WINSCP to access to the files and dellete the files in the rom folder of internal raspberry memory ((remenber this files are only shortcut you can dellete then for free space on disk))
    2-If you dont have wifi install new image of retropie (and remenber if you connect usb stick unmounted the system make a shortcut backup

    Sorry for bad english but I try! ;)

    #110306
    pizzafaceassn
    Participant

    This is probably a really stupid question. What does your setup look like? I have my keyboard, wifi, Bluetooth, and PS3 usb connected how are you adding an additional control?

    #110305
    Anonymous
    Inactive

    Hi,

    I recently purchased a 2 player X-arcade stick (the one without the trackball).

    The x-arcade stick is the older model that has a PS2 connection rather than USB.

    My goal is to mount a RPi inside the x-arcade stick.

    My question is should I use a PS2->USB adapter and also mount that inside the x-arcade or should I buy a control block adapter and use that instead of using PS2 at all?

    Any advice would be much appreciated.

    Thanks in advance.

    marco-vania
    Participant

    hello,
    I’ve made my custom joystick with 12 buttons and a usb interface from ebay. It works fine but my problems start when the layout and controller configuration does no suit for all the emulators available in retropie.
    Is it possible to change the layout for each emulator?

    I’ve seen this on the net and would be nice to have a feature like this on retropie.

    thanks!!

    phaseiv
    Participant

    Here’s a quick rundown to get the neGcon controller working with Pcsx-Rearmed/RetroPie.

    You’ll need the latest version of the PSX emulator for neGcon support. Update the lr-pcsx-rearmed emulator with the RetroPie Setup menu. Select build from source and wait a couple of minutes till it’s ready.

    Connect the neGcon with a PSX-to-USB Controller Adapter to your Raspberry Pi. If all goes well you will be able to configure the neGcon buttons with emulationstation. Select ‘Configure Input’, assign some buttons (we need to edit the file later) and select OK. Now track down the config file that emulationstation has written for the USB adapter, it should be in /opt/retropie/configs/all/retroarch-joypads/. Edit the file and replace the button layout with this configuration:

    input_start_btn = "9"
    input_r_y_plus_axis = "-1"
    input_r_y_minus_axis = "+1"
    input_r_x_minus_axis = "-0"
    input_r_x_plus_axis = "+0"
    input_l2_axis = "-2"
    input_r_btn = "7"
    input_a_btn = "1"
    input_x_btn = "0"
    input_up_btn = "h0up"
    input_down_btn = "h0down"
    input_left_btn = "h0left"
    input_right_btn = "h0right"
    input_enable_hotkey_btn = 9
    input_menu_toggle_btn = "0"
    input_reset_btn = "h0left"
    input_exit_emulator_btn = "h0up"

    Now for the last step you need to tell the emulator that a neGcon is connected, since it’s not automatically detected. Start a Playstation game and open the RGUI menu, browse to Quick Menu -> Core Options -> Pad 1 Type and select negcon.

    Happy Racing!

    #110289
    mojoe
    Participant

    @redfarmer

    I’m having the exact same issue as you were. Could you list a step by step of how you got your controller working?

    I tried plugging in another wired controller. When I put in “lsusb” it listed the PS3 controller lower on the list than the wired controller. So I assume the PS3 controller is the “second device” like you suggested. But I’m still getting the same result.

    After running the PS3 controller install, the controller does work via a usb cable. But it won’t pair via bluetooth

    Any tips?

    BTW, I’m using a clean install of Retropie v3.2.1 from an SD image, and a genuine PS3 controller

    HoustoneD
    Participant

    Techy- if you are still having problems, I can offer advice.

    I was using berryboot originally so I could have both retropie and openelec.

    I scratched that plan. Do a standard load of retropie 3.2.1, then install Kodi from experimental setup in retropie_setup.sh. I think since berryboots filesystem is flat, we cannot write data to certain files. You could try adding user pi to admin or use chmod777 to see if it is a possible permissions issue.

    I think I’m done with berryboot though. It’s cool, but I think just running kodi out of ES is better

    Sent from my XT1254 using Tapatalk

    #110283
    hypersonic
    Participant

    Damn

    It doesn’t like the +tive and -tive axis lines and when i set the axes to mouse axes, it shows some promising lines in the console before loading kodi but doesn’t give me a mouse pointer.

    Also none of the controller buttons work, i’m wondering if i need to sort out a usb keyboard to go in and turn on the mouse pointer in kodi settings to make this work.

    #110275
    redfarmer
    Participant

    Problem is solved!

    I first connected a cabled XBox360 controller that made my PS3 controller the “second” device. So when the RetroPie setup wanted me to connect it over USB and then unplug to pair i did not get the error in the screenshot above.

    By curiosity i removed the XBox360 controller during the pairing process and the error appeared.

    I think the RetroPie setup gets “confused” when the main controller is removed, even in the pairing process. This is why i couldn’t pair when the PS3-controller was the only active controller connected over USB.

    #110256

    In reply to: SNES games not loading

    linkz
    Participant

    Yeah the 777 was lazyness. Normally I would freak if people just gave full access to files on my linux server at work, but since this is a private “machine” I wasn’t worried about it. I don’t think they were owned by root since root password is disabled since 3.0. I got the roms onto the pi via usb but for some reason they wouldn’t auto sync so I just
    cp /media/usb/retropie/roms/snes/* ~/RetroPie/roms/snes

    petrockblog
    Keymaster

    I’ll consider adding it as an option, but for now if you must use NTFS, you can enable it by doing the following

    
    sudo apt-get install ntfs-3g
    sudo sed -i "s/hfsplus/hfsplus ntfs fuseblk/g" /etc/usbmount/usbmount.conf
    
    #110235
    pausuri
    Participant

    [quote=110225]OK, so far things ARE WORKING PERFECTLY.

    First of all, I want to just say that I took the small step to get PuTTY so I could control my Pi from my Windows PC and it made a world of difference being able to copy and paste and see my screen etc. Everyone should do this.

    I can’t explain how the “Invalid exchange 52” problem was solved. I removed and re-added the devices many times, usually the error would persist. But now, after removing all the paired BT devices and just re-adding the Start-R booted SNES30, so far RetroPie is connecting everytime. *knock on wood*

    What ended up working for me? I have:
    two 8Bitdo SNES30 gamepads (firmware 2.63)
    RetroPie v2.3.1 on RPi 2.
    BT usb adapter (Kinivo)
    Wireless usb keyboard

    Boot SNES30 with Start-R (Joystick mode, I guess). It won’t appear to blink differently.
    Confirm it booted in the right mode with hcitool scan
    For me, instead of showing 01:06:F6:0E:xx:xx 8Bitdo SNES30 GamePad
    it would show FE:F9:09:F1:xx:xx 8Bitdo SNES30 GamePad Joystick

    Set up your first SNES30 as per Floob’s wiki instructions

    sudo bluez-simple-agent -c DisplayYesNo 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

    Repeat the above for the second SNES30. Again, as per the wiki instructions, add sudo bluez-test-input connect XX:XX:XX:XX:XX:XX twice in the startup file, each line for each SNES30 MAC address.

    Now, as per instructions on the first page of this post we will modify the keyboard direction input in retroarch.cfg to nul.
    type sudo nano /opt/retropie/configs/all/retroarch.cfg
    under the Keyboard input section change
    input_player1_left = left
    input_player1_right = right
    input_player1_up = up
    input_player1_down = down

    into ..

    input_player1_left = nul
    input_player1_right = nul
    input_player1_up = nul
    input_player1_down = nul

    My SNES30’s have been previously configured with Emulation Station, so I did not perform step 4 on the wiki guide.

    On to step 5, I ensured there was no retroarch .cfg file for my gamepads. Then I ran, from PuTTY, the RetroArch controller configuration script.
    sudo /home/pi/RetroPie-Setup/retropie_setup.sh
    Running this from PuTTY allowed me to avoid the prior bug I had where my TV screen would turn black near the beginning of the mapping. I believe I only had to do this with the one controller, since they are identical and write the same 8BitdoSNES30GamePadJoystick.cfg file anyway.

    I think that’s basically it. To use the SNES30’s, I just turn them on with Start-R just before or after turning on my Pi. The blue flashing turns to solid blue around the time Emulation Station splash screen comes on. I have tested in 2-player simultaneous games in NES and SNES that both controllers work great for P1 and P2 with no d-pad crossover as before. Hopefully some of this info can be helpful to others. In the meantime I hope that “Invalid exchange 52” bluetooth connection issue stays away.

    [/quote]

    Thanks for the info, are you experiencing any troubles when you try to reconnect the Pad??

    turk182
    Participant

    My USB is NTFS … this is the reason ? Retropie doesn’t recognize the NTFS ?

    HoustoneD
    Participant

    I am slowly, but surely getting everything working in my RetroPie.

    Right now, my current hurdle to get over is getting my master system up and running.

    Genesis, SNES, NES, N64, and Atari all seem to be working using my PS3 Dual Shock Controller, over USB and also with bluetooth.

    Even playing some SMS ROMS through the Megadrive Emulator seems to work fine.

    I am running RetroPie 3.2.1 (fully updated, updated emulator binaries, setup script, etc.) on a RPi2.

    Hopefully these snippets will help provide some insight as to what my issue is. i am sure it is something easy. Please help!

    #### Input

    # Input driver. Depending on video driver, it might force a different input driver.
    # input_driver = sdl

    # Input device driver. (Valid: linuxraw, sdl, dinput)
    # input_joypad_driver =

    # Path to input remapping file.
    # input_remapping_path =

    # If enabled, overrides the input binds with the remapped binds set for the current core.
    # input_remap_binds_enable = true

    # Maximum amount of users supported by RetroArch.
    # input_max_users = 16

    # 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

    # Show the input descriptors set by the core instead of the
    # default ones.
    # input_descriptor_label_show = true

    # Hide input descriptors that were not set by the core.
    # input_descriptor_hide_unbound = false

    # Directory for joypad autoconfigs.
    # 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/configs/all/retroarch-joypads/

    # Sets which libretro device is used for a user.
    # 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 user 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

    # Input device 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 =

    # Menu buttons.
    # menu_ok_btn =
    # menu_cancel_btn =
    # menu_search_btn =
    # menu_info_btn =
    # menu_default_btn =
    # menu_scroll_down_btn =
    # menu_scroll_up_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 user 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 users.
    # 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_btn =

    # 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

    # RetroPad button combination to toggle menu
    # 0 = none, 1 = L + R + Y + D-Pad Down, 2 = L3 + R3
    # input_menu_toggle_gamepad_combo = 0

    # 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

    And my two PS3 configs-

    input_device = “PLAYSTATION(R)3 Controller”
    input_driver = “udev”
    input_b_btn = “14”
    input_y_btn = “12”
    input_select_btn = “0”
    input_start_btn = “3”
    input_up_btn = “4”
    input_down_btn = “6”
    input_left_btn = “7”
    input_right_btn = “5”
    input_a_btn = “13”
    input_x_btn = “15”
    input_l_btn = “10”
    input_r_btn = “11”
    input_l2_btn = “8”
    input_r2_btn = “9”
    input_l3_btn = “1”
    input_r3_btn = “2”
    input_l_x_plus_axis = “+0”
    input_l_x_minus_axis = “-0”
    input_l_y_plus_axis = “+1”
    input_l_y_minus_axis = “-1”
    input_r_x_plus_axis = “+2”
    input_r_x_minus_axis = “-2”
    input_r_y_plus_axis = “+3”
    input_r_y_minus_axis = “-3”
    input_enable_hotkey_btn = “0”
    input_exit_emulator_btn = “3”
    input_menu_toggle_btn = “15”
    input_load_state_btn = “10”
    input_save_state_btn = “11”
    input_reset_btn = “14”
    input_state_slot_increase_btn = “5”
    input_state_slot_decrease_btn = “7”

    input_device = “Sony PLAYSTATION(R)3 Controller”
    input_driver = “udev”
    input_r_y_plus_axis = “+3”
    input_l3_btn = “1”
    input_r_x_minus_axis = “-2”
    input_r_btn = “9”
    input_save_state_btn = “9”
    input_l2_btn = “10”
    input_start_btn = “3”
    input_exit_emulator_btn = “3”
    input_l_y_minus_axis = “-1”
    input_l_btn = “8”
    input_load_state_btn = “8”
    input_up_btn = “4”
    input_r_y_minus_axis = “-3”
    input_a_btn = “14”
    input_b_btn = “13”
    input_reset_btn = “13”
    input_down_btn = “6”
    input_r2_btn = “11”
    input_l_x_plus_axis = “+0”
    input_l_y_plus_axis = “+1”
    input_r3_btn = “2”
    input_right_btn = “5”
    input_state_slot_increase_btn = “5”
    input_x_btn = “15”
    input_menu_toggle_btn = “15”
    input_select_btn = “0”
    input_enable_hotkey_btn = “0”
    input_l_x_minus_axis = “-0”
    input_y_btn = “12”
    input_left_btn = “7”
    input_state_slot_decrease_btn = “7”
    input_r_x_plus_axis = “+2”

    Thanks in advance for the help.

    #110225
    tossy
    Participant

    OK, so far things ARE WORKING PERFECTLY.

    First of all, I want to just say that I took the small step to get PuTTY so I could control my Pi from my Windows PC and it made a world of difference being able to copy and paste and see my screen etc. Everyone should do this.

    I can’t explain how the “Invalid exchange 52” problem was solved. I removed and re-added the devices many times, usually the error would persist. But now, after removing all the paired BT devices and just re-adding the Start-R booted SNES30, so far RetroPie is connecting everytime. *knock on wood*

    What ended up working for me? I have:
    two 8Bitdo SNES30 gamepads (firmware 2.63)
    RetroPie v2.3.1 on RPi 2.
    BT usb adapter (Kinivo)
    Wireless usb keyboard

    Boot SNES30 with Start-R (Joystick mode, I guess). It won’t appear to blink differently.
    Confirm it booted in the right mode with hcitool scan
    For me, instead of showing 01:06:F6:0E:xx:xx 8Bitdo SNES30 GamePad
    it would show FE:F9:09:F1:xx:xx 8Bitdo SNES30 GamePad Joystick

    Set up your first SNES30 as per Floob’s wiki instructions

    sudo bluez-simple-agent -c DisplayYesNo 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

    Repeat the above for the second SNES30. Again, as per the wiki instructions, add sudo bluez-test-input connect XX:XX:XX:XX:XX:XX twice in the startup file, each line for each SNES30 MAC address.

    Now, as per instructions on the first page of this post we will modify the keyboard direction input in retroarch.cfg to nul.
    type sudo nano /opt/retropie/configs/all/retroarch.cfg
    under the Keyboard input section change
    input_player1_left = left
    input_player1_right = right
    input_player1_up = up
    input_player1_down = down

    into ..

    input_player1_left = nul
    input_player1_right = nul
    input_player1_up = nul
    input_player1_down = nul

    My SNES30’s have been previously configured with Emulation Station, so I did not perform step 4 on the wiki guide.

    On to step 5, I ensured there was no retroarch .cfg file for my gamepads. Then I ran, from PuTTY, the RetroArch controller configuration script.
    sudo /home/pi/RetroPie-Setup/retropie_setup.sh
    Running this from PuTTY allowed me to avoid the prior bug I had where my TV screen would turn black near the beginning of the mapping. I believe I only had to do this with the one controller, since they are identical and write the same 8BitdoSNES30GamePadJoystick.cfg file anyway.

    I think that’s basically it. To use the SNES30’s, I just turn them on with Start-R just before or after turning on my Pi. The blue flashing turns to solid blue around the time Emulation Station splash screen comes on. I have tested in 2-player simultaneous games in NES and SNES that both controllers work great for P1 and P2 with no d-pad crossover as before. Hopefully some of this info can be helpful to others. In the meantime I hope that “Invalid exchange 52” bluetooth connection issue stays away.

    mtume
    Participant

    I’ve got a pair of bt controllers of eBay. They came with one USB receiver.
    I only get one to work. They both work but not at the same time.

    Is there a solution ?

    lamaman1971
    Participant

    So, after my trauma of Mame4All and my USB Soundbar I binned that approach and used a bog standard 3.5mm audio out instead (my cabinet is driving an old 4:3 monitor, no HDMI). Anyway, generally speaking the sound is OK but once in while it stops working – in the whole of Retropie, not just a single emulator. Reboot and its fine – which suggests its not the hardware.

    Anyone seen this before?

    Cheers

    Mark

    ExSilver
    Participant

    Hi there, I’ve built my lad an arcade machine for Christmas. Its a Pi 2 Model B with MAME and unfortunately a Xin-Mo USB Interface. I’ve managed to do a few of the tutorials to make the USB device recognise as 2 joypads and get the controls some what sorted out.

    Basically I’ve used the start button to bring up the menu where you hold a button to configure your controls and it works to some extent.
    When outside of a game P1 joystick Left/Right & Up/Down are inverted. But P2 is fine.
    When inside a game P1 is inverted like above but P2 is fine.

    Could someone please explain the reason? Forgive me I’m new to Pi’s and Linux and so don’t know very much terminology or commands etc. So if you could, could you dumb any answers down for me? lol

    I’ve heard of various configuration files that can be edited but I don’t know the difference. The EmulationStation/es_inputs.cfg, the retroarch/config.cfg and I’ve also had a message pop up saying opt/retropie/configs/all/retroarch-joypads/Xin-MoXin-MoDualArcade.cfg…… which ones am I supposed to be editing for “Out Game” and “In Game”?. Once again sorry for my lack of knowledge lol. It’s very painful writing this haha

    Any help would be amazing as I’m desperate to get it working soon so I can reassemble it ready for xmas.

    Thank You In Advance, This forum has already been a godsend!

    P.S Please See attached image for my setup. I have now got LED Strips in the top Part, with a glass panel with my sons name written on it in SEGA text. It’s certainly getting there I Just need this final niggle sorted lol

    linkz
    Participant

    Hi all first let me fill this out:

    Pi Model: B I think, I have the first one made
    RetroPie Version Used: 3.0.0, just downloaded yesterday
    Built From: SD Image
    USB Devices connected: Keyboard or USB SNES Controller
    Controller used: 2 USB SNES Controller
    Error messages received: None
    Guide used: A basic setup guide
    File:
    Attachment of config files:
    How to replicate the problem:

    Basically I have all my NES roms working which is awesome! But all of my SNES roms don’t, I start the rom, I see the “press any key to load options” then the screen fades black and I’m back at my select a SNES rom screen. No errors or anything and I don’t see anything in that .log file. Ideas?

    Anonymous
    Inactive

    Zipped roms are tricky to get working, mame for example you have to also edit the

    /opt/retropie/emulators/mame4all/mame.cfg

    To also point the rompath to your usb, not very difficult, just an extra step, not sure about snes, I run those roms from my sd card,and just a quick note for you guys, running roms from your usb does not let you use the savestate function anymore since it’s trying to save to usb and the pi doesn’t have permission to save to usb, this is also easily fixed

    Good luck

    #110114
    rdhanded2
    Participant

    http://www.retrousb.com/product_info.php?cPath=21&products_id=44&osCsid=5db5274fe2f80445647dfca4b075c5cc

    the retrousb controller so I can plug in original snes and nes controllers. Shows up as

    RetroUSP.com Retropad

    petrockblog
    Keymaster

    I know it works, so it must be an issue on your set up. Double check your usb stick has a single partition formatted as fat32 or ext4 with a folder in the root called “retropie” and plug it in to the pi. then from a terminal do “cat /var/log/syslog” – when it’s working it should have some lines like

    
    Nov 17 11:55:25 retropie usbmount[2282]: executing command: run-parts /etc/usbmount/mount.d
    Nov 17 11:55:26 retropie usbmount-01_retropie_copyroms-[2327]: Attempting to create directory structure for ROMS in '/media/usb0/retropie/roms' ...
    Nov 17 11:55:29 retropie usbmount-01_retropie_copyroms-[2327]: Syncing roms ...
    Nov 17 11:55:29 retropie usbmount-01_retropie_copyroms-[2327]: Syncing configs ..
    
    #110104
    dankcushions
    Participant

    @shoothere
    i’d previously manually set up the symlinks for each rom folder, but i’ve just done a re-build and attempted to do it with one link of the whole folder (i copied the contents of the stock roms directory to my stick beforehand), and it worked fine. saves time, cheers!

    my USB stick is read/write (thanks to that fstab line) and i’m running 3.2.1 (although it worked fine before)

    #110097
    oleguer
    Participant

    You can! Try using WINSCP to acess to raspberry pi files if you can use wifi….or use the terminal (connect keyboard to usb port and press F4 to open terminal) and edit them with sudo nano /etc/fstab add the permisions to fstab and lucky!

    #110088
    tossy
    Participant

    (Edit: I am using a newly, successfully installed RetroPie 3.2.1 on Raspberry Pie 2. The SNES30’s have the latest firmware)

    How does the process differ in the wiki article (https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-a-Bluetooth-controller) if I have two SNES30 controllers?

    I followed all the instructions, and I set up both controllers for bluetooth with command lines and edited the startup file so both will automatically connect with each boot.

    On Step 4, my controller D-pads work fine in the GUI, but on the Emulation Station controller configuration the d-pads do not register as assigned keypresses, but just move the selection around. (edit: I have noticed when it’s looking for a controller button to be pressed, and if I press a SNES30 dpad, it will display “keyboard” as the to-be configured device.)

    On Step 5, I was able to configure my first controller using the described method. For the next controller, I did not delete the file again, and when I went into the “Configure input devices for RetroArch” tool, this time the screen goes completely black. Mashing buttons for a while will bring the screen back but with a bunch of timeouts and some assigned buttons to the config tool.

    In practice, I could play a NES game where P1 controller would work fine, but the P2 controller would also work fine except its dpad would control both player 1 and player 2.

    I’m somewhat worried that when I did the “cd /opt/retropie/configs/all/retroarch-joypads/
    ls -lah”
    Aside from my XBOX360 USB I had tried earlier, it only showed the one config file for my gamepads (there was a bak copy as well). I have noticed in Emulation Station my gamepads have identical names. Should there be a config file for each gamepad?

    This is proving to be far more complicated than I ever anticipated. If anyone can help me figure this out I would greatly appreciate it.

    #110078
    techytecherson
    Participant

    Hi Floob, I think thats just about the only thing i didn’t try, but i noticed i have an even bigger issue now, I can’t connect to the internet, i can connect to the home network and access the pie files ad roms and stuff but can’t connect to the internet at all, so i can’t apt-get update or anything i made another post about it, its driving me so crazy been about a half a month trying to get this working!

    and like i was saying in the other post i made on cana usb bluetooth wifi post I tried everything i’ve seen on the net, youtube, forums everything and can’t get it to connect out side of my network, its a little thing but driving me crazy!

    techytecherson
    Participant

    YES!! I’ve been trying to get mine going for half a month, I know a little about linux, and I’ve tried EVERYTHING! every thing i can find on youtube and forums, but nothing seams to work, i can see it, i can write files to the pi over the network, but can’t get it to connect onto the internet only my home network, and therefor i can’t get apt-get update to work or anything, I really need to get on the net so i can get this thing working, I’ve also tried both wired and the CANA usb wifi, i know the adaptor works i can see it lsusb and like i said i can write files to the pie but can’t get it to go out to the internet I hope that someone can help me this is driving me crazy!

    #110073
    ngseven
    Participant

    Update: I managed to get retroarch and fba-libretro to run on my PC, using the same monitor and USB keyboard as on my PI. Using hard GPU sync on, input lag went down to 2 frames! With hard GPU sync off, I got the same input lag of 4 frames or more as on my PI.

    So, at the moment I think that the problem is that hard GPU sync does not work in retroarch on retropie, as I already conjectured above.

    Hence, it would be interesting how I could get hard GPU sync to work in retroarch on retropie, e.g., by compiling retroarch with certain options. However, I remember that certain dependencies would have to be included, and I am not a Linux expert, so any suggestions on how to successfully activate hard GPU sync would be very welcome.

    Of course, the problem might be then that the processing power of the PI 2 does not suffice for Neo Geo games with hard GPU sync switched on…

    jerseywavesurfer
    Participant

    Hi smoothere hope you got it up and running now as I feel your pain. If not this is what I did.

    Formatted both my sd card and usb stick
    Download a fresh 3.2.1 retropie
    Installed it and followed you tube vids techtipsta, floob and others f4 typing part where you over clock, explanded the sd card. Rebooted but still no nes or snes emu was dishearten. After I changed the usb stick to other ports (now mine in the top right one) and re explanded my sd card, in the retropie options (no typing.) another reboot and eureka happyness returned to me as they appeared and worked. I did no editing and haven’t change any of the emu all on default. I hope this helps you out and good luck.

Viewing 35 results - 911 through 945 (of 3,655 total)