Looks like you've not defined a Hotkey when asked in EmulationStation input mapping - that's why B resets the current game. What version of RetroPie are you using ? Can you add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first ?

@mitu I can confirm: downgrading SDL to v2.0.8 solved my problem! Thanks for the help, as always. :-)

Any update to this? I hate not knowing how much battery life is in my controller.

After hearing the replies I think I will just power it on with the front button. Thanks for the replies!

@ivooc Yeah I meant threaded video. I've had the same RetroPie build from version 4.4, its hard to remember all the changes and configurations I've made. I'll try to share once I think of them. Do you have a fan installed? The temp_soft_limit is 60 by default and will throttle the cpu to 1.2ghz I increased the soft_limit to 70 and it barely reaches 63 during emulation. Have you updated retroarch, raspbian, and your cores, since you installed the image? the firmware, I should search to find out for sure, I think it is updated when you go to retropie config >> configure >> raspbian >> update raspbian(next to install pixel desktop) It could be a psx_bios, some have higher compatibility, I have quite a few in my folder actually, but I think scph_101 is the highest compatibility and it will be chosen over the others, not to be confused with scph_1001. As I say that Gran Turismo refuses to work. I don't know why, but I did update the core since I last played it.

@mitu said in ds4 and ds3 pads together: @pplatinumss .... Remove the PS3 driver and install the customhidsonly driver, then try to pair both controllers. Remove any previously paired controller before doing this. ok. That worked like a CHARM. MANY thanks I removed dual shock 3 driver added the Sony hid one and paired the DS3. The DS4 pad was working from being previously paired. Awesome

@webodan I don't think ES reads the list of Audio cards present in the system - the choices you see now are the default choices. Try using the instruction from the USB Audio FAQ page.

@rsn8887 RetroPie doesn't automatically maps the keyboard as a controller - it only saves the gamepad configuration from the configuration you made in Emulationstation. Unless you explicitely map the keyboard in ES, it shouldn't generate any configuration for it. You can find the saved configurations - one per gamepad configured - in the /opt/retropie/configs/all/retroarch-joypads folder. Must be a new RA thing, does it do the same without the keyboard plugged in ?

Thanks!

@herb_fargus said in Anyone's Inputs Change with 4.4?: There were some driver modifications but don't know how they affect PS4. It was discussed at length on GitHub. Don't remember if it was merged in or not before release Would this thread be what you're referring to? I wonder if that's somehow what I'm running into somehow? Edit: Just checked. Still at 1.7.1. Edit Again: Follow this thread.

@blerkotron i have got the same issue with the analog sticks using a Sixaxis Controller. Also works fine with jessie. Something seems to affect the analog Inputs of Sony Controller when using stretch.

but including retro pie I think you might just make with exactly 16 GB

@mitu thanks, im try it later)

@dankcushions O thanks that's very helpful. I really had my eyes set on the ps1 styled 20th anniversary ds4 controller, but that color layout is only available as a V1..so that could still be an option. (I prefer wired.)

@meleu That's okay! I've had a few issues specific to the DS4. I guess I'll just roll back to my last SD save.

I confirm the same as @mosi0815 the buttons in runcommand are very slow to respond, but indeed it is much better (but not good!) when controler does not move. By very slow I mean we need several seconds to have the button acquired. Thus, I need to constantly press (not hold) f.e. DPad Down button for few seconds to see the action reflected in runcommand menu. Other menus and games work perfectly fine. Edit: The problem is due to time.sleep is always performed, even when there are events. So after each event is processed, the script waits some small amount of time, if there are many events waiting to be processed, then this is lagging menus. I fixed this problem by amending /opt/retropie/supplementary/runcommand/joy2key.py At end of script I added check if the script can sleep, so if event occurs no sleep is performed: js_fds = [] rescan_time = time.time() while True: # added this: do_sleep = True if not js_fds: js_devs, js_fds = open_devices() if js_fds: i = 0 current = time.time() js_last = [None] * len(js_fds) for js in js_fds: js_last[i] = current i += 1 else: time.sleep(1) else: i = 0 for fd in js_fds: event = read_event(fd) if event: # added this: do_sleep = False if time.time() - js_last[i] > JS_REP: if fd in js_button_codes: button_codes = js_button_codes[fd] else: button_codes = default_button_codes if process_event(event): js_last[i] = time.time() elif event == False: close_fds(js_fds) js_fds = [] break i += 1 if time.time() - rescan_time > 2: rescan_time = time.time() if cmp(js_devs, get_devices()): close_fds(js_fds) js_fds = [] # added this: if do_sleep: time.sleep(0.01) Created pull request with this fix: https://github.com/RetroPie/RetroPie-Setup/pull/2039

@mosi0815 thanks for the reply I will test that out soon. It makes perfect sense to me sounds simple enough. Is echo 1 to enable and echo 0 off? Nvm ill try it out tomorrow if I can.

Something got corrupted during the install. I did a fresh install and it works fine.