@Jofo well, being that I now have several versions of the PSX bus reader, I can talk about my results with all versions.

The original version of the driver, even with the Select button filtered, definitely had sporadic issues with input glitches. My updated version was nearly perfect after filtering the Select button. I'm pretty sure the Acknowledgement line implementation is what did it. I'm pretty confident in that one.

However, the Arduino reader is 100% perfect. So far I've needed no filtering, it all just works. I need to work on the CPU usage of the driver though, still, but for what it's worth, it should work on the Pi. Just plug the Arduino in with USB.

@AlexMurphy

@obsidianspider

Of course who could forget the whole stealing RetroArch code thing:

https://www.libretro.com/index.php/retroarch-license-violations/

@ljm99 Kodi has an add-on called ROM Collection Browser for playing your existing roms. I've never used it, so I don't know how well it works, but I thought I'd mention it.

You can check the status of this here:
https://status.aws.amazon.com/

Just updated everything, retested it: WORKING!
Thanks so much for your help. I was already creating all the MD5 checksums and doing some regex & excel magic to combine all lists LOL

Thank you! :-)

@moe_diggity81 you have to use etcher if you want to write a gz file

@camaro5690 Whew! Ok, that was odd for sure. As for PSX, I can't offer much help, as I have not used it.

I think this has to do with thegamesdb being very slow, or even down at times. Specially the last day. I can't even scrape anything without it saying it now, even with Selph's. There are other options on Selph's, but not inside emulationstation.

Can a programmer possible explain what this means. It is beyond my ability to decipher:

It is related to my problem of the joystick not working while the button do work with my Mayflash F300

What steps will reproduce the problem? 1. Use hori fighting stick mini 3. 2. Try using the stick. 3. Does not work,

What is the expected output? What do you see instead? Stick working.

What version of the product are you using? On what operating system? Rasbian, mame4all compiled from change set: ea85746014e2c2a85665f2a4d4a4b87e819a5287.

Please provide any additional information below. I made a patch that works for me.

Attachments
patch.txt 1.23KB
[diff --git a/src/rpi/input.cpp b/src/rpi/input.cpp
index 10dc318..14eb69f 100644
--- a/src/rpi/input.cpp
+++ b/src/rpi/input.cpp
@@ -672,14 +672,38 @@ extern SDL_Joystick* myjoy[4];

int is_joy_axis_pressed (int axis, int dir, int joynum)
{

if (!myjoy[joynum]) return 0;

if (joynum > 3 || !myjoy[joynum]) return 0;

int hats = SDL_JoystickNumHats(myjoy[joynum]);

if (hats * 2 > axis) {

// Each hat has two axis Uint8 hat = SDL_JoystickGetHat(myjoy[joynum], axis / 2); int sub_axis = axis & 1; /* Normal controls */ if (dir == 1) { if (sub_axis == 0) return (hat & SDL_HAT_LEFT) != 0; return (hat & SDL_HAT_UP) != 0; } else if (dir == 2) { //right down if (sub_axis == 0) return (hat & SDL_HAT_RIGHT) != 0; return (hat & SDL_HAT_DOWN) != 0; } return 0;

}

/* Ajust for hat axis */

axis -= hats * 2;

/* Normal controls */
if(dir == 1) { //left up

if(SDL_JoystickGetAxis(myjoy[joynum], axis) < -12000) return true; if(SDL_JoystickGetAxis(myjoy[joynum], axis) < -12000) return true; }
if(dir == 2) { //right down if(SDL_JoystickGetAxis(myjoy[joynum], axis) > 12000) return true; if(SDL_JoystickGetAxis(myjoy[joynum], axis) > 12000) return true;

}

return 0;]
Comment #1

Posted on May 27, 2015 by Happy Monkey
Thanks so much for this! It worked great for my same stick.

How I used this patch:

--from the console on the pi mkdir mame4all cd mame4all git init git pull git://git.code.sf.net/p/mame4allpi/code/ --download patch and copy into mame4all directory (I used WinSCP and had renamed mine sticks.patch) git apply sticks.patch make --after quite a while it should finish and you'll have a file "mame" right there in your mame4all directory, cp it to where ever your mame launches from, I am using retropie so I: cd /opt/retropie/emulators/mame4all and then: sudo cp /home/pi/mame4all/mame mame

@R2dTOO Are you using .bin/.cue files? Might have something to do with the .bin files being hidden. Stick an eboot .pbp file in there and see if it shows up. I use .pbp files and it displays the number of games no problem. In fact I wish I could turn this off!

@djoveryde I know it can get frustrating. I have a few Zeroes myself and they're touchy. I guess that's what you get with a $5 computer.

Some searching says

4 flashes: start.elf not launched

http://elinux.org/R-Pi_Troubleshooting#Power_.2F_Start-up

@sticcino I am picking up a couple things from your message. First, most of us keep the roms zipped. There are no folders used, just a single folder filled with zip files, and the actual ROM chip files are zipped up inside them. That said, I think MAME can work with them unzipped in folders of the same names, but maybe not FBA.

Second, MAME is able to look at multiple zips to load dependencies. In other words, the necessary files can be in other zip files (or other folders, if your ROMs are not zipped), but as you say, 19xx has no parent ROM.

Assuming you are using the correct romset for the emulator you are launching, it sounds like you might have a permissions problem, either with the folder, or the files themselves. Where exactly is this "clean" folder you are using, and what emulator are you using?

@obsidianspider I've connected them individually from power off direct to the pizero USB port using a single otg cable, one controller detects and the other doesn't

@NYIslanders91 when I tried attract mode i followed their forum and this guide to get it going. I since returned back to Emulationstation on my pi.

A PC with a Core i CPU (and a Nvidia videocard) should be the best solution. The most arm boards are to slow for GameCube emulation.

@dankcushions Thanks!