@supppp nvm

@spm2600 Same problem.

@mitu ok cool thank you.

Had a look and I can't seem to set my input device to anything other than "Wireless Controller" either within the retroarch input menu. I do have the other devices under /dev/input, and evdev does correctly detect the motion sensor/touchpad.

Nothing else obvious in /etc/udev/rules.d/.

The picture doesn't show the error start (though it may be off-screen), but the init not found message means the kernel doesn't have access to the sdcard's files.
Try to backup your image, then use 7Zip to read the .img file, you may be able to recover some data.

@buzz Appreciate this is an old post but anyone know hiw I access the standaone input settings O inca rebind the keys? I have a keyboard plugged into a Raspberry pi running Retropie to use this emulator. Going to check teh docs file now. Thanks in advance, DtM

Edit - I read the docs and found I can access the menu by pressing my hot key + X. Then went into the quick menu > controls > Port 1 Controls. Here I could change the button by highlighting iot and pushing my joystick right to cycle through the different button options. Hope this helps anyone in future looking for the answer.

@misanthrope whenever i have had issues with those controllers i have uninstalled and reinstalled the xpad drivers. also make sure what mode the switch on the front of your controller is set to

As @YFZdude mentioned, the genesis folder is a symlink (shortcut) to the megadrive folder, so there's no need to remove it - it's not actually taking any space. You can leave it as is, it's ok - the scriptmodules expect a megadrive ROM folder and updating the MD emulators will re-create the folder.

@mitu Swear I did BUT I didn't. Thanks!

@mitu LOL... Don't I feel like an idiot... Figured it was something silly and it is.

@dankcushions

Can you forgive me little rant earlier? Sorry. I've had a good play with it now and I think it's working. And I understand what you mean by pressing the hotkey and F1. Is there a way to have it by pressing F1 alone?

I've Reset Retroarch config and plugged in a Wired Mouse and keyboard and OP Wolf is working now.

I've also changed my RetoArch to Ozone just like my PC. It's much less confusing now. It's going to take some time to get used to this :)

Both advmame and advmess configuration files are under $HOME/.advnance - named advmame.rc/advmess.rc. Game specific configurations are saved there, prefixed with the game/romset name.

@goldengalaxies jzintv working?

They are sorted by type, then alphabetically.

So emulators, libretrocores, ports, supplementary.

Uh dang, I need to make some retractions here.

I went back to re-examine the joystick circuitry and stuff and it looks like the thumbstick works fine at any voltage. (I felt my logic was odd when lying in bed the other day). The "lopsided-ness" I was talking about is actually caused by setting the range incorrectly. Ignore what I said for #1 in the previous post. The thumbstick appears to behave the same with 1.8V as with 5V (from a design standpoint, you'll probably save a little power by driving it at 1.8V).

Most modern joysticks expect something in the range of -32767 to +32767 with the center/neutral point (when the joystick is not being touched) being 0. Why? Because this is the min and max values you can represent with a signed 16 bit integer. To be extremely pedantic, you can actually go to -32768, but we pretend it's -32767 to make it symmetric.

When I did the mapping function, I take an input range of values going from ~70 to ~325 to 0 <-> 16384. I think this is where the "lopsided-ness" comes in. I'm using a built in function from the Arduino library called map() so I don't exactly know what is going on, but it places the center point somewhere around 4000 instead of ~8150 as you would expect. This isn't a problem if the output range is -32767 to 32767 for some reason.

@dankcushions

ok i did that, i hope it fixes it

@crossmr Turns out I had the wrong image, after hours of slow downloads, I managed to get the same pi zero w image that I had before. it looks like the rom in question was being run on lr-fbalpha, not fbalpha2012. This was a retropie 4.2 image. The performance on lrfbalpha seems slightly better than the alpha2012 that is available on 4.6 retropie but still not as good as pifba.

@crossmr I managed to get the controls reconfigured, however the graphics option"MaintainAspectRatio=1" doesn't seem to work in the config file. Right now the image is stretched to the sides, instead of maintaining the proper aspect ratio.