Socom fireteam bravo 3 graphic error

[kyousuke77]

screenshot:https://imgur.com/a/ihOUiAj
this happen when changing non buffered rendering to buffered rendering
ppsspp android version:v1.7.5-473-g4d8f3c48a

[hrydgard]

OK, so that's the classic case of buffers not being cleared every frame sticking around. I guess you can workaround by making and reloading a save state? I'm not sure there's a good solution to this, but leaving open in case we think of something.

[kyousuke77]

iam not using save state and this issue only happen when i'm playing multiplayer ad-hoc
everything normal on singleplayer

[kyousuke77]

another screenshot
https://imgur.com/xttKeR0

[hrydgard]

Thanks. But if you avoid switching between buffered/unbuffered, everything is fine, right?

[unknownbrackets]

Wasn't this what that code to clear RAM on a clear was for? See #8994 and #8973 (comment). Basically, iirc, it does a clear in an FBO, then a while later after that FBO is destroyed, it uses the memory since it's "quite sure" that it's all zeros.

-[Unknown]

[kyousuke77]

graphic bug sometime occurs when i'm going to some place in the game
only happen in multiplayer.
Everything normal in singleplayer

[kyousuke77]

another screenshot
https://imgur.com/a/3iKqh3M

[hrydgard]

@kyousuke77 can you check the Game ID of your ISO? (hold-press on the icon, the letters and numbers after the name of the game). That last commit could have helped.

[kyousuke77]

UCUS98716

[hrydgard]

Thanks, that rules out one possible explanation.

[ghost]

I can repro this issue by changing buffered rendering to skip buffered rendering, not only that I can also repro this issue by loading a savestate hm. 🤔

• Loading from savestate

• Changing buffered to skip buffered

• GE Dump
SOCOM3.zip

[ghost]

@unknownbrackets removing this game id to ClearToRam and move to DisableReadBack compatibility fixes this issue on my phone 🤔

Edit: I forgot that disable slower effects is enable sorry 😅

[ghost]

This issue can be fixed by enabling Disable Slower Effects tried and tested both VK and OGL.

[ghost]

Ok I finally found a proper fix no need disable slower effects I put this game id to DisableFirstFrameReadback compat and it's totally fixed now.

[ghost]

DisableFirstFrameReadback OFF

Screenrecorder-2021-09-27-21-40-12-566.mp4

DisableFirstFrameReadback ON

Screenrecorder-2021-09-27-21-41-04-778.mp4

[ghost]

Yes adding this game to DisableFirstFrameReadback fixes this issue.

[ghost]

@hrydgard it's unsafe to add this game to DisableFirstFrameReadback? but it fixes this issue as I tested both on my android phones.

[ghost]

@hrydgard after you added this game to DisableFirstFrameReadback you can also remove this to ClearToRam because it doesn't help this game.

[hrydgard]

Done. Bumping further work here to Future.l

[StilMuz]

I can repro this issue by changing buffered rendering to skip buffered rendering, not only that I can also repro this issue by loading a savestate hm. 🤔

• Loading from savestate • Changing buffered to skip buffered • GE Dump SOCOM3.zip

I can probably solve this issue i just press select 2x and then it would not have the bug anymore

[ghost]

I can repro this issue by changing buffered rendering to skip buffered rendering, not only that I can also repro this issue by loading a savestate hm. 🤔
• Loading from savestate • Changing buffered to skip buffered • GE Dump SOCOM3.zip

I can probably solve this issue i just press select 2x and then it would not have the bug anymore

No need to that using ppsspp latest git build try it.

[StilMuz]

I can repro this issue by changing buffered rendering to skip buffered rendering, not only that I can also repro this issue by loading a savestate hm. 🤔
• Loading from savestate • Changing buffered to skip buffered • GE Dump SOCOM3.zip

I can probably solve this issue i just press select 2x and then it would not have the bug anymore

No need to that using ppsspp latest git build try it.

Thank you so much man the bug never appears again 😀

[ghost]

No need to that using ppsspp latest git build try it.

Thank you so much man the bug never appears again 😀

Yeah because of this
#11814 (comment)

[ghost]

Try it and see what happens.

[hrydgard]

Gotta be a duplicate of #16210. Closing as fixed.