Home Page Forums MAME Non-Windows MAME Support Outrun slow since 0.131u2?

I wonder if sigsetjmp shouldn't be also used for Linux, just in case

Almost certainly could be coded better. Not necessarily a quick / low invasive change to do so. Least disruptive would be to pass a bit more data around and add some tests so the flow unwinds normally.

Got to love programmers that use exceptions as logical conditions (I'm referring to the games there, not the MAME team

sigsetjmp() is a POSIX standard. setjmp() is ISO C. So setjmp() provides for greater compatibility, but I would argue that sigsetjmp() should preferably be used in any POSIX compliant system.

(Actually, I would argue to take all these methods out the back and humanely dispose of them, but we're veering off subject)

Thanks scarlet for your great work!

Yeah. The problem is that OS X doesn't #define any of the standard "I am POSIX" signifiers as far as I could see. I could force one in sdl.mak I guess.

That's because it isn't (quite) POSIX unless you #define _POSIX_C_SOURCE or something.

thank you for investigating this and helping out.

Wow! Finally with 0.134u1 OutRun is working fine on my iMac 3.06 GHz/ATI 4850!! Same with Super Hang On!

I only wonder why Space Harrier notes at startup that something is missing but the game works without problems...

Well, our team of trained psychics are on vacation so what does it say is missing?

(And nobody answer for him, I want to know what his screen says is missing).

"One or more ROMs/CHDs for this game are incorrect". I do not know which. ClearMAMEPro does not find any problem so it's hard to say!?