[Regression] MotorStorm Pacific Rift Video playback is broken (#16352)

[SzThBalazs]

Quick summary

Video playback jumps backwards

Details

No response

Build with regression

v0.0.34-17195-30ca2370

Attach two log files

RPCS3.log //this is the broken versions log
RPCS3.log

//ive used default config for these logs, but this issue happens with my custom config too

Attach capture files for visual issues

BCES00129_20250125121046_capture.rrc.gz
BCES00129_20250125121101_capture.rrc.gz

System configuration

op: Win 11 Home
cpu: AMD Ryzen 7 7745HX
gpu: Nvidia Geforce RTX 4070 laptop
gpu driver v.: 566.36 (game ready driver)

Other details

No response

[AniLeo]

Regressed by #16352, surprisingly this is for @kd-11

[kd-11]

@SzThBalazs So disabling asynchronous memory manager option in advanced tab fixes the issue?

[SzThBalazs]

Yes, disabling it fixes the issue. Thx!

[kd-11]

Let's keep this open, I want to check why it is not compatible with the setting.

[digant73]

the stuttering on the intro video (with Disable Asynchronous Memory Manager disabled on Debug tab) is not present if the 60 FPS patch is applied or VBlank Frequency is set to 120 (of course in that case the gameplay is too fast)

[digant73]

@kd-11 the issue is not present if line 48 in MM.cpp is commented out:

// if (prot == utils::protection::rw || prot == utils::protection::wx)

...but of course that means mm_defer_mprotect_internal is never invoked

EDIT:
if I move the loop for flushing if any overlap is detected (line 51 in MM.cpp) before (outside) the check on protection flag (line 48) then the issue is not present. It also fixes the issue on Split Second (#16786)

[kd-11]

I'm unable to reproduce this issue. All I did was create default settings and add WCB for the exposure issue then boot the game and wait for the video to start (no inputs).
Do I need any special settings or actions? I think this is the one issue that I could use to investigate the async MM thing due to ease of reproducibility if I can figure out how the bug happens.

[digant73]

I'm unable to reproduce this issue. All I did was create default settings and add WCB for the exposure issue then boot the game and wait for the video to start (no inputs). Do I need any special settings or actions? I think this is the one issue that I could use to investigate the async MM thing due to ease of reproducibility if I can figure out how the bug happens.

the settings are ok. In my case I see the stuttering in the intro video and in the main menu. This is also the only game having the issue only with LLVM but works fine using ASMJIT etc.. All other reported games have the issue even using ASMJIT.