forums.marpirc.net

INPs should still be downloadable, if you have the original player initials, game name, score and version that make up the filename.

All MARP replays are still available at: http://marp.retrogames.com/inp/log_romname_xxxxxx_wolf106.zip Where: "log" is the player's login ID "romname" is the name of the ROMset in MAME "xxxxxx" is the score "wolf106" is the MAME version used That this still w...

Going from Python 2.x to 3.x could be the main issue here, I seem to remember they are not all that compatible with each other.

I have sent an e-mail to Zwaxy, but no response so far (he's not particularly active)
I can upload or modify files on the server if need be, although I am no Python/MySQL expert.

If it can't find MySQL, then it seems like a server issue. Not much can be done.

Done

Should be, it's in the archive I uploaded.

Did we ever decide how much boomerang leeching is allowable? Saulonpb's latest TMHT INPs (and apparently his now 12 year old TMNT INPs, which are confirmed) will do about 10 per enemy. Ideas were given in the past thread, but it would appear no definitive amount was decided upon. http://forums.marpi...

0.252 binary now uploaded to Github.
https://github.com/mahlemiut/wolfmame/r ... ag/wolf252

Okay, I have a 0.253 Windows binary uploaded, after much screwing around with some hacky setup to get some sort of build.
Please do thoroughly test this, hopefully it should work.
I'll upload a 0.252 binary sometime next week, when I have some spare time.

Unfortunately, I am unable to provide a binary for WolfMAME 0.252, due to the extensive reworking of BGFX, cross-compiling is rather broken. I've published the release, so source is available, and should build natively without issue. If anyone is willing to build a 64-bit Windows version (preferably...

Nothing planned at this stage

I don't have a setup for cross-compiling 32-bit Windows builds currently, maybe someone with a native Windows setup could do it.

Yeah, the hosts don't encourage directory listings (for security reasons), so the files have to be accessed directly. I do keep it up to date, though (when I remember, at least )

There was a lot of work around that time on the M72 driver. At a guess, it could be the MCU, which provides startup code for the game could be the culprit (which would also suggest that this is also correct behaviour). The MCU was not dumped at 0.208.