-
Search Results
-
Hello
I have Pi Zero with RetroPie 3.5 on 16gb sd card with keyboard, gamepad nad wifi dongle connected through powered usb hub.
I’ve spent almost whole weekend trying to get it working witout success…
After installation of RetroPie emulation station is launched and i have to configure gamepad. My gamepad is Esperanza PS3-like controller and it is recognized as “Sun Light PS2 PS3 USB Controller”. During key mapping i have none problems with key assignment.
Afterwards i press A and go to menu. Now if i select any option like Super Mario or configure wifi and go back to menu gamepad doesn’t work anymore. Keyboard doesn’t work also (arrows or anything besides F4). Then i press F4 and go back to terminal, start emulation station again and i have to configure controller all over again.
There are many guides with controller configuration but almost everyone refers to 2.X Retropie…
Hello everyone, I try to grab the video output of my raspberry pi and send it via ffmpeg to an rtmp server.
Build the most updated version of ffmpeg from source, I have another good PC, which should handle the main processing, so I really need the pi, only to send the output to the stream. I know it may be easier other way around, but I would really like to do this this way.So what I have:
ffmpeg -devices:
Devices:
D. = Demuxing supported
.E = Muxing supported
—
DE alsa ALSA audio output
D dv1394 DV1394 A/V grab
DE fbdev Linux framebuffer
D jack JACK Audio Connection Kit
D lavfi Libavfilter virtual input device
DE oss OSS (Open Sound System) playback
E sdl SDL output device
E v4l2 Video4Linux2 output device
D video4linux2,v4l2 Video4Linux2 device grab
D x11grab X11 screen capture, using XCBhoped i could do something like:
ffmpeg -f fbdev -i /dev/fb0 -f flv rtmp://192.168.0.103/live/test
but i only get ‘Output file #0 does not contain any stream’. So I need to enable them or they are not fully present?emustation / retroarch(emulators) do not run through x11, if im not mistaken, so which video source should i grab? And what are the input (files) for the streams? I read something about v4l2 and /dev/video0 , but video0 is not present, or better grab it from the dv1394? Doing more research, but maybe someone knows.
Hope I’m understandable :D
happy valentine’sPi Model: 2 +
RetroPie Version Used: latest version 7 days ago
Built From: SD
USB Devices connected: keyboard, WLAN, 2 controllers
Controller used: 1 xbox360 (udev) and an old ps one fake usb controller (greenix something)Topic: Megadrive project
Hello, just thought I’d share my just completed Megadrive 2 conversion.
Here is the console freshly disassembled.
[img]http://i.imgur.com/FAaxDnS.jpg[/img]Sadly a Megadrive 2 was most definitely harmed during this. I wanted to retain the power buttons, power LED and the cartridge slot but still needed space to fit the raspberry pi so the board had to be cut up.
[img]http://i.imgur.com/T3VAkI5.jpg[/img]Here are the board sections back in the case. As it turned out this still wasn’t enough to fit everything inside comfortably so more hacking was required.
[img]http://i.imgur.com/xlfjrK6.jpg[/img]After lots more hacking and use of a rotary tool to remove unwanted plastic bits I was finally able to fit everything inside the case comfortably. Below you can see all the components. to the right are what remains of the Megadrive board – the cartridge area had to be cut in half to allow everything to fit how I wanted.
The power socket has been replaced with a new socket and this will be wired to that cut off usb connector to power the Raspberry Pi.
The power button and power led have wires attached so that they can be connected to the ‘Powerblock’ so that they will both be functional (great piece of kit by the way).
I couldn’t decide on how to do the HDMI connector originally but settled on the solution shown which works really well – there is a hole already at the back of the console which as it turns out is a perfect diameter for the HDMI extender cable.
The USB extension leads pictured will be shortened and then used in place of the original controller ports.
The ethernet socket will be connected to the raspberry pi and will replace the original AV socket.
[img]http://i.imgur.com/WkZXOJW.jpg[/img]Everything secured in place. I drilled holes in the original circuit board and used cable ties to hold the ethernet socket and USB extension leads in place. It’s actually really sturdy surprisingly. Holes were drilled below the Raspberry Pi so that it could be secured using nuts and bolts.
[img]http://i.imgur.com/EYsw0Yv.jpg[/img]View of USB ports.
[img]http://i.imgur.com/UpcwDOb.jpg[/img]Rear panel showing HDMI extender, ethernet socket and power socket.
[img]http://i.imgur.com/Wlt364W.jpg[/img]Here’s the reason I wanted to keep at least some of the cartridge slot. Here is a bog standard Menacer Cartridge bought on ebay.
[img]http://i.imgur.com/BWesNB6.jpg[/img]And after lots of label peeling and some time spent in photoshop here is the all new cartridge.
[img]http://i.imgur.com/DYtT55t.jpg[/img]And here’s the finished product :)
Topic: Teensy with emulationstation
Hi all…
Im new here and this is my first post, I’m having trouble getting my teensy 3.1 to work in emulationstation.
I have a keyboard setup fine so I can navigate through the menus and when I select “configure input” from the menu I get the teensy serial/keyboard/mouse/joystick appear. If I hold the button it enters the menu but thats it, from that point on their is no more input regestered and I cant set the keys.
I have also tryed “jstest” and get no responce to button pressing with that, but it does see it as a usb device.
Im using a teensy 3.1 set to 72mhz and as a “serial+keyboard+mouse+joystick”
Any help would be greatly appreciated!
Hey Everyone,
I’m using a wireless Xbox controller with a zettaguard wireless receiver like I know many are on this site. However, I’m having an issue where the controllers disconnect when they lose line of site with the receiver (like if your legs are in the way). I’m only about 8 feet away. At first I thought it was a power issue. I’ve added a 5v 4amp power supply and add “max_usb_current=1” to /boot/config.txt. But I’m still having the same issue.
Is this typical of these receivers or am I missing something?
I have a one-button usb-joystick connected to the Raspberry. It is setup with the button mapped to A. It works in the GUI (with some navigation going through keyboard) but when I load UAE, the button does not work. The joystick works fine for up, down, left, right, but games does not respond to the button. Does anyone know how to remap the button to another button than A or in some other tweak make it possible to play with a one button joystick?
Regards
AndreasGood afternoon,
After much playing over the past month on 3.3.1 I’ve realised there is an update and had to revise the hacks list I made myself… so I thought I’d share it and ask a hopefully simple question!
Pi Model: 1 Model B
RetroPie Version Used: 3.5
Built From: SD Image
USB Devices connected: N/A
Controller used: Keyboard/360 Controller (official)The above is used to configure the SD card before placing into my Pi Zero, the lack of a LAN port is killing me. There are however no issues swapping between the two!
My Initial Setup
1) Write the retropie-3.5-rpi1.img to the SD card using Win32 Disk Imager
2) Go into RetroPie/RetroPie-Setup and ‘Update Retro-Pie Setup’, then Reboot
3) Place into the Pi and boot for the first time
4) Setup keyboard as an input device, don’t plug in the 360 controller yet
5) Shutdown the Pi and place the SD card back in my PC, enable ‘hdmi_drive=2’ in config.txt (or I don’t get sound on my TV)
6) Boot back up and shell out (F4), disable the existing Xpad drivers –
sudo nano /etc/modprobe.d/fbdev-blacklist.conf
Add ‘blacklist xpad’ to the bottom of the blacklist, save and exit (F3 then ctrl+x)
7) Either ‘exit’ or ‘sudo reboot’
8) Go into RetroPie-Setup and install the Xbox 360 drivers, reboot
9) Plug in the 360 controller and ‘Configure Input’ from the main menu, it should now use the right driver!Random Hacks… these are done once I am happy with the system, to keep sticky fingers out
Remove ‘Press a key to configure emulator’ prompt
sudo nano /opt/retropie/supplementary/runcommand/runcommand.sh
Search for IFS= and replace the number 2 after -t with a 0
(this removes the option for someone to mess with your emulator settings although with the new runcomamnd.sh options you may want to leave it in and just disable joystick input)Hiding ‘RetroPie’ from the list of emulators in EmulationStation
sudo nano /etc/emulationstation/es_systems.cfg
Add <!– to the start of ‘RetroPie’
and –> to the endAdding ‘analogue’ support to the emulators (there are much better hacks!)
Using ftp to access \\retropie
Edit configs/all/retroarch.cfg to include the following –
input_player1_analog_dpad_mode = “1”
input_player2_analog_dpad_mode = “1”
input_player3_analog_dpad_mode = “1”
input_player4_analog_dpad_mode = “1”
input_player5_analog_dpad_mode = “1”
input_player6_analog_dpad_mode = “1”
input_player7_analog_dpad_mode = “1”
input_player8_analog_dpad_mode = “1”To prevent it interfering with PSX and N64 analogue functions edit their separate retroarch.cfgs and add –
input_player1_analog_dpad_mode = “0”
input_player2_analog_dpad_mode = “0”
input_player3_analog_dpad_mode = “0”
input_player4_analog_dpad_mode = “0”
input_player5_analog_dpad_mode = “0”
input_player6_analog_dpad_mode = “0”
input_player7_analog_dpad_mode = “0”
input_player8_analog_dpad_mode = “0”Possible fix for audio lag stutter –
Using ftp to access \\retropie
Edit configs/all/retroarch.cfg to include the following
audio_out_rate = 44100 (this will already be in there as 48000, uncomment and change)
audio_driver = sdl (this will already be in there but blank, uncomment and change)My question
Now that I’ve bored everyone.. but hopefully put some stuff in one place! Here goes.
On the Main Menu is the option for ‘Configure Input’, I would like to remove it so that I can leave the emulator in the hands of children and they won’t mess the joysticks up to the point I can’t remap them. I tried setting a read-only es_input.cfg but it didn’t work.
If I can remove the configure input menu option there isn’t anywhere they can go (if you don’t count the RetroArch shortcut in game). The rest of the menu can stay otherwise I can’t reach the Shutdown/Restart options. :)
Thanks for any advice.
Lee
I hope this is the right place to post this info:
This HDE receiver works perfectly with Retropie (tested on 3.4 and 3.5)
Nothing else to do than plugging and enabling the xboxdrv from retropie menu.Holding the wireless button on the controller and on the receiver will get them to pair.
No Lag, works in all retroarch emulator.Note 1: To enable analog input for psx change the following line in
/opt/retropie/configs/all/retroarch-core-options.cfgpcsx_rearmed_pad1type = "standard" pcsx_rearmed_pad2type = "standard"
to
pcsx_rearmed_pad1type = "analog" pcsx_rearmed_pad2type = "analog"
Note 2: Best method to map controller for each emulator:
1 – create input configuration from emulation station
2 – copy the following folder and its contentto the rom folder:
copy:
/opt/retropie/configs/all/retroarch-joypads/
to (example)
/opt/retropie/configs/psx/retroarch-joypads/
3 – include the following line in the retroarch.cfg file of the emulator:
example:
in /opt/retropie/configs/psx/retroarch.cfg
add this line before the #include… statement:
joypad_autoconfig_dir = /opt/retropie/configs/psx/retroarch-joypads/
4 – make sure the emulator rom folder is correctly called in the line you just entered.
5 – Modify the inputs for the controller in the controller config file:
/opt/retropie/configs/psx/retroarch-joypads/XboxGamepad(userspacedriver).cfg
here are my settings for a few console:PSX:
input_device = "Xbox Gamepad (userspace driver)" input_driver = "udev" input_save_state_btn = "7" input_start_btn = "9" input_exit_emulator_btn = "9" input_load_state_btn = "6" input_up_btn = "h0up" input_reset_btn = "1" input_down_btn = "h0down" input_right_btn = "h0right" input_state_slot_increase_btn = "h0right" input_menu_toggle_btn = "2" input_select_btn = "8" input_enable_hotkey_btn = "8" input_left_btn = "h0left" input_state_slot_decrease_btn = "h0left" #input_up_axis = "-1" #input_down_axis = "+1" #input_left_axis = "-0" #input_right_axis = "+0" input_l2_btn = "6" input_r2_btn = "7" input_l_btn = "4" input_r_btn = "5" input_a_btn = "3" input_b_btn = "0" input_x_btn = "1" input_y_btn = "2" input_r_y_plus_axis = "+3" input_r_x_minus_axis = "-2" input_l_y_minus_axis = "-1" input_r_y_minus_axis = "-3" input_l_x_plus_axis = "+0" input_l_y_plus_axis = "+1" input_l_x_minus_axis = "-0" input_r_x_plus_axis = "+2"
NES:
input_device = "Xbox Gamepad (userspace driver)" input_driver = "udev" input_save_state_btn = "7" input_l2_btn = "4" input_start_btn = "9" input_exit_emulator_btn = "9" input_load_state_btn = "6" input_up_btn = "h0up" input_a_btn = "0" input_b_btn = "2" input_reset_btn = "1" input_down_btn = "h0down" input_right_btn = "h0right" input_state_slot_increase_btn = "h0right" input_menu_toggle_btn = "2" input_select_btn = "8" input_enable_hotkey_btn = "8" input_left_btn = "h0left" input_state_slot_decrease_btn = "h0left" input_r_x_plus_axis = "+2" input_up_axis = "-1" input_down_axis = "+1" input_left_axis = "-0" input_right_axis = "+0" input_y_btn = "3" input_x_btn = "1"
SNES:
input_device = "Xbox Gamepad (userspace driver)" input_driver = "udev" input_save_state_btn = "7" input_start_btn = "9" input_exit_emulator_btn = "9" input_load_state_btn = "6" input_up_btn = "h0up" input_a_btn = "1" input_b_btn = "0" input_reset_btn = "1" input_down_btn = "h0down" input_right_btn = "h0right" input_state_slot_increase_btn = "h0right" input_menu_toggle_btn = "2" input_select_btn = "8" input_enable_hotkey_btn = "8" input_left_btn = "h0left" input_state_slot_decrease_btn = "h0left" input_r_x_plus_axis = "+2" input_up_axis = "-1" input_down_axis = "+1" input_left_axis = "-0" input_right_axis = "+0" input_y_btn = "3" input_x_btn = "2" input_l_btn = "6" input_r_btn = "7"
PCENGINE:
input_device = "Xbox Gamepad (userspace driver)" input_driver = "udev" input_save_state_btn = "7" #input_l2_btn = "4" input_start_btn = "9" input_exit_emulator_btn = "9" input_load_state_btn = "6" input_up_btn = "h0up" input_a_btn = "0" input_b_btn = "2" input_reset_btn = "1" input_down_btn = "h0down" input_right_btn = "h0right" input_state_slot_increase_btn = "h0right" input_menu_toggle_btn = "2" input_select_btn = "8" input_enable_hotkey_btn = "8" input_left_btn = "h0left" input_state_slot_decrease_btn = "h0left" input_r_x_plus_axis = "+2" input_up_axis = "-1" input_down_axis = "+1" input_left_axis = "-0" input_right_axis = "+0" input_y_btn = "3" input_x_btn = "1"
Advantage of using this controller config method is that you could load tons of different controller configurations and the system will attribute player 1 to the first type of controller connected and match the corresponding custom config you made in the folder /opt/retropie/configs/(ìnsert emulator name)/retroarch-joypads/
.Hope this helps :)
MirageHi all,
There seems to be a plethora of retro usb joypads out there, but playing Sensible Soccer etc on joypad just doesn’t feel like the real thing to me. I miss the feel of my old two-button Amiga joystick.
Did anyone manage to find something suitable? Amazon have a Competition Pro style joystick listed but it is unavailable, and nowhere else seems to have one in stock. Maybe it was a limited run or something?
I don’t need anything fancy like the ones designed for flight sims or with tons of buttons; just a stick and a couple of buttons. Is it really too much to ask :/
Topic: Questions about 3.5
Team and fellow RetroPie users in the know,
I have two questions.1. Screen blanking from time to time, it is noted that the 3.5 image fixes this. I was on 3.4 and updated to 3.5 using the binary install method. However I still get an occasional blank screen. Do I need to start with a 3.5 Image? Also I run my setup from USB.. As my USB is updated to 3.5, could I just flash the base 3.5 image to my SD card and modify the boot config to load off the USB and have the issue resolved?
2. Arcade Roms folder. There is not any info I saw in the Wiki on this do we place subfolders in here for MAME and FBA etc… many of the rom names are the same but require diffrent versions. Just wanted to get more info on this.
Topic: Amiga Emulating Setup
Hi,
So I thought I was all setup and ready to go, up until I got to the configuration when I realised, I’m going to need a keyboard.
Much to my surprise, my PC keyboard is actually PS/2 port! I don’t own a USB keyboard.
Cheapest solution was to help myself to a PS/2 to USB converter from work, but I’ll be swapping over from PC to RPI. So I want to buy a USB keyboard.
As silly as this sounds, I don’t know what to get. I want a slim keyboard so it can easily transported. I found a slim Xenta wireless keyboard/mouse for a good price, but I haven’t done enough research to know if it is compatible.
Next I come across this, http://www.ebay.co.uk/itm/2-4G-Wireless-QWERTY-Media-Keyboard-Touchpad-Mouse-Combo-For-PC-Raspberry-PI-/281690984379
But if I want to use it for Amiga emulation, I don’t think it’ll be suitable.
Any recommended setups for Amiga emulation? Any known compatibility issues with wireless keyboard/mouse combos? Is the touchpad/keyboard combo any good?
Thanks
TomHello,
I am very new to RetroPie, command line, and the whole raspberrypie thing, but I have carefully followed all of the installation instruction and coding that I can find. I have looked over my wiring many times and everything appears to be in order (Please see attached pics)
My build is in a SNES mini, i have retained the original controller ports and on-off switch, and have soldered onto the bottom side of the board at those points. I had to retain the main original SNES board, because the ports and the rear panel are connected to the main board. I simply hacked everything off of the original SNES bard to make room for the Rp2.
I went through all of the online instructions and everything seemed to go okay as I received no errors. Retropie and ES boot up without issues and run smoothly, a USB SNES controller is connected via USB and is working as it should, a usb wifi dongle is plugged in and working as it should and is connected to my network. A wireless USB keyboard dongle is also working as it should.
The ControBlock Power switch function works as it should and powers the system up and down completely without issue.
Here is where things go wrong, when I boot up, I can see that 3 controllers are recognized, but only the usb controller is active, I am never asked, nor am i able to configure the two controllers connected to the original SNES ports. I have scoured the internet and this blog looking for answers and have tried everything that i can find, but still no working controllers besides the USB one. Here is what i can tell you about my system:
– Raspberrypie 2
– latest retropie sd image installed and working properly (from what i can see)
– controlblock rev 2.1 (wired for SNES) on off switch working properly
– System is not over clocked
– device tree is enabled
– 12c is enabled and set to load as default
– SNESdev is disabled
– Input gamepad type at: (sudo nano /etc/controlblockconfig.cfg) is set to “snes”That’s really all I know to do and look for…
With everything else working as it should, I can only assume that I am missing something simple here…As I said earlier, I am (very) new to raspberryPie and command line, so anything that you need me to do to investigate this needs to be spelled out very clearly.
For instance, I see basic commands on the blog like “jstest /dev/input/js1” for testing basic functions, but… when i simply type “jstest /dev/input/js1” into the command line, I get the error: (-bash: jstest: command not found)
So I assume that I am missing something… I really need full (new user) instructions please.Any help in this is greatly appreciated. Thank you in advance!
MichaelI’ve been trying to set up a controller for use with RetroPie and regardless of whether I try a PS3 or Xbox 360 controller I’m seeing a similar error.
When I boot up the Pi, the controller will initially work, but after a period of time (it seems like a constant period, but can’t be sure) the controller resets and I’m unable to use it. When it happens with the 360 controller, I get the error message:
[ERROR] XboxdrvDaemon::launch_controller_thread(): USB device disappeared before it could be opened
However, since the problem is also occurring with my PS3 controller, I’m not convinced it’s an issue with Xboxdrv.
I’ve set up Xboxdrv through RetroPie_Setup.sh, and tested the PS3 controller both with and without going through install/pair PS3 controller. Regardless of how I do it, I’m still getting the same problem.
It doesn’t seem to matter which USB port they’re plugged into, and the keyboard works fine, so I don’t think it’s necessarily a hardware issue.
If there’s any more info that I could provide to help diagnose what’s going on then let me know!
Pi Model: B
RetroPie Version Used: 3.0.0
Built From: SD Image
USB Devices connected: Logitech keyboard
Controller used: PS3 Dualshock (with USB cable) or wired Xbox 360 controllerI recently installed the latest version of Retropie on a rpi2. During setup I installed a keyboard, Xbox 360 wired controller, and a PS2 controller using a USB adapter. Somehow during setup the Xbox controller became assigned as game pad 3.
Does anyone know how to change this to game pad 2 and have the PS2 controller as game pad 1?I’ve tried rm /home/pi/.emulationstation/es_input.cfg and then rebooting with only the two controllers attached. When I set them up again, gamepad 3 is assigned to the controller.