thank you. that file did the trick.

i wasn't using an old version of retropie though. in fact it was a fresh install of 4.1. i even updated all installed packages via the retropie setup.

maybe they changed it back?

anyway thanks again!

Well if anyone is interested, I figured out what was wrong.

Somehow, something caused a file to be created in the configs/all folder called "videoresolutions.cfg" (or something to that effect, I forget the exact name) and it was telling Mame2003 to force a resolution of 320x240. I deleted the file and everything is fine again.

@cashnewman the bios zip goes in the ROM folder. Stick it in BIOS too if it makes you feel better.

I found a solution in case anyone else has this problem in the future:

I did cat /proc/bus/input/devices to list input devices, which does not give the full ID. But I saw a "Wireless Controller" listed there, so I knew that was my bluetooth controller. I saw it had an H: Handlers set as event0 and I recalled being ale to substitute this for the full ID. So, instead of doing --evdev /dev/input/by-id/*** where the ID is still unknown at this time, I was able to do --evdev /dev/input/event0 instead.

Now whether or not the button mappings I did are accurate is a whole different problem. Time to go test it out.

@rbaker fixed it, I just updated all my stuff through the source and they work now!

@dsfrancis got my controllers configured. Now I just need to apply my shaders and I'm set.

@Ditch123 said in Run And Gun 2 and outrunners:

Overhead? Sorry i cant understand can you elaborate further. English is not my native language

Not a problem. It really just means that it takes more processing power to run the exact same games in lr-mame2010 than it does in lr-mame2003. As a result, most games will run smoother in lr-mame2003.

@monkee

That which is most obvious is often obscured.

Your lucky numbers are:
6, 34, 1, 19, 8, 11

I have purchased the above adapter and can finally get the wireless adapter to power on, but when it is attached to the pi the controller will not connect to the wireless adapter. Any thoughts?

They need to be downloaded. Go into RetroPie Setup Option in the GUI. Choose Config / tools. Scroll down to 827 - splashscreen. Choose 8. Then 9. Then choose any splashscreen you want...

Did sadly not work even tryed using my usb snes controller and did sadly not work:/

@SeTzX You have not described what process you followed. You sure you have a Pi with built in wifi? You went to retropie setup and connected to the access point using your network ssid and password? got the ip of the Pi? using winscp or putty? Also you can just browse the relevant folders on a pic without ssh if you want, they appear in the network tab. In most cases you have to look it up via IP address...

On Windows though, go to My Computer then click map network drive, then click browse and click on the Retropie folder to map...

If it doesn't show up then you may have a firewall issue...

To find the IP address you can either check your router interface or go to WiFi settings on the Retropie menu.

@gusrod1580 Yes but earlier in the file you are assigning 8 to select and enable hot key as well as exit emulator. So you will get no functionality even if those last lines are removed.

@timothy_atwood onyx is a Mac OS app. It does a lot much more. It's just one feature that it does.

I am having the same problem getting this to work in RetroPie 4.1 with two players. It works fine with one player.
I installed driver v0.1.4. manually back in RetroPie 3.8 and got it to work with two players no problem. But now for some reason I can't seem to get it to work with two players.

I installed this driver automatically from RetroPie Setup drivers install. So it was not a manual install this time around.

I then ran sudo nano /etc/modules to verify that mk_arcade_joystick_rpi was added. It was.

Then I ran sudo nano /etc/modprobe.d/mk_arcade_joystick.conf and added the line options mk_arcade_joystick_rpi map=1,2 Making it the only line in the file. Saved the file and exited.

Performed a reboot and BAM! Joystick 0 is detected and works, but Joystick 1 is not.

Is there some other thing I need to do to make this work? Thanks in advance.

EDIT: I reposted to a new thread since this one is marked as solved, but does not solve my problem.

Sincere thanks, guys. I finally got it to work last night by installing a completely different build (Steve Smith's triple-boot at http://www.multibootpi.com/). Still not sure what happened, as this setup just worked smoothly, ROMs transfer just fine, etc. THEN I had to learn about the wonders of HDMI sound being flaky on RPi, and adjusting the config file to activate it. Interestingly, it didn't work plugged directly into my small TV, but it works fine plugged through the receiver connected to my big TV.

@julian2000P how many raspberries do you see during boot?

Whats your download speed? Or you can get my torrent (the one post above) currently we have 19 seeders.