RPCS3 / rpcs3

PS3 emulator/debugger
https://rpcs3.net/
GNU General Public License v2.0
15.21k stars 1.9k forks source link

[Regression] WWE '13 BLES01699 now constantly freezing and hangs in recent RPCS3 updates. #16108

Open Bobble80 opened 4 hours ago

Bobble80 commented 4 hours ago

Quick summary

There has been a performance regression in the WWE '12 BLUS30841 and WWE '13 BLES01699 games in recent updates to RPCS3. The games still boot, but will freeze or hang during initial loading or when they get to the title screen.

Details

I usually test WWE '13 every couple of months in RPCS3 to see if the performance is improving, and it does seem to be getting better as time goes on. A few months ago, and even beginning from July 2023 when I initially tested the game for the first time, I could always get ingame and play some matches. Maybe after 20 mins or so, the game might freeze and hang but it was playable for the most part.

Now I've been testing the game over the last week or two and there seems to be a big hit to the performance in recent updates. I don't know exactly when this happened or in what build of RPCS3, but now in the current builds the game will boot as normal but will freeze and hang either during initial loading or when it gets to the title screen. I've also tested the previous game in the series, WWE '12, and getting the same issue.

Build with regression

Unknown

Attach two log files

RPCS3.log.gz

Attach capture files for visual issues

No response

System configuration

No response

Other details

No response

AniLeo commented 4 hours ago

Need Information: Build that introduced the regression.

Bobble80 commented 4 hours ago

Need Information: Build that introduced the regression.

I've just tested it from build rpcs3-v0.0.32-16650-f948a802_win64 from June 30th and it seems to be running ok like before with no freezing or hangs.

I've also tried build rpcs3-v0.0.32-16729-a323e753_win64 from August 1st and that also goes ingame, but freezes a lot quicker into the match when it starts. So it might have been somewhere there that the performance regression was starting.

Do I have to check every build now from June 30th onwards to find out where the regression was?