Regression: NCAA 14 no longer loads into game (#8769)

[chrisyuska]

Quick summary

When loading into any game (exhibition or season), I'm now experiencing a freeze that never continues in NCAA 14 (only recently since last build downloaded a couple days ago).

Details

After loading up NCAA 14 (menus run fine), I experience a freeze when loading into the actual football game. Here's a screenshot of an example of the freeze:

1. Please provide exact build (or commit) information that introduced the regression you're reporting.

• Build 0.0.11-10800

2. Please attach TWO logs:

• One for the build with regression:

RPCS3 v0.0.11-10800-43172918 Alpha | HEAD | Firmware version: 4.86
AMD Ryzen 7 1800X Eight-Core Processor | 16 Threads | 31.93 GiB RAM | TSC: 3.600GHz | AVX+ | FMA3
S UPDATER: RPCS3 is up to date!
S SYS: Updates found at /dev_hdd0/game/BLUS31159/!

F {RSX [0x00ec6ac]} SIG: Thread terminated due to fatal error: Unexpected vkFormat 0x7E

• One for the build that works as expected:

I don't have a log of before it worked, but the log above seems to point in the right direction. The last working build was ~2 days ago.

6. Please provide your system configuration:

• OS: Windows 10 Pro
• CPU Ryzen 7 1800X
• GPU AMD RX 580
• Driver version AMD 20.4.2
• etc.

[chrisyuska]

My uneducated guess after briefly scanning through the previous commits since the last working build would be to suspect one of these commits (mainly because they touch vk):

d000d64
65ead08
f6c6c04
a5ac5a9
faaf28b

I have not tried to restore to an individual build among these to narrow down the culprit. Is there a suggested method for downgrading to an earlier build without trashing my installation directory? If not, is there a recommended way to downgrade and restore my home directory?

Thanks, and you're doing awesome work!

[AgentSmith630]

This is an example of the error message that pops up when closing the game after the crash

[AntLanz]

i was playing all day and i restarted my computer RPCS3 showed it had an update. So i updated it now i cant even get past the license screen before it crashes

[AntLanz]

[nfisha]

Experiencing the same problems. Appreciate whoever is working on this.

[Cutman685]

There was a change in V10790 that broke it. We will have to revert to 10781 to use NCAA again. Process is to download 10781 from the repo and unzip it into the folder where RPCS3 runs from and overwrite the existing files. save games will not be harmed.

[chrisyuska]

There was a change in V10790 that broke it. We will have to revert to 10781 to use NCAA again. Process is to download 10781 from the repo and unzip it into the folder where RPCS3 runs from and overwrite the existing files. save games will not be harmed.

Perfect, that rollback process worked for me. Thanks!

[nfisha]

I do not really know what you are talking about, could you maybe give a step by step process?

[chrisyuska]

I do not really know what you are talking about, could you maybe give a step by step process?

1. Go to previous builds page here: https://rpcs3.net/compatibility?b
2. Download the 10781 build for your system (click the Windows or Linux icon depending on your OS)
3. Extract the files from the downloaded .zip file into your RPCS3 installation folder (let it replace all duplicate files)

That should be all you need to do. Let me know if you have trouble, @nfisha .

[AntLanz]

i had to go back to 10779 in order for it to work

[AniLeo]

Removed console output flood, missing actual log file

[AniLeo]

On OpenGL it throws Unhandled GL format 0x8CAC
On Vulkan it throws Unexpected vkFormat 0x7E

[AniLeo]

Needs testing again with v0.0.11-10803 as soon as it's up

[Cutman685]

Tested with 10803. No Joy. There are a few odd messages in the logs but the killer is the vkFormat 0x7E. Full Log uploaded:
RPCS3.log. errors seem to start around 0:00:17

[kd-11]

Well, that was fast. There's that one game using 16-bit floating point depth buffers.

[kd-11]

Should be fixed by #8796. There is a weird "shadow" on the field but looks like it was always broken.

[lista187]

F {RSX [0x0000000]} SIG: Thread terminated due to fatal error: Unknown context dma 0x0