@buzz said in Bluetooth Controller works fine in EmulationStation, but not in emulators:

@mendingo I don't exactly know - some difference in how the device reports it between the sdl input code and the retroarch udev code. Another option is to switch input to "sdl2" in retroarch config (then the mapping should be the same).

If you give me the name of your controller and your ES vs retroarch config I can put in a workaround. the 8bitdo controllers used to have an offset of 11, but it was fixed in a firmware, which suggests it may also be linked to how the device reports itself.

Sorry for resurrecting old thread, but it took me quite a lot of time to solve this issue and I would like to share this simple fix. I recently bought a bluetooth controller - a chinese cheap one - called Gen Game New S3. It is identifying as "GEN GAME" in retropie. There was the same issue as OP had - only cursor button worked in games, but no action buttons. Simple "hack" is to "switch input from udev to "sdl2" in retroarch config" as @mendingo mentioned. Once this is done and gamepad is remapped in emulation station gui, all buttons work perfectly in games as well.
Maybe this can help to people who bought similar controller.

@keithmason if memory serves, if you exit it and then restart it will work fine. it absolutely does work in lr-mame2003 - i coded the dual sticks option :)

@psyke83 said in Sony DualShock 3 - call for testers: "sixaxis" script module:
...

NOTE: If you don't know how to test PRs, then it may be wise not to try testing this, as I'll need some basic technical competence to provide logs, etc., if something goes wrong.
...

sorry, but I've just read your note about how to test the driver and I fear that I can't help here.
I'm really not familiar with pull requests; and even for basic linux things I need to follow step by step instructions... not knowing what and why I'm typing things in more than 80% of cases.

**
hey mitu, finaly got it working!
But now i noticed the snes sounds are stille crackling,
Am i missing something?**

Followd this guide:
link text

Guide from link:

Ok, first delete the file /etc/modprobe.d/alsa-base.conf Raspbian Jessie does not use this config file like Wheezy did.

To find what address your device uses you need to first enter the command aplay -l this shows all audio output devices, and their address. For example, my USB sound card comes up as device 1 in the output which looks like this.

card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 1: Device [USB PnP Sound Device], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
Now, to set the device to your default card you will need to edit the file /usr/share/alsa/alsa.conf with the command sudo nano /usr/share/alsa/alsa.conf scroll down until you find the lines

defaults.ctl.card 0
defaults.pcm.card 0
and change them to (if your device is also listed as device 1, if not change the 1 to whatever address it was listed at)

defaults.ctl.card 1
defaults.pcm.card 1
Explanation: USB sound cards are registered as card 1 on Raspbian Jessie. On Wheezy they would be registered as card -2 by default and editing /etc/modprobe.d/alsa-base.conf would change that.

I do not know if this next step is necessary but without it my card wouldn't work.

Create and edit the file ~/.asoundrc by using the command sudo nano ~/.asoundrc and change it so that it only reads this:

pcm.!default {
type hw
card 1
}

ctl.!default {
type hw
card 1
}
Now your default audio out (speakers) and audio in (mic) are your usb device.

@darky2003 Thanks. :)

Solved. Had to access emulator settings for the one second the game was booting and disable "Fast Memory (Unstable)". Boots fine now.

Well I had a look in the emulation station source seems es-core/src/PowerSaver.cpp and https://github.com/RetroPie/EmulationStation/blob/master/es-app/src/SystemScreenSaver.cpp would need changed if there is no scripting support. Im going to look at that source a little more. It shouldn't take too much to add a option to add a script option. Like
sh screensaver.sh on
sh screensaver.sh off

i really surprised its not got this option

@point7 Start the game. Open the Retroarch menu (Select+Y on your xbox controller probably). Go to Options. Change Pad 1 Type to Standard. Go back to the quick menu and Resume.

You're welcome.

@greenhawk84 The binary package is based on an older version than the current source. You probably updated from source FBAlpha (or lr-fbalpha) and the 'update all' operation took the last binary version (from the RetroPie site).

