The Godfather Don's edition vulkan crash

[shadap32]

RPCS3.zip This is my log file.. i don't know how to solve, i have seen every topic but i can't find the solution I have seen some fixes but I don't know how to download them, if someone can explain me how to do it .. this is the error:SIG: Thread terminated due to fatal error: Verification failed

Windows 10 Home i5-9600k Gtx 970 16 gb of ram ddr4 3200mhz this is my configuration, please someone help me

[shadap32]

can someone help me? :D

[YuriNator557]

A label has been added to it, I presume it is an emulator bug, you will just have to wait for a fix

[shadap32]

ok thanks :)

[TerrorVan]

I have a different issue related to this:

I can get Don's Edition to boot and i've been playing it but it'll crash after about an hour with VK_ERROR_DEVICE_LOST, which is a known issue from January of this year related to specifically nVidia cards and Vulkan.

The best workaround (for at least my issue) is that it is less likely to crash if you keep it in a window rather than fullscreen but i've yet to test this out.

.

[RLTYProds]

I have a different issue related to this:

I can get Don's Edition to boot and i've been playing it but it'll crash after about an hour with VK_ERROR_DEVICE_LOST, which is a known issue from January of this year related to specifically nVidia cards and Vulkan.

The best workaround (for at least my issue) is that it is less likely to crash if you keep it in a window rather than fullscreen but i've yet to test this out.

.

Tested this. Will still crash. The only thing that really delayed it (note that I'm using the word delay, as I've found nothing that will stop the crashing) was setting the driver wake-up delay to 200 or 300. I've been able to play for around 2 to 3 hours at a time PROVIDED that you do not, under any circumstance, alt-tab or shift windows while playing. I've been found that doing so significantly increases your chance of that error. I've gathered this from over 4 hours of testing. No, I have no idea why that is the case.

[TerrorVan]

Tested this. Will still crash. The only thing that really delayed it (note that I'm using the word delay, as I've found nothing that will stop the crashing) was setting the driver wake-up delay to 200 or 300. I've been able to play for around 2 to 3 hours at a time PROVIDED that you do not, under any circumstance, alt-tab or shift windows while playing. I've been found that doing so significantly increases your chance of that error. I've gathered this from over 4 hours of testing. No, I have no idea why that is the case.

Yeah, since my post I tried a few different things and they all crashed within an hour. I don't specifically recall switching windows while I played but since I stream my gameplay I probably tabbed out for only a few moments to click on OBS or Discord or something.

Does it matter if I have Windows 10's magnification enabled? I use a large 1080p monitor that does okay 4K, enough that I have my desktop resolution as 4K with 150%-size icons and play my games at 1080p internally since 4K gameplay streamed at 1080p makes things microscopic.

[RLTYProds]

Tested this. Will still crash. The only thing that really delayed it (note that I'm using the word delay, as I've found nothing that will stop the crashing) was setting the driver wake-up delay to 200 or 300. I've been able to play for around 2 to 3 hours at a time PROVIDED that you do not, under any circumstance, alt-tab or shift windows while playing. I've been found that doing so significantly increases your chance of that error. I've gathered this from over 4 hours of testing. No, I have no idea why that is the case.

Yeah, since my post I tried a few different things and they all crashed within an hour. I don't specifically recall switching windows while I played but since I stream my gameplay I probably tabbed out for only a few moments to click on OBS or Discord or something.

Does it matter if I have Windows 10's magnification enabled? I use a large 1080p monitor that does okay 4K, enough that I have my desktop resolution as 4K with 150%-size icons and play my games at 1080p internally since 4K gameplay streamed at 1080p makes things microscopic.

