Leaderboard

MAMEUI Classic 0.255.0 has been released. Fixed a crash with some sliders: Gamma, Brightness, Contrast etc Available at https://messui.1emulation.com

It's all in italian, but there are nice pictures, you can see the page of the kof98 test, which also talks about ips patches. And you can translate the text if you want, by using google lens on a cell phone for example ! Here is the link : https://zzapmagazine.blogspot.com/2023/05/zzapraine-numero-12-in-arrivo.html?m=1

Actually this version number was displayed for neocd in the title bar until may 29th 2021, commit 90761c9f7afc679394d550c4eb4f5e6ef3b42358. The commit was not specifically about that but to fix an incompatibility between 2 games, I guess I probably took it off because I found it made too long titles which is probably true for a lot of games there. Oh well since you are the most efficient bug finder around here I can put it back... !

MAME, WOLFMAME AND MAMEUI 0.255 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

Ok it's fixed, ironic find, it's a specific cue file which creates the crash, and from internet archive, I hadn't even noticed they had neocd files. I won't put auto-download from there though because such a format is really a waste of space ! Anyway the indexes are taken into account that's why there was a crash here, that's indeed the index which crashed simply because it tried to seek in the file before loading it... !!! At least the fix was short. I don't plan to release a binary just now for that, this bug has been here for years ! For info to reproduce it, I had an iso + wav files dump and I hadn't even converted the wav to mp3 (lazy... !). So I just adapted my cue file to look like yours. Then I made a savegame during the demo just before the highscore screen appears. For me it crashed just after the hiscore screen. This way it was very fast to get to the crash, these neocd saves are super efficient ! And finally converting my cue file was not even necessary it would have crashed even with the one I had originally, it's just that nobody left the demo running until now, and for some reason this kind of crash doesn't seem to happen during normal play... !!! Quite crazy ! But at least it was easy to fix. It's a super old bug here again, from neoraine time, you are super efficient to find bugs currently !

I haven't got the latest one, but still more recent than that, I had to allow an update specifically to be able to update the nvidia driver, I couldn't install the latest version without that, so I guess you don't have the latest nvidia version neither ? It must be the 22h2 if I remember correctly, I disabled windows update after that and I hope to keep it at this level for long. Well you are lucky it's minor, just a white cross instead of a green one, because supporting such a specific windows version would seem quite crazy. Anyway... ! edit : confirmed after verification, 22h2, installed late in march 23 because I blocked windows update before, and I still blocked an update on this version (I can now update the nvidia driver so it's enough for me).

Congrats! I used Google Translate to read the main text.

sfz3a is using english text so for this one it's sure sfa3 is totally equivalent is setting the region switch to asia. For sfz3j, it's Japanese text which is obviously not in the rom, so I'll take just this one back for now, but I'll have to check those I removed earlier... progearj seems ok when using progear with japan region at least, so it's probably something specific to sfa... ! 1944 with japan region has almost no text from japan, it even writes USA in its 1st screen but not the copyright screen. So I'll assume the only problem was with sfz3j, if anyone finds another problem, let me know !

I was mistaken, I thought there was a new decryption code finally allowing to totally decrypt the rom, but no !!! In 2023 we are still stuck with opcodes / operands, and by the way raine was already using the same algorithm as xcopy when saving a cps2 rom in debug mode, but what you get are the decrypted opcodes. Some areas of the rom are totally readable directly, like the 8 1st bytes : $ff8000 this is the initial value of the stack pointer at offset 0, but if you go only to offset $60, same file, it should be the vector for irq0, and this vector is obviously unreadable, it's $14e for sfa3/sfz3j but it must be read from the encrypted area. What this means is the roms can't be compared directly, there's still no reliable way to do this ! Ton of crap... ! When you think that the rom encryption keys were in some volatile ram using a battery and so when the battery died you got a useless machine, it would probably have been declared illegal in this time, that's obvious planned obsolescence... ! And so no surprise that you are still unable to get a fully decrypted rom from that. Well, maybe I should just take back all the removed sets, or at least sfz3j then, I'll see... !

* Joyce 2.4.2 [Amstrad] - http://www.seasip.info/Unix/Joyce/index.html * Kegs 1.26 [Apple2gs] - https://kegs.sourceforge.net/ * BigP Emu 1.06 [Atari Jaguar] - https://www.richwhitehouse.com/jaguar/index.php?content=download * WinArcadia 29.40 / DroidArcadia 2.01 [s2650-based] - https://amigan.yatho.com/ * PPSSPP 1.15.4 [Sony PSP] - https://github.com/hrydgard/ppsspp/releases * Raine 0.95.5c [Arcade] - https://raine.1emulation.com/download/latest.html