Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Madden 17 Freezing Issue (BLUS31589) #9049

Closed
munchnbeaver opened this issue Oct 8, 2020 · 19 comments
Closed

Madden 17 Freezing Issue (BLUS31589) #9049

munchnbeaver opened this issue Oct 8, 2020 · 19 comments
Assignees
Labels
Blocked This issue's cause is known, but another ticket is blocking further progress. Bug RSX

Comments

@munchnbeaver
Copy link

Quick summary

Upon loading into a match, the game freezes.

Error Code

F {PPU[0x1000018] Thread (FGGameCore) [0x01399ea8]} SIG: Thread terminated due to fatal error: Verification failed (0000000000000000):
(in file D:\a\1\s\rpcs3\Emu\RSX\VK\VKRenderTargets.h:602)

RPCS3.log

This is the screen it freezes at and and throws the error that I posted above.
Untitled

5. Please provide your system configuration:

  • Windows 10 x64
  • Ryzen 7 3700x
  • RTX 2070 Super
  • 456.71
@Jacoby1218
Copy link
Contributor

So some notes on this one

  • It only affects madden 15-17 (i only have 25 and 16 to test, but someone on the discord said this occurs on 15 as well)
  • If you start the Skills Trainer first, then try any of the other modes, it works

@munchnbeaver
Copy link
Author

munchnbeaver commented Oct 8, 2020

So some notes on this one

  • It only affects madden 15-17 (i only have 25 and 16 to test, but someone on the discord said this occurs on 15 as well)
  • If you start the Skills Trainer first, then try any of the other modes, it works

Even going to skills trainer, I still freeze. What settings are you using for madden 17?

Also, on the maddens that you have tested (12, 13, etc), what are the exact settings that you changed (from default), to get it working properly? I have issues still on the other maddens; I figured my settings are wrong.

@Jacoby1218
Copy link
Contributor

I thought the issues were fixed, but you may still need Write Color Buffers enabled. Games should work fine (with some minor texture issues on the sidelines)

@munchnbeaver
Copy link
Author

munchnbeaver commented Oct 9, 2020

I thought the issues were fixed, but you may still need Write Color Buffers enabled. Games should work fine (with some minor texture issues on the sidelines)

I cleared all Caches, and changed only 2 settings, the resolution to 300% and enabled Write Color Buffers, and left the rest at default. I'm getting crashes upon loading into skill trainer (this one first as you mentioned), not to mention the other game modes.

RPCS3.log

May I see what your settings are? Maybe I got something messed up. But like I said, everything is at default except those 2 settings I edited.

-Edit-
I'm getting this error:
(FGGameRender) [0x003d5fac]} SIG: Thread terminated due to fatal error: Verification failed (e=0x57) (0000000000000000):
(in file D:\a\1\s\rpcs3\Emu\RSX\VK\VKRenderTargets.h:602)

@Jacoby1218
Copy link
Contributor

I tested it today and it appears the workaround no longer works, I thought it did still.

@xddxd
Copy link
Contributor

xddxd commented Oct 9, 2020

Try the game with builds 10501 and 10502, if 10502 crashes and 10501 doesn't it's a duplicate of #8901

@munchnbeaver
Copy link
Author

I just tested build 10501 and I'm still crashing:

·W 0:03:19.382758 {RSX [0x01bee6c]} RSX: Cached object for address 0x303E0740 was found, but it does not match stored parameters (width=512 vs 1024; height=64 vs 32; depth=1 vs 1; mipmaps=0 vs 1)
·W 0:03:19.388161 {PPU[0x100000d] Thread (OnLoad) [0x00912690]} sys_semaphore: sys_semaphore_destroy(sem_id=0x96080c00)
·W 0:03:19.388363 {PPU[0x100000c] Thread (OnLoad) [0x00912690]} sys_semaphore: sys_semaphore_destroy(sem_id=0x96080a00)
·W 0:03:19.390286 {PPU[0x1000018] Thread (FGGameSim) [0x00912668]} sys_semaphore: sys_semaphore_create(sem_id=*0x30237070, attr=*0xd0153df0, initial_val=0, max_val=100000)
·W 0:03:19.390328 {PPU[0x1000018] Thread (FGGameSim) [0x00912668]} sys_semaphore: sys_semaphore_create(sem_id=*0x2775a998, attr=*0xd0153470, initial_val=0, max_val=100000)
·W 0:03:19.429044 {PPU[0x100000d] Thread (OnLoad) [0x00912690]} sys_semaphore: sys_semaphore_destroy(sem_id=0x96080e00)
·W 0:03:19.429894 {PPU[0x100000d] Thread (OnLoad) [0x00912690]} sys_semaphore: sys_semaphore_destroy(sem_id=0x96081400)
·W 0:03:19.430186 {PPU[0x1000019] Thread (FGGameRender) [0x003d814c]} RSX: Cache miss at address 0xC7388000. This is gonna hurt...
·W 0:03:19.431819 {PPU[0x1000019] Thread (FGGameRender) [0x003d814c]} RSX: Cache miss at address 0xC71F4400. This is gonna hurt...
·F 0:03:19.431826 {PPU[0x1000019] Thread (FGGameRender) [0x003d814c]} SIG: Thread terminated due to fatal error: Verification failed (e=0x57) (0000000000000000):
(in file d:\a\1\s\rpcs3\Emu\RSX\VK\VKRenderTargets.h:553)

