(ULUS-10239) Hot Wheels - Ultimate Racing (Game runs at half speed)

[piau9000]

What happens?

The game have some speed problems. It runs at 50% but the in game FPS is at 60. It seems that the max FPS of the game is 120 but, since PPSSPP limit it to 60, it runs at half speed.
It's not a problem of weak computer, as the game runs at above 500% when you throttle the fps. It also seems to be related to vsync, because when you disable it it runs at 93% (113 FPS). Still not 100%.
By using older versions of PPSSPP that still had the "Prevent FPS from exceeding 60" option, you can make it run at 100%. It may be something related to it too.

What should happen?

The speed of the game is wrong on the emulator so it should work at full 100% speed.

What hardware, operating system, and PPSSPP version? On desktop, GPU matters for graphical issues.

Lastest build of PPSSPP used (1.9.3-251). Windows 7 64 bit, GTX 750 ti.

[LunaMoo]

The option still exists, it was just turned into compat.ini hack and enforced on games where it helps.

[piau9000]

Thanks for the help. I added the following to [ForceMax60FPS] in compat.ini

Hot Wheels: Ultimate Racing
ULUS10239 = true
ULES00828 = true

This should cover the two versions of the game.

[unknownbrackets]

If the game is trying to flip more than 60 times per second, and we let it (all the way to the host), that's a bug. Vsync should not have any impact: that's a bug.

It may be that ForceMax60FPS was papering around a separate bug in this game. It may possibly run better with the actual bug fixed.

Does anyone know what FPS this renders at on real PSPs? Note: a PSP screen can only display 60 different frames per second, but it is possible for games to (wastefully) render frames that the display hardware never shows. It'd help to know if that's actually supposed to be happening here, because it's pretty rare in PSP games.

-[Unknown]

[hrydgard]

I checked in the workaround, but am keeping this issue open of course, since there must be some kind of emulation bug indeed.

[unknownbrackets]

So we're either not interacting properly with its frame limiter, or we're not spending enough cycles.

I have started to consider - potentially - analyzing the GPU timing and trying to better model it in the software renderer. It should have all the information needed to do so and it might really be good for compatibility. That said, it'd mean a timing impact to using the software renderer, which wouldn't be great...

-[Unknown]