Hi there!

So the reason why i'm writing this is, because i talked to Fab about a new MAME port.
The most ROMs you can find in the Internet nowadays won't work with the old version of MAME available for MorphOS.

Fab told me that he has limited time and that there are other more important things to be worked on like OWB etc.

Now i was hoping that we could get enough people interested in a new MAME version to show Fab some love for his work and convince him to start porting the most recent version to MorphOS :)

What y'all think? If we stick together maybe he'll take the time to work on that

I'd rather more work on OWB to be honest.

hmmmmmmmm......

I don't use mame much.

Had no idea it had issues with roms.

OWB is more important.

I wonder if developers could not set someone up with a proper system to go at it themselves.
I'd be willing to tinker.

i also think that OWB is more important but working on MAME would only take a specific amount of time until its done. it would only delay the next OWB release, its not like dropping development.

well I use mame extensively and it is a huge part of why I even use my system. Perhaps he should start devoting some
time to updating. It is another of his finer works! I use ver. 0.121, owb has been constantly updated. I saw no real need to move up to the broken arm ver
sorry fab, so I still use 1.17. The main problem Fab has stated is that it gets slower with each release, and that discourages him. I had requested atleast
support for MVSC2, which I'd love to see, but oh well. I'd hate to go the pc route, since all my setup and data is on morph.

MAME 0.120/0.121 works just fine with all roms, provided you use 0.120/0.121 rom sets. New romsets will be incompatible of course.
These romsets can be found in various places... :)

About updating MAME, it's not very difficult, just boring, because they entirely switched the osdependant layer to C++. This layer is the code I have to refactor in C++, considering i don't use the SDL backend there, because it would slow it down even more, and it wouldn't have a builtin GUI.

As i had mentioned earlier, the problem is indeed some systems really get slower as MAME project goes. Psikyo hardware system is now 5-10 times slower than it was in 0.12x (that's an exception though, most systems didn't get affected, or only a little (5-10%). My latest build of MAME was 0.140 and it worked properly, but i never released it.


[ Edited by Fab 04.02.2013 - 10:19 ]

I finally found a little time to update MAME to a more recent version (0.145). I'll update it again to 0.148 since they probably didn't change a lot the osdependant layer since (i hope !).

Anyway, it works rather fine. A bit slower, as expected of course. For instance, CPS2 games like street fighter alpha or dungeons & dragons run at 180% speed instead of 200% with 0.121. And any SH2-based system is amazingly slower (for these, stick to 0.121).

So when i'm happy with the port state, i'll release a new version of MAME.

Oh by the way, the binary is now... 118MB large... Insane ! ;)

@Fab can we download it from your page?

[ Edited by CountRaven 29.04.2013 - 05:44 ]

No, it's not ready. I still have to fix the GUI and i'd rather update to 0.148 first.

@xyphoid

Don't even hope to run mvsc2 at a reasonable speed, by the way. This system uses a 200MHz SH4 CPU... That's really too much.

[ Edited by Fab 20.02.2013 - 06:53 ]

dam! thanks though man! don't forget all the multiplayer scripts

Question Fab, mkII was one of my favorites, but it's really slow now (unplayable). It seems those from mk 2 up to mk4 are affected. Mk works fine. Have we lost those, from here on? Not a big issue, as you said stick with 0120 for those.

Are the multiplayer modes working in 0.48? Sticks 3-4 aren't registering in game config. for me.
Thanks!

Quote:

I only listen joystick 1 and 2 AFAIR (i didn't register 3 and 4 because listening for events had some impact at some point).
Anyway, if you really need it, i could make a build for additional joysticks.

Whenever you get around to it Fab.
Thanks!