Regression: Sonic Unleashed (#9161)

[vanderleivieirainacio]

Good night.
I would like to report that the Sonic Unleashed game was working well but now, as soon as the game logo presentation videos go on, when you enter the game, simply the screen goes black, the game stops, it totally crashes, including the emulator.

RPCS3.log

[AniLeo]

Cannot reproduce.

[vanderleivieirainacio]

It doesn't really work here. My PC is:
Radeon RX 580 4GB Sapphiretech
AMD Ryzen 7 1700
Windows 10 x64 latest version
The SONIC UNLEASHED version is the American version by download (NPUB31204)
And it's still crashing, I did several tests.

[vanderleivieirainacio]

Unfortunately the only information I can give you is above: Game after the video of logo presentations doesn't even enter the "press start" screen, the game stops before and the screen is black.

[Asinin3]

You can try old builds. You can validate your game dump. You can let us know if it is a regression (working previously). If you're trying old builds try 111092 https://rpcs3.net/compatibility?b and the latest version.

[vanderleivieirainacio]

Thanks. I did the test in the old version RPCS3 11088 and the game Sonic Unleashed worked perfectly but the game Ninja Gaiden 3 Razor's Edge does not work in this old version, only in the current version from version 11140.

[vanderleivieirainacio]

It is a bug in the current version that does not let Sonic Unleashed work and as I said it only shows the presentation videos and before entering the "press start" screen everything is black and locks the emulator. I have already passed my hardware settings and unfortunately I would only know if they tested with the same settings as me, I think. I'm sorry but it is as much as I can answer about the problem.

[windwhirl94]

This one has happened to me recently, too, with BLES00425 (the disc version of Unleashed). Previous to this testing, I erased all caches and removed all custom configs for the games and RPCS3 itself, and then I made a new custom config for Unleashed.

System specs:
Windows 10 (mind, this is a Dev channel preview, build 20246.1, but for most things it can be treated as Windows 10 2004)
Ryzen 5 3600
Gigabyte Aorus RX 580, Radeon Adrenaline driver 20.10.1
RPCS3 0.0.12.11147

Edited to remove comments that were based on wrong assumptions and to avoid confusion for anyone that drops here.

[vanderleivieirainacio]

I also did as you said and erased all caches and custom settings and at first it worked but after I closed and opened the emulator it didn't work anymore and even after I cleared the cache and custom settings again it didn't work. The problem is as you described: the game crashes after the logo videos (SEGA, Hedgerog Engine, Havock) and the screen goes black and the emulator crashes.

[vanderleivieirainacio]

My hardware is all AMD like yours. It may be a problem only on AMD hardware maybe ...

[vanderleivieirainacio]

I tested it again and whenever I delete the game's cache folder and the "config.yml" file, the game works again, but after closing it and I opened the game again, it has the same problem, crashes after the logo videos (SEGA , Hedgehog Engine, Havok). I can assume that it has something to do with the cache and the config.yml file because the game only works if you delete both but it only works once, then you have to delete the folder and the config.yml file and start all over again.

[windwhirl94]

I retested with the configuration you had in your log. The emulator crashed after the Havok logo fades to black in the first run. The second run went fine, the third crashed again.
The fourth run went fine until at some point in Apotos Act 2 the emulator threw me an error about an incompatible driver (log attached).
RPCS3.log

Nothing changed between each run. Always using the same config.

I'm gonna poke at this thing a little more. Maybe there's a setting that's screwing with the game.

[vanderleivieirainacio]

Thank you very much for your attention!

[windwhirl94]

Well, running Unleashed with the emulator in "stock" settings. First run went fine until I got memory error
·F 0:05:13.640952 {RSX [0x00b0050]} VM: Access violation reading location 0xcf900000 (unmapped memory) [type=u0]
Still, I managed to play quite a bit of a level, so that seems to be a different issue and I will not post the log for that here.
Second run, with stock settings, crashed just like the runs I did with custom config. Log below.
RPCS3 - BLES00425 - Unknown Crash with default settings.log
It seems that this problem is sort of random? One run the game works fine, the next one doesn't.

[windwhirl94]

Now, I went back and tested quite a few previous builds, starting from 11088, while using OP' settings. The error we are discussing here could be reproduced only with build 0.0.12.11117 and probably latter ones. Build 11107 (which was the one right before 11117) worked fine.

Log for 11117 attached.
RPCS3.log

Build 11117 was born from #9161

[AniLeo]

Try with "Accurate SPU DMA" and see if the issue still happens (You need to enable it by editing config.yml)

[windwhirl94]

Try with "Accurate SPU DMA" and see if the issue still happens (You need to enable it by editing config.yml)

No changes. During the first test-run the game works fine, the next one it crashes before reaching the start screen, the third one runs fine, and the fourth fails again. Btw, I close the whole emulator between test runs, not just the game (clarifying, since I didn't say it before), so I shouldn't be keeping anything in memory between runs to justify this... constant switch between working and not-working.

Anyway, log down below.
RPCS3.log

[windwhirl94]

RPCS3.log
Tested with Linux (Fedora 33 KDE) on the latest build (11194). No changes, the emulator still crashes randomly.

[Straitjacket99]

This is happening to me too. On BLES00425 (European disc).

RPCS3.log

[JSKorbit]

This has been crashing when attempting to load the title screen for the last month or so on default settings, but as of trying the latest build(11312), it worked only when changing the PPU decoder from Recompiler(LLVM) to Interpreter(Fast). Other changes didnt seem to have any impact. In another note, the game is no longer covered in wireframe on my system, though there's a lot of misrendered motion blur.

Specs:
Using HDD version NPUB31204
Windows 10 19042.630 20H2
Ryzen 5 3600 w/ 3000mhz CL15 16GB
MSI 5600 XT Mech OC, Radeon driver 20.11.2
RPCS3 0.0.13.11312

[vanderleivieirainacio]

The loading error disappeared but the problem of the screen going black after the logos continues and happens with all SPU modes, both interpreters (in quick mode sometimes) and recompilers (ASMJIT, LLVM).

[AniLeo]

I am being serious, if no one else can reproduce how do you want this to get fixed, specially when there's no actual crash, only a deadlock. If there was a crash you could provide a stack trace and it could be possible to guess what's wrong from the code.

[Straitjacket99]

You could inject a RAM tracker into it and then track when it locks and stop it

[AniLeo]

coredump doesn't work with RPCS3 as is due to high amount of virtually reserved memory

[Straitjacket99]

You don't need to use coredump, use a RAM tracker like IDA

[AniLeo]

Seems easier to use gdb, don't see how IDA would be useful in this scenario, but any kind of captures would have to be done by someone who can reproduce this and you'd also have to find someone with IDA willing to debug them

But since this is a regression from 9161 I can guess it wouldn't help either way

[windwhirl94]

Please fix it I wanna play the game

For now, build 11107 is the last one that works OK with Unleashed, which I commented about earlier in the thread...

Now, I went back and tested quite a few previous builds, starting from 11088, while using OP' settings. The error we are discussing here could be reproduced only with build 0.0.12.11117 and probably latter ones. Build 11107 (which was the one right before 11117) worked fine.

Log for 11117 attached.
RPCS3.log

Build 11117 was born from #9161

You may find that build in the Builds History

[DavidPires]

Steps to reproduce:
-> delete the file patch_config.yml in the config folder
-> open RPCS3, go to Manage and then Game Patches
-> go into Sonic Unleashed and browse the patch list like this (or else it won't work):

-> apply and then save
-> run the game and there will be a guaranteed crash after the logos.

Solutions i found:
1 - empty the file manually or add a patch
2 - go to Settings and in the Advanced tab enable the option Silence All Logs.

[windwhirl94]

Steps to reproduce:
-> delete the file patch_config.yml in the config folder
-> open RPCS3, go to Manage and then Game Patches
-> go into Sonic Unleashed and browse the patch list like this (or else it won't work):

-> apply and then save
-> run the game and there will be a guaranteed crash after the logos.

Solutions i found:
1 - empty the file manually or add a patch
2 - go to Settings and in the Advanced tab enable the option Silence All Logs.

Well, that works for me.

[JSKorbit]

Steps to reproduce:
-> delete the file patch_config.yml in the config folder
-> open RPCS3, go to Manage and then Game Patches
-> go into Sonic Unleashed and browse the patch list like this (or else it won't work):

-> apply and then save
-> run the game and there will be a guaranteed crash after the logos.

Solutions i found:
1 - empty the file manually or add a patch
2 - go to Settings and in the Advanced tab enable the option Silence All Logs.

Can confirm that Silence All Logs fixes this crash.

[vanderleivieirainacio]

I tested here and actually scoring the Silence All Logs option causes the game to load and to play something but the game freezes and the emulator closes alone in certain parts when I'm playing and it happens in a few minutes of gameplay.

[Straitjacket99]

Steps to reproduce:
-> delete the file patch_config.yml in the config folder
-> open RPCS3, go to Manage and then Game Patches
-> go into Sonic Unleashed and browse the patch list like this (or else it won't work):

-> apply and then save
-> run the game and there will be a guaranteed crash after the logos.

Solutions i found:
1 - empty the file manually or add a patch
2 - go to Settings and in the Advanced tab enable the option Silence All Logs.

omg thanks so much bestie. that works!

[windwhirl94]

It seems this issue was fixed by #9593 (I tested a few builds, it seems that 11568 was the last one to exhibit this problem, while 11569 no longer has it), at least on my end.

Also, if closing this issue, check #9481, which seems like a duplicate of this one.

[elad335]

Linking #10357.