Thanks - updating VICE on it's own didn't work (I tried that) but updating the retropie-setup script first, then VICE, seemed to do the job.

@felleg I've just read your method to configure the controller for a specific console and I think it's not a good approach. Your configs/megadrive/retroarch.cfg is ignoring the global configs/all/retroarch.cfg.

My suggestion is:

recover the default configs/megadrive/retroarch.cfg (check if you have a retroarch.cfg.rp-dist on the same directory, that's the default config). configure your Hori controller in emulationstation like a SNES controller (square = Y; triangle = X, circle = A, etc.) You need to define if you want to use your Hori controller for player1 or 2, and make sure you'll always use it as that player (if you change, you need to remap). And then use the Core Input Remapping when running a megadrive game and use the following scheme: MegaDrive = RetroPad B = A A = B C = R2 Y = X X = Y Z = R after remap, select Save Core Remap File.

@scampa123

I got it to work! I re-ran it multiple times using Append and different DBs..All roms are tagged except for one!

@BuZz point taken. Thanks again for your input

I apologize, I guess my configuration information would help troubleshoot this issue.

I have searched the forum and have not found a fix specific for the xbox one controller. The basic issue seems like I can not point this emulator to use the xbox one controller configs. So if we can figure out how to get libetro 2003 to use the same controller mappings as mame4all we will be golden.

Pi Model: (B, B+, 2 B etc..): Raspberry Pi 2 -Model B - Version 1

RetroPie Version Used: 4.1

Built From: Using base 4.1 image from retropi website download link

USB Devices connected: Keyboard

Controller used: Xbox One S - Connected by USB

Error messages received: No error message. Can not back out of Emulator

File: (File with issue - with FULL path): no exactly sure what file is having issue with the configuration. My guess it is one of the files in /opt/retropie/configs/all/retroarch/autoconfig or /opt/retropie/configs/mame-libretro/

Emulator: (Name of emulator - if applicable): Mame-libretro 2003

How to replicate the problem: I was able to replicate by doing a complete reload and taking the base image 4.1 offered on the retropi website. I was still unable to configure libretro to work. When I got it to work earlier I must of done some global configuration to get it to work because I was in Mame4all and then went to libreto and it worked. Eventually something happen to muck up my controller configuration.

@Shakz will try...

Edit: Aha, there seems to ONLY be an issue with the N64 emulator. I had mapped by triggers and shoulder buttons wrong, so that is fixed now. It works on all emulators but the N64 one - which is unfortunate considering that's the one I use the most.

Edit 2: It works now?! It just doesn't display the text that indicates that a save state has been saved / loaded / selected! There is still the fact that Majora's Mask lags when NPCs are in the area, but that's something I can live with for now. Thank you for your help!

@BuZz
That did it, works like a a charm now. Thanks a lot :)

@Hype built-in bluetooth works fine for me with my 8bitdo NES30 Pro controllers without lag.

@Bluediablito note: RetroPie images include the latest xpad driver by default and it can be updated from the retropie-setup script under Manage Packages -> Drivers

@FlyingTomahawk said in PiFBA buttons don't match jtest:

Not sure the following works for every arcade stick but it did for me.

Unfortunately there's no standard for these numbers. Every manufacturer set them up in different ways. The best way is to use jstest to discover the numbers.

BTW: in some bluetooth controllers the numbers obtained in jstest don't match those used in configs.

@herb_fargus Thanks for that info mate, much appreciated! Works a treat, will just have to replicate it a fair few times for all the games but thats fine! All in good time!

Cheers!

Thanks for the help. That did solve it for running it myself but the python script still failed. I get

/opt/retropie/configs/all/autostart.sh: line 1: 3353 Terminated emulationstation
tput: unknown terminal "unknown"
'unknown': I need something more specific.
Error opening terminal: unknown.
Traceback (most recent call last):
File "/opt/retropie/supplementary/runcommand/joy2key.py", line 42, in <module>
curses.setupterm()
_curses.error: setupterm: could not find terminal

Then emulationstation proceeds to launch again.

In the end I got everything working by going back to RetroPie v4.0.2. I really do not care about having the latest version for this one as it is more of a novelty item than anything since I can launch games with cartridges.

@Dochartaigh I just did a quick read of your progress (or lack of same and I really feel your pain!!) and I may have missed something but was just wondering if you have tried a USB2 port and reader to burn the image and a larger microSD card (maybe 32gig)? I would just load the basic image to see if ran OK, then add ROMs one at a time till it fails. Please don't think I am patronizing you or your effort.

Well this is what happens when you realize Retropie doesn't yet support direct I2C connections.

Re-attached half of a nunchuck cable, going the Bluetooth route as it seems that's the only way to connect a Wii controller+accessory to Retropie.

alt text

Howdy Friend,
Nope sorry there is no way...at least with my setup. All my dreamcast games have a cue file followed by track1 track2 track3 etc.
All the other games have the exact same files so the only way to keep it from messing up is to keep everything in a separate folder.
Unless you are using...I think they are called CDI files which compress and combine the audio files....but you take a major hit on audio quality when you use them.
Just my thoughts.

@BuZz Yes. I have not tested it personally, but users are reporting it working with composite video.

Note that the timings programming is enabled only after configuring AdvanceMAME with the advcfg utility to add the proper monitor clock information. At that point AdvanceMAME starts generating video mode at runtime, taking into account the monitor capabilities. More precisely, it's enabled if the "device_video_clock" option is present.

If no configuration step is done, AdvanceMAME uses the current video timings, and ask the Framebuffer to do the scaling, like in your changes.
Likely the only difference is that it takes into account of the aspect ratio.

@seanami

is this a known bug, and if so is there a resolution or workaround

You have to write your own Kodi controller mapping file from scratch.

The easiest workaround is to just use a little Bluetooth keyboard (which is nice to have anyways). I've got this one and it works pretty well.

Kodi 17 should be coming out before too long and it has a controller mapper built into it so this shouldn't be an issue after that.

Is it specifically ps3 controller? or is there a list of ones that fall into the bug category so I can use a compatible one

I'm not sure but it seams like the PS3/4 and Xbox 360/One controllers don't work out of the box using the xpad driver.

If you want to make your own PS3 mapping for Kodi, then check out this thread with my experience of making a Xbox 360 mapping file:
https://retropie.org.uk/forum/topic/3580/wireless-xbox-360-controller-issues-in-kodi-16-1-on-retropie-4-0-1