@brainslugs83 said in Selph Scraper scrapes unknown ROMs as a PSP game called ".hack//Link" -- even for other systems.:

I'm running version 4.3 of retropie, with the the scraper built from sources last night (2/7/18)

If the issue remains, did you update the scraper recently? Because @sselph made some fixes for this problem six days ago.

@malas13 said in File.img damaged:

Many thanks and sorry for my bad english :)

What bad english? ;) (At least to me as a German it looks fine.)

@dunginhawk nm.. found these https://www.banggood.com/100Pcs-Mini-Micro-JST-1_5mm-ZH-2-Pin-Connector-Plug-With-Wires-Cables-150mm-p-1170260.html?rmmds=search&cur_warehouse=CN now just trying to figure out if i can get them to make them in 300mm

@mitu said in All ROMs running in slow-mo:

Sounds like a slow video driver problem. Are you using the default driver (amdgpu) or the AMD (fglrx) driver ?

I've tried to install the AMD driver but it gives me the following error:

One or more tools required for installation cannot be found on the system. Install the required tools before installing the fglrx driver. Optionially, run the installer with --force option to install without the tools. Forcing install will disable AMD hardware acceleration and may make your system unstable. Not recommended. See /usr/shar/ati/fglrx-install.log for more details.

Here's the log:

Check if system has the tools required for installation. fglrx installation requires that the system have kernel headers. /lib/modules/4.13.0-32-generic/build/include/linux/version.h cannot be found on this system. One or more tools required for installation cannot be found on the system. Install the required tools before installing the fglrx driver. Optionally, run the installer with --force option to install without the tools. Forcing install will disable AMD hardware acceleration and may make your system unstable. Not recommended.

@lordkramgb please fill out https://retropie.org.uk/forum/topic/3/read-this-first

@djawadi Looks like a bad written image or undersized sd card. Please give more details - https://retropie.org.uk/forum/topic/3/read-this-first

@z1mzum Welcome to the forum. In general, it's better to open your own thread for your questions instead of using other's threads in the hope that a solution for your problem comes along. That said, a quick advice: If you can access your Pi over the network via SSH, you can use its file manager from afar. Just enter mc on the command line after logging into the Pi.

@gabgreen For more information - see https://retropie.org.uk/forum/topic/3/read-this-first.
The L/R buttons should not function as hotkeys, if you mapped them correctly in Emulationstation (in the input configuration) as L/R, then they should work in-game. You can open the RetroArch GUI menu to check your buttons by pressing Select + X and checking the Input section.
Please see the read this first page and give more details, especially about the controller and emulator used.

EDIT: According to the manual, the L/R buttons don't function in all areas, so it could be that the buttons are working fine.

When in an action scene, the L and R buttons can be used to scroll the screen forward or backward slightly. [...] This function does NOT work in all areas.

It worked, downloaded it from optional packages from retropie.

@mitu - I've done some more digging. The GameStick doesn't seem to be recognized properly by the evdev system. Found some fun log messages via dmesg:

[ 15.328485] hid-generic 0005:0F0D:1011.0003: unknown main item tag 0x0 [ 15.328963] input: GameStick Controller as /devices/platform/soc/3f201000.uart/tty/ttyAMA0/hci0/hci0:11/0005:0F0D:1011.0003/input/input2 [ 15.330713] hid-generic 0005:0F0D:1011.0003: input.hidraw2: BLUETOOTH HID v7.07 Keyboard [GameStick Controller] on b8:27:eb:03:bd:7f

It appears that the "unknown main item tag" error (which, googling around, seems to be a bug), is causing the controller to be detected by evdev as a "Keyboard". Which, obviously, doesn't work so hot for controller stuff, since the various buttons don't seem to map to anything ES's controller setup recognizes as a button or axis.

I'm going to see if there's any kind of config option or something I can pass to allow this to work...

Memory card has failed, yep.