Fatone85

Hello all. I realize I haven't been online now for a while, and I hope I haven't disappointed anyone by not progressing on the software. The last year or so has been an intense one for me and I'm just recently getting back onto the online community. My question is this: Is there still a need to contribute further to FatMatch? I have noticed other utilities surface such as Skinny Match which seem like impressive software and with more dedicated contributers. Let me know your thoughts.

That's true. You would end up getting random load errors from the emulators and have to let your guests know that you faked them out, thus shooting down their hopes.

I'm not brainstorming too much into this, but as a quick thought, you could create a pseudo-file (for example, create a new text document that contains nothing) and name it after the ROM that you don't have. This way GameEx would assume you had the file and display it as such. As an example, if you don't own "Metroid.smc", create a blank file and rename it to "Metroid.smc". GameEx will not know that it's not a ROM. Just a though.

Try (right click "Save As"): http://emumovies.com/torrents/EmuMovies_Vi...0325%5d.torrent

My laptop has a Logitech LCD panel on it which uses the same drivers and software as the G15 keyboard, and I cannot use this LCD panel with the plugin. Having said that, I haven't put much effort into getting it to work. That's the only help I can give you. Cheers.

Just for a quick update. I haven't given up on FatMatch. I work on it when I can. Things are getting pretty hectic at work with a bunch of guys being laid off every week. So I try to do as much as I can there which is taking up all of my time. I'll keep you all posted.

Welcome to GameEx. You'll fall in love with it, I promise. Between Tom Speirs, Brian and the Guru users, I really don't believe there is a better community out there for this type of software. Cheers

I'll make it an option in the next release. Thanks Alkis.

I guess I would be one of the young-guns here, having just turned 24.

Thanks for all the ideas! I'm working straight on the next release and I'm trying to address all your issues as I go. I'll keep you posted.

I can understand how that would seem like the better way to go, and I assure you that this is the way I had originally coded the algorithm, although the problem arose when I got into larger amounts of files. For example, I have a set of 872 Sega Genesis ROMs and I just downloaded a set of Title images that contained about 1000 images. The average word count of the ROMs filenames is 4. With 4 words in a filename, you have 7 possible neighboring permutations plus the individual words themselves for a total of 11 attempts at matching. The algorithm does this on both strings, so that becomes 22 attempts. This means that each time a single rom filename is matched against the 1000 images, 22000 attempts have been passed through the search code. So with a set of 872 ROMs, the code would have cycled 19,184,000 times. And that's just on an average of 4 words per filename. Some of these filenames might have 9 or 10 words, which becomes increasingly bigger. The app was so boggy when I tried doing it this way that I had to change it. What I have implemented as a near fix is to have the program search a word for Upper-cased letters and separate it at that point. (i.e. BomberMan becomes Bomber Man) I'm also working on a guide to help people with using FatMatch at it's full potential. In this guide, I suggest matching at a high accuracy rate like 80% or higher and then rename the files that you select. You can thereafter run the "List Missing Images" function to move the matched Images and Roms to a temporary separate folder, where-after you can run another Matching search at a lower accuracy like 49%, which would yield you more broad results, but without over-listing possibilities. Please keep the suggestions coming!

Hi all, Thanks for testing this software and reporting your issues. In this case, bkenobi is correct. Using the ultimate algorithm to match words or "Fuzzy Matching" is incredibly tedious. You have to somehow predict what the user would see and validate as a match if he/she was doing it manually. One example of a match that would seem very obvious to the human eye - but not so much for the program - is in the case of say "Bomberman" and "Bomber Man". The application always matches two strings of words. The first being the filename of the ROM, and the second being the filename of the Image. It first takes the ROM name and splits it into words, and gets a percentage of the match performed. Then it does the same for the Image name, against the ROM name. The result of these two matches yields two values that are weighted at 50% each of the final Match Percentile. So in the case above. The program takes the ROM name (Bomberman) and splits it into words. Since Bomberman is technically a single word, it starts matching it against the Image name. When Bomberman is tested against Bomber, it returns a match count of 0 (Since Bomberman in reality is not the same as Bomber). When it is tested against "Man" the same result. Now that takes care of half the search, where you are still at 0% matched. Next the program would split the Image name into words and find 2 words (Bomber and Man) and match them individually against "Bomberman". So if you follow me, Bomber IS present in Bomberman, so there's 1 out of 2 words matched. Onto the next word, "Man" IS present in Bomberman, which brings us to 2 out of 2 words correct, or, 100% of the second string tested. Gathering all the results that we just calculated in the past fraction of a second, we can determine that the first of two searches yielded a 0% match (0% x 0.5 = 0) and the second search yielded a 100% match (100% x 0.5 = 50). Add them together, and you have a final result of 50%. (0% + 50% = 50%) So you can maybe see how sometimes, the computer is too smart for it's own good. The computer does not know that Bomberman is pronounced the same as Bomber Man when spoken, and therefor doesn't differentiate properly between combined words and separated words. IMBerzerk, the reason why your search rendered bad results is an error on my part. For some wonky reason, the portion of code that replaces underscores with spaces was commented out in my code. I'm glad you pointed this out as it is a potentially crucial mistake. Thanks a mil!

Hey Tom. Thanks for your continued interest in FatMatch. It's an honour to have you mention it. If you feel that it's worthy enough to be included in the GameEx download, then by all means ... hell yes! I'm currently working on some added features for the 0.4 release, which will include a CRC matching scheme (this is proving to be pretty handy, and I'll elaborate more on it in a few days). I've also noted a few requested changes from other posts that I've come across, and I'm working on adding those features as well. Thanks!

Good work!

Hmmm, sounds like you downloaded GameEx Remix 2009. The new version that Tom is working on. ..... No I'm just being an idiot. Sounds like this is a MameUI32 issue. If you load up a rom manually (without GameEx) it does the same thing right?