Home Page Forums Archives MacMAME MacMAME 0.95 Xcode projects posted

Yes, but (and I'm not trying to be insulting here) if Arek is actually putting out updates in sync with PC and you aren't, maybe his should be official and your build can be a special "turbo" one that comes out whenever you have time.

Alex,

As always

I've still been having some issues myself. 95 was holding the default configuration for a while, then I opened up "Narc" (which was a bad idea for so many reasons), and it all went back to default.
To prevent this from happening, I set up all the default configurations I could possibly want, then quit MacMAME, opened default.cfg, and locked it.
I may not know how to do it right, but I can do it so it works.

Belmont's got a point, why not make the new MacMame the official one, and Brad's a special turbo one. I'd really like to see a version of MacMame updated at the same rate as the PC one, no disrespect to Brad's work...

For speed-problems on Sega games and other's which seem to be slow, be sure to uncheck frame-skipping in the MISC menu. I was so happy to find out Thunder Blade now 100% in MacMame, running pretty much full speed on my PowerBook... I luv the new MacMame!

Rapha?�l Nabet had the PPC assembly cores compiling (for MacMESS) under Project Builder/Xcode. I reverted to Arekkusu's method for my current releases. I plan on moving back to PPC core as soon as I figure out how he did it.

all i have to say is THANK YOU. Mortal Kombat 3 is now again playable with the xcode compile. I havent been keeping up with mame recently, but i sure will be now. Thanks again.

Forking it just to have a "fast" build vs. a "slow" seems like a waste of energy and IMHO would really only confuse end-users. Ultimately I'd like to open my SVN server to the world and just have Alex and everyone else check in and build off of it.

That way, he could build "official" binaries off of it with XCode and I could easily come along later (or, gasp, earlier) and do a CodeWarrior release and we could share a consistently-progressing version numbering scheme even though we're building in two totally different environments.

Of course, if Alex wants to end up being point man for support alongside myself, that's his choice.

I was wrong about Rapha?�l's use of the PPC ASM cores. He didn't port them, he just used the Asgard source file to load the C core.

Sorry for the confusion.

BTW, I love this passage from MovingProjectsToXcode.pdf:
The PPC cores do all the heavy lifting with globals.

I took a look at these. Although it is true that both these games use the 68k, and the C core used in the Xcode build is slower than the asm core in the official build, the 68k emulation isn't the biggest bottleneck for these games.

For Afterburner, the bottlenecks are cpu_timeslice (it has a high cpu interleave?) and segaic16_sprites_outrun_draw (the video hardware.)

For Primal Rage, the bottlenecks are video_update_atarigt (the video hardware) and tms32031_execute (which doesn't have an asm core in the official build anyway.)

For comparison, on my hardware with fskp 0, 0.95 runs Afterburner II at around 50/60, and Primal Rage at around 36/60.

0.87b runs Afterburner II at 60/60 with some CPU left over, but Primal Rage is still around 36/60.

There is not a lot I can do to improve the speed of these in the Xcode build (with the available time I have.) You can still use 0.87b to get some speedup in games with CPUs that use asm cores (68k, 6502, Z80 etc) but it won't be faster in every case.


I'd also appreciate info on that.