Home Page Forums Archives MacMAME MacMAME 0.87

What are you asking? If it'll ever be possible or if I'll fix the crashing bug? Yes to both. Just be patient.

It is possible to play Bubble Bobble 2 using MacMAME 0.84 Xcode, though.

OK, if the stack backtrace for the crash doesn't end with mac_joy_is_pressed(), then I'm interested in hearing about crashes. Otherwise, not so much.

Yes, because it uses the slower C version of the 68020 core.

Can you give me a little more info please? I tried hitting F4 just now in a variety of games, and MacMAME didn't crash. This leads me to believe it's specific to a certain subsection of games, but with 5000 to choose from, it could be a while before I discover which ones.

Happens in the CW 0.87 release just going down the list-- '88 Games, 005, 1943...

Doesn't happen in the 0.87 Xcode build I made, though. Compiler bug?


Of course it's highly desirable to keep the assembly core, but maybe running slowly is better than not working? :p

And (now that I know to put the CHD at the root of the disk) on my 1.25GHz PowerBook I get 61%, 36fps in the CW 0.87 release and 68%, 41fps in my Xcode 0.87 build. This is with fskp 0 during the first weddingr animated sequence with music after startup.

Now that both builds are using usleep() we can do some comparisons between the speed of the asm and C cores (PSX core is C in both cases, right?)

Why does usleep matter? I'm able to benchmark the C vs. PPC cores regardless. Yes, the PSX is C for both builds.

It seems likely - it doesn't happen in my CW debug builds.

Most games run at full fps on my hardware; without usleep MAME would always sample at 99% in Shark so it was hard to compare. Now it's a bit more even... I'll look at some games with asm cores.