(android) enable rendering duplicate frames causing lag on brave story new traveller.

[ghost]

Game or games this happens in

ULUS10279

What area of the game

What happens

The option render duplicate frames can make brave story new traveller lag instead of fast/smooth.

What should happen

Should make the game run fast/smooth.

GE frame capture

brave_story.ppdmp.zip

Platform

Android

Mobile phone model or graphics card

Redmi 9 Android 11 Helio G80

PPSSPP version affected

v1.11.3-1184 buildbot

Last working version

none

Graphics backend (3D API)

Vulkan

Checklist

• Test in the latest git build in case it's already fixed.
• Search for other reports of the same issue.
• Try resetting settings or older versions and include if the issue is related.
• Try changing graphics settings to determine if one causes the glitch (especially speed hacks or enhancements/replacements.)
• Include logs or screenshots of issue.

[ghost]

Same happening on OGL as well.

[anr2me]

rendering duplicate frames will gives extra burden isn't? so it's normal to get slower performance with extra burden, or was i mistaken?

[ghost]

Bomberman a 30fps game is no lag on rendering duplicate frames.

[unknownbrackets]

This shouldn't really be surprising. The setting makes us do more work and has downsides - it's not really unexpected or a bug that this can cause worse performance. Obviously, it depends on how much work the game is doing for rendering whether it will - so some games may be able to use this setting on weaker devices, and some may not.

How we normally do timing:

|-----1-----2-----3-----4-----5-----6------| <-- time showing on your watch
|123--------------------456----------------| <-- when the game actually executes

This makes it:

|-----1-----2-----3-----4-----5-----6------| <-- time showing on your watch
|-----12----------34----------56-----------| <-- when the game actually executes

This incurs a speed penalty, because if anything takes too long in the normal method, it looks like this:

|-----1-----2-----3-----4-----5-----6------| <-- time showing on your watch
|1222222223-------------45555555556--------| <-- when the game actually executes

See how it's still okay? That's not happening anymore:

|-----1-----2-----3-----4-----5-----6------| <-- time showing on your watch
|-----122222222---34----------5555555556---| <-- when the game actually executes

Now you're lagging behind on some frames. Isn't it a shame that we didn't get started on "5" early when there was all that time we sat around waiting, doing nothing? That's what this setting specifically requests doing.

But, the upside is your watch on your wrist matches the watch on the game, at least every frame. This can reduce microstutter.

-[Unknown]

[hrydgard]

It would be possible to implement frame duplication that only runs emulation every other frame, to maintain the same perceived performance - that's not what the option currently does, though, indeed.

[unknownbrackets]

Since this isn't a bug and the reporter closed their account, I'm going to close this.

-[Unknown]