Nope, not at all. I have standard Win10 display settings and it still happens. :( Anyways, if I do find out a better way, I'll be posting it here. Here's hoping they find a fix before that happens!

[TerrorVan]

I've been saving as frequently as possible by using phones in motels and clubs to take a driver back to a safehouse I own. For me, it seems like most times I've played it it'll freeze up at the 45 minute mark, curious to know if it's something like a memory leak.

[kd-11]

Is it possible to intentionally trigger this in seconds to a few minutes?

[RLTYProds]

To my knowledge, no. But setting the Driver Wake-up Delay to nothing (basically default settings) can make it happen within 10 to 15 minutes of gameplay. I say "can", since sometimes the crash could happen much later, but it never exceeds an hour in my experience.

[RLTYProds]

Update: Confirming that controller state is irrelevant. Played for around 2 hours. No crashes despite controller sleeping multiple times. No crash since I've never alt-tabbed or switched windows. Driver Wake-up Delay at 200.

Original: I just crashed with 200 Driver Wake-up Delay within 20 mins. Definitely not normal in my case, at least with those settings. Alt-tabbing and switching windows definitely agitates it. Not sure if related, but the crash coincided/is nearly timed with my controller going to sleep. Should be noted that crashes happen with the controller active, anyways.

The log: https://www.mediafire.com/file/onp6uyf68lidmyv/RPCS3.7z/file

TTY file is empty.

I changed the link from Google Drive to Mediafire. Google Drive was looping the log in my browser.

[TerrorVan]

@RLTYProds

I can tell you that it crashed at the 45 minute mark despite staying in the same window. I am forced to switch windows because I am also experiencing a bug between RPCS3 and my 8BitDo where I have to switch from the game window to the system window because I have to open/close the Pads menu after the game starts before it'll recognize my controller.

I have tried: Single-threaded vs Multithread Pad Handling, 1080p/enhanced settings, 720p/normal settings, RPCS3's defaults, the recommended settings for a multi-core Ryzen, the driver delay thing, etc.

[RLTYProds]

@TerrorVan Make a savestate on the main menu of the game to quickly circumvent the unrecognized controller bug with this game. Just remember to right-click the game and select "Boot with savestate" the next time you launch it. Then enter fullscreen only when you're loaded your save and controlling your character. That's what I do and it seems to have significantly delayed the crashes at times. Hope it works for you, too. I've also tried the other settings, and I think it's only the driver delay that's relevant for our case.

[TerrorVan]

@TerrorVan Make a savestate on the main menu of the game to quickly circumvent the unrecognized controller bug with this game. Just remember to right-click the game and select "Boot with savestate" the next time you launch it. Then enter fullscreen only when you're loaded your save and controlling your character. That's what I do and it seems to have significantly delayed the crashes at times. Hope it works for you, too. I've also tried the other settings, and I think it's only the driver delay that's relevant for our case.

I am embarassed to say that I thought of something like this but I just can't find the button/menu item to save a state.

Edit: I found out it's Ctrl + S by looking around the notes for the builds around when savestates were put in.

Edit II: I'll let you know how stable it is for me while starting via this method; just for any dev that passes by this topic though, this happens when I save a state:

`S SYS: Saved savestate! path='E:/Emulators/RPCS3//savestates/BLUS30023.SAVESTAT'

E SYS: Restart failed: Savestate data is corrupted or it's not an RPCS3 savestate`

It can't restart the savestate it just made, but it can also load the savestate just fine if I do it manually.

[ynhhoJ]

Happens to me after 1 minute of gameplay.

RPCS3.log

[ynhhoJ]

Maybe my last log fille on default settings. For me, doesn't metter if i switch or not window with RPCS game. It happens at random time. I can play 15 minutes and get crash or i can play 45 minutes and everything will be okay.

Crashed after 2 minutes of gameplay: RPCS3.log

UPD: One of way to get VK_ERROR_DEVICE_LOST every time is set very high resolution of game. Error happens after select save. 5 errors from 5 game runs.

Last log file: RPCS3.log

GPU settings: (all is on default settings, Resolution Scale is on maximum)

[kd-11]

We need vulkan debug traces for this one. If you can reliably trigger it then follow these steps (windows users):

1. Go to https://vulkan.lunarg.com/sdk/home#windows
2. Install the vulkan SDK. It's essentially just some libraries for developers.
3. Open the game config.yml. Edit the file to set "Debug Output" option to True from False. Alternatively, enable the hidden debug menu and enable the option from there.
4. Play the game until it crashes. You'll know its working because framerate will be terrible. This is why it is important to find a reliable way to trigger the crash.
5. Attach the log file. You may uninstall the SDK after that if you so wish.

[ynhhoJ]

I hope, i did everything correctly. Turned Debug Output to true, and there is my logs:

Played 35 minutes in total. The last session took 25+ minutes, set the scale 150% (1920x1080). The error never appeared. FPS is on 10 - 15 fps. RPCS3-long-play.log

Default settings, scale 800% (10240x5760). Triggered VK_ERROR_DEVICE_LOST error RPCS3-high-scale.log

P.S: I will try to play in the future until the VK_ERROR_DEVICE_LOST error appears in the game

[kd-11]

The setup is correct. Let me know if you can recreate the device lost error without memory thrashing. The high resolution crash is just because we run out of memory and start rendering into system memory and there are some unhandled paths in there. I'll fix that one but it won't fix the other crashes.

[ynhhoJ]

Get VK_ERROR_DEVICE_LOST after 45 minutes of playing.

Here is my log file: RPCS3-very-long.log

UPD: Unfortunately, I was never able to cause this error on purpose, since everything happens randomly, without special conditions. Quickly changing windows between RPCS and another program does not affect anything. Disabling the gamepad didn't cause error too.

As a result, the error appeared when I paused the game and moved away from the computer for a couple of minutes. In the past, without using Debug Output, more often than not the game would crash when loading new shaders.

Hope this helps!

[kd-11]

I looked over the log. There are no violations around the crash, it just comes out of nowhere. This usually points to a driver problem, but it could also be some condition that is not checked by the validation tools. Either way, I have nothing to work with for the moment unfortunately. Pascal has architectural problems with multi-queue setups, can you try disabling async texture streaming and multithreaded RSX to see if it helps?

[TerrorVan]

@kd-11 I can tell you that I tried all sorts of combinations of settings, and it still crashes with the above error eventually. The most stable was able to get the game was with help from another thread, where it was suggested to make a savestate past the initial controller check then avoid changing windows at all.

[ynhhoJ]

Pascal has architectural problems with multi-queue setups, can you try disabling async texture streaming and multithreaded RSX to see if it helps?

Is there any settings what i should try? Is better to use for Shader Mode: Legacy or Async (multi threaded)?

[kd-11]

Leave it at multithreaded unless you have an old quad core cpu.

[ynhhoJ]

After some long hours of tests with Debug Output i can't reproduce it. IDK what changed, but it never appears since last logs / reports :(

VK_ERROR_DEVICE_LOST can be caused by high fps?

[kd-11]

After some long hours of tests with Debug Output i can't reproduce it. IDK what changed, but it never appears since last logs / reports :(

VK_ERROR_DEVICE_LOST can be caused by high fps?

Yes, sometimes. But this usually means there is a problem with resource lifetimes. Unfortunately with closed source drivers I cannot do much unless the sdk catches a problem.

[ynhhoJ]

@kd-11 , got it!

RPCS3.log

[kd-11]

Someone managed to catch a crash with validation details in https://github.com/RPCS3/rpcs3/issues/12438 I'm investigating, hopefully this one also goes away.

[ynhhoJ]

I'm investigating, hopefully this one also goes away.

Good luck! Thank you for you job!

[kd-11]

Try with https://github.com/RPCS3/rpcs3/pull/12512

[ynhhoJ]

Played with #12512 fix since i see your comment (1.5 hours back) and everything is okay. It seem like is realy fixed, but i will play more

[ynhhoJ]

Got VK_ERROR_DEVICE_LOST after 2.5 hours (in total) using #12512 Played without Vulkan debug traces.

Log file: https://www.dropbox.com/s/3itimpyp92lhhq9/RPCS3-crash.log?dl=0

[ynhhoJ]

Here is log file with VK_ERROR_DEVICE_LOST error with last patch (#12512 ) + Vulkan debug output

RPCS3.zip

[kd-11]

Needs an update. I fixed the queue concurrency issue recently.

[ynhhoJ]

@kd-11 , with Vulkan debugging enabled or simple play test?

[kd-11]

Just a simple play test should suffice. If it crashes then you can enable debugging for the logs.

[Atarashi-Daten-Shi]

Apparently this is a issue for other games as well with this Vulkan Error. I'm wondering if it's something a Hot Fix for the Emulator can work.

[AniLeo]

Will be assumed fixed and closed if no one else has this issue

[ynhhoJ]

Will be assumed fixed and closed if no one else has this issue

Okay, i'll try to play in this weekend to test if problem is still exists

[ynhhoJ]

Bug still exists

[Jon-Todd]

Still encountering the same issue VK_ERROR_DEVICE_LOST with latest Nvidia drivers. Can provide more details if necessary

[kd-11]

Same situation as before, I need some crashes to happen with debug tracing enabled. You can try with the latest SDK version, maybe we'll catch something useful in the logs. Ftr, previously, we have found problems, but fixing them didn't solve all the crashes. There seems to be one bug still hanging around somewhere.

[SilviKofcourse]

still hannin, mane this shitty ass game is so beautiful and an ok remaster but i cant play it.

[kd-11]

Test with https://github.com/RPCS3/rpcs3/pull/13875

[TronBronson]

I am getting the crash as well. Could you tell me how to test with what you posted above? I made a github just to try to help with this so i don't know how to use the website very well but i am willing to do whatever and post the logs

EDIT: Nevermind haha I finally figured it out. Going to try to play again. Will post log if it crashes. Thank you for the ongoing help for so long!

[TronBronson]

Okay it crashed but the .LOG file is not in the folder anymore. It was there when i started because i checked. Would the RPCS3 text document be of any use to you?

[Darkhost1999]

Would the RPCS3 text document be of any use to you?

That most likely is the log. You just don't have file extensions enabled. You can upload it or just enable file extensions to confirm its the correct file

[TronBronson]

Ahhh okay you were right. I was looking at the file that said "RPCS3.LOG" even with extensions off. It kept disappearing after it crashed yet if i close the emulator manually it does not disappear. Anyway here is the log https://www.mediafire.com/file/jrw517zs6ww3fuv/RPCS3.log/file

[Atarashi-Daten-Shi]

Hey has anybody found any fixes yet or anything?

[ynhhoJ]

@Atarashi-Daten-Shi , i switched to AMD GPU and can't provide more test info from Vulkan :( . But, you can read old messages and contribute to fix this bug...