RPCS3.log

@xddxd
Copy link
Contributor

xddxd commented Oct 14, 2020

From my testing the regression is most likely caused by #5675.

@Jacoby1218
Copy link
Contributor

This regression is much newer, as it started happening in june/july of this year.

@xddxd
Copy link
Contributor

xddxd commented Oct 15, 2020

10435, which I asked you to test on discord is a late May build and it was already broken?

@Jacoby1218
Copy link
Contributor

i'll try and find what broke it this weekend, then, since apparently, i don't know when some of these builds are from

@kd-11 kd-11 self-assigned this Oct 18, 2020
@kd-11 kd-11 added Bug In Progress This issue is actively being investigated at the moment. RSX labels Oct 18, 2020
@kd-11
Copy link
Contributor

kd-11 commented Oct 18, 2020

image
I cannot reproduce this issue. Provide definite step by step instructions on how to reproduce this crash effectively.

@munchnbeaver
Copy link
Author

munchnbeaver commented Oct 18, 2020

There's a couple of ways that you can try to reproduce the crash.

Start the game and go straight to practice mode (skipping skills trainer). On loading into practice it will crash.
If for some reason that doesn't crash and if practice mode works, exit practice mode and go to the play now mode. Start a match in play now. It should crash, and one more time if it does not, exit play now and go to connected franchise mode. start a new franchise using a created coach. Go to the first week, play the 1st week matchup, and upon loading into the match, it should crash.

95496448-ddf7f700-096e-11eb-82f7-5a3287922d11

-Edit-
So I know for a fact "Write Color Buffers" is what causes it to crash. I'm able to play the game without crashes with it disabled, however Write color buffers is needed in order to fix the field graphics issues as you see in the screenshot below

2

-Edit-
I created a little video to show you exactly what I'm doing for it to crash. I will also attach the log at the bottom of the video.
Recreating the crash
RPCS3.log

Hopefully that helps.

@kd-11
Copy link
Contributor

kd-11 commented Oct 19, 2020

I was able to reproduce. I thought this was a typical use after free issue but nope - the dynamic cast is failing on a valid object pointer. There is likely some kind of memory corruption going on that I need to look into.

@kd-11
Copy link
Contributor

kd-11 commented Oct 19, 2020

This turned out to be a bit more interesting than I anticipated. I figured out what's causing the crash, but I want to fix it properly, which requires more time. A proper fix should be ready in the next day or so. Hopefully other titles with WCB problems (flickering and corruption) are improved by the fix as well.

@kd-11
Copy link
Contributor

kd-11 commented Oct 20, 2020

Should be fixed by #9107. Retest with that PR build.

@kd-11 kd-11 removed the In Progress This issue is actively being investigated at the moment. label Oct 20, 2020
@kd-11 kd-11 added the Blocked This issue's cause is known, but another ticket is blocking further progress. label Apr 13, 2021
@munchnbeaver
Copy link
Author

It's been a while since I've been here, I just downloaded Madden 17 today and tried it, still experiencing the missing text when using RCB

@kd-11
Copy link
Contributor

kd-11 commented Jan 2, 2022

Does the crash still happen without RCB? I moved the code around a bit to improve synchronization since I last looked at this.
Missing text when RCB is enabled is known and I know why it happens, let's ignore that option for now.

@kd-11
Copy link
Contributor

kd-11 commented Jan 8, 2022

I'm unable to reproduce this. Closing.

PS. The RCB issue is known, the root cause was identified, but it is not a priority for now since WCB works ok. Fixing the RCB issue is actually easy, but performance suffers too greatly to be worth it. I will explore other options in future.

@kd-11 kd-11 closed this as completed Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocked This issue's cause is known, but another ticket is blocking further progress. Bug RSX
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants