>Play California Speed on MAME
>The FPS is all over the place, sometimes hitting 60 and then dropping down to 15 seemingly randomly
I know the 3DFX arcade games were weak but can anybody who's actually played this game at the arcades tell me if the FPS was this shitty? It's really ruining the game for me and there's nothing I can do to fix it because internal overclocking just speeds the game up not improve the framerate, fuck I'd prefer if they just aimed for a solid 30fps instead of this unstable shit
>>3754913
it's like that because mame uses a very slow method for rendering 3d. get a faster cpu
the arcade game was fine
>>3754921
I'm not talking about MAME's performance, it always runs at 100 percent, I'm talking about the internal performance
picture related, the game seems to switch from 60/30/20/15fps depending on what scene is going on, the problem is that it seems to keep switching from 30 to 15 to 60 way too often making for an unstable and unpleasant image, i'm just asking if the arcade version exhibited such radical FPS changes
Buy the 64 cart. Its cheap and fun.
>>3754942
no it did not, like you have already been told
>>3755278
Well then that's just great, thanks MAME devs for getting the emulation wrong
Crusin USA looks like it uses the same engine and it is really jerky in the arcade
>>3754913
any good?
>>3754913
The N64 version is one of the shittiest games I love. Game is objectively low-budget dreck but it has so much content.
>>3754913
I think MAME devs just haven't put much effort into 3Dfx stuff. Both California Speed and San Francisco Rush are much jerkier than they are on the original hardware, Rush: The Rock stops working after the menus, and Rush 2049 (the superior arcade versions) doesn't even start.
>>3756498
The games use very different hardware though, might be easier to make a new engine instead of porting it to the different architecture.