Compatibility Report

@AlbertoEberhardt I'm guessing that by city area you mean castletown plaza?

Have you kept playing the game recently? If so, have these crashes continued? Have you noticed if there are other factors involved? Like, for example, the season or time of day.

Yes is the Castle Town Plaza.

I recently (less than a week ago) switched the compatibility layer to Proton 10 Beta, made some testing and the the game didn't seem to crash, so i decided to keep playing normally, then after 2 or 3 in game days, the game crashed after i exited the Restaurant and walked a little toward the Castle entrance (where usually are two guards standing).

So to summarize: the crashes still happening, but aren't as easily to reproduce as they where on previous versions of Proton.

But while writing this, i discovered that if you put the Steam Deck to spleep with the game open the game will crash if you go to Castle Town Plaza after waking up the Steam Deck. Maybe this was the reason i had the crash that i said earlier (cannot remember if i have put the Steam Deck to spleep, maybe?).
And if you put the Steam Deck to sleep with the game open while you is in the Castle Town Plaza, after you wake the Steam Deck, the game and Steam will crash.

Today i found another way to crash the game: go to Castle Town Plaza and take a nap, then the screen will fade in and out to symbolize the time passing, and after you wake up and move the character a little the game will crash. If you take the nap from 3:00 PM to 6:00 PM (which is the time when the climate/light change) the game will crash before you are able to move the character.

@AlbertoEberhardt thank you for all the information, sadly I haven't had luck getting the game to crash on my end? Does the nap approach reliably crash the game for you? I've been playing on and off since yesterday trying to spend a lot of time entering and leaving the plaza and its buildings, and today the napping, but no luck so far.

Just to try and narrow things down, do you have decky or something that hooks into game mode installed? Do you play handheld or docked? Any configuration that you've changed in the Quick Access Menu?

The nap crash i was able to replicate, but after restating the Steam Deck i cannot replicate it.
But i think now i have one crash that still happening even after multiples system reboots: Go to Castle Town Plaza and put the Deck to spleep wait a little (4 or 5 minutes) then wake up the Deck, to me this makes the game crash (sometimes you will be able to walk a little but eventually it will crash), but if i put to spleep and wake up the Deck without waiting some minutes the game doesn't seems to crash, it only crash if you wait some minutes.

Yes! I have decky installed and the following plugins: AutoSuspend, Pause Games, SteamGridDB, PlayTime, CSS Loader and Game Sync (i don't have it configured to upload any file for this game, because it already have steam cloud support).

I play only in handheld mode.

The only setting that is changed in the quick access menu is the TDP Limit wich is set to 10 watts (globally not specific game configuration).

Here is the log of the crash with the method commented on the previous message (but this time it didn't crash first time so i put the Deck to spleep a second time, then waited more 5 minutes).

steam-1492730.zip

@AlbertoEberhardt still no luck, even with 10w tdp and suspending the system, 5 minutes, 1 hour, no luck. I haven't used decky so I don't know if it's too much trouble, but could you try uninstalling autosuspend and pause games? There's a chance there might be some conflict with them installed, leading to the crash.

Even after uninstalling the two plugins i was able to make the game crash. Will try to delete decky to see what happens.

I am still able to make the game crash without decky installed.

@AlbertoEberhardt Things are getting complicated. What I have is an oled, so I was hoping this was a rare lcd specific issue, but I asked someone to try and repro, and they couldn't on either steamos 3.7.15 or 3.8.0 (main).

While resetting the steam deck would be ideal to make sure there isn't some leftover configuration causing issues, I understand this is annoying.
For now, something we can try is that if you repro the issue again, go to the steam menu > settings > system > create report (it's at the bottom) save to desktop. Then you can go to desktop mode, and you'll find a text file with the information in your desktop, upload that here please.

I have tried several thinks: wifi off, bluetooh off, no sd card inserted, switched the language to English and did a Steam OS repair, an in all tests i was able to make the game crash with the sleep + waiting 5 minutes method, and it only happens in that specific location i tried in other locations and it didn't crash, must be something very very specific, i will send the report that you asked and then i will do a clean install of Steam OS since the repair already deleted my installed games and the per game settings, there still just a couple of thinks to backup.

systemreport-20251002220717.txt

Even after reinstalling Steam OS i am able to reproduce the crash.
System report with the crash on the clean installation ->

systemreport-20251002225213.txt

@AlbertoEberhardt this log is meant to be after getting the device back to stock, right? I see that decky is still being loaded, although strangely it seems to only load after the gpu resets, not before (though after that gpu reset, I see more kernel issues about hanged tasks).

Yes! The one with the message (and that is about 2mb in size) is the one after i reinstalled Steam Os with the option to Wipe and Install Steam OS.
Very strange indeed that Decky still being loaded, i am willing to do one more reinstall before i give up, but i would need a little help, before reinstall the system i want to format and clear/delete all disk partitions that Steam Os creates when is installed, but i don't how to do that on Steam OS , on Windows we can use the Disk Manager, but i didn't find anything similar on Steam OS.

@AlbertoEberhardt If you go to settings > system> factory reset (at the very bottom) it should wipe the deck back to how you originally received it. This will wipe any changes you made to the home folder in desktop mode as well, so you need to back up anything you don't want to lose.

Just did it, an unfortunately i am still able to make the game crash.

Here is the log ->

systemreport-20251003215550.txt

@AlbertoEberhardt Yeah, now decky isn't on your system anymore, so that can be written off the suspect list. I imagine the response to this will be no, but just to make sure, have you changed any of the following options in the quick access menu performance tab? : Disable Frame Limit, Allow Tearing, Half Rate Shading, Scaling Mode, Scaling Filter (the last two select the leftmost option by default).

If you haven't modified any of these, can you share your save file to make sure it doesn't somehow depend on progressing through the game for the issue to occur, hopefully the file saves are sharable.

To find it for this game you'll have to go to desktop mode, look for the steam folder in your home folder, and then go to ./steamapps/compatdata/1492730/pfx/drive_c/users/steamuser/AppData/LocalLow/BANDAI NAMCO Entertainment Inc_/DORAEMON STORY OF SEASONS FotGK/ and zip the folder called Saved, while you are here, and if the last time you played had the game crashing, grab Player.log as well.

I haven't changed any settings on the quick access menu all are defaults.

I can share the save files, but i did think the same about needing to progress more, so i tested with a new save file and the issue can be reproduced there as well.

Saved.zip

Player.log

Just to remember how i make the game crash:
1- Go to Castle Town Plaza (i usually stop by the bulletin board)
2- Put the Deck to Spleep (i press the power button)
3- Wait 5 minutes.
4- Wake up the Deck.
5- Now the game freezes and after some seconds it force close, sometimes it doesn't freeze right after you wake up the Deck, but if you try to walk around the Plaza a little bit it probably will freeze and crash.

@AlbertoEberhardt You have the dlc, right? while it shows the save slots with their name and day you were at, it doesn't let me load them complaining about downloadable files, I added the dlc but the nag didn't go away. So I started a new game and went to the plaza, but still no repro.

For reference, this is the graphics settings I'm using

Regarding your method for reproduction, you had also mentioned that you were able to crash it by napping to 18:00 while in the plaza, does this not make it crash reliably? But just to confirm, I tried to repro by suspending at the plaza for several minute to several hours at a time with no luck (though recently only 3 tries after 5-6 minutes).

The reason the game crashes appears to be that the gpu kernel driver crashes, but the why is the issue here.
There's a tool that should hopefully help get more information out of the gpu crash, but it requires going into desktop mode (or a SSH connection, if you know how to use that) and using the terminal to install and set things up.

The 2 two first saves requires all the dlcs, the 3 one shouldn't need any dlc because i disabled them to test, but also is just right in the beginning of the game (and also is the one that i still using to do all this tests).

I am using the same graphic settings as you are.

The nap method isn't 100% reliable. The suspend/resume is the only method that work 100% of the times, and 99% in the first attempt.

If you post a guide of how to setup the tool i can try it! I not familiar with SSH, i just remember that Dolphin created a folder with this name after i used it to copy some files from my Windows Pc via sftp.

@AlbertoEberhardt SSH is a way to connect and run commands from another device remotely, in this case I'd say it's just going to increase friction, so let's just run the commands from deck directly. Hopefully you have a keyboard you can connect to it.

Also, bear in mind that there's a possibility the game may not crash with these extra debugging options attached and there would not be an extra log to get as a result 😢.

1. Go to desktop mode
2. Open the terminal (it's called konsole)
3. Write the following command: passwd. With this, you'll be able to set up a password, which will be needed to run things as root. This won't affect game mode. Note that you won't be able to see any characters that you write, not even as asterisk, this is normal.
4. sudo steamos-devmode enable is the next command, this will ask for the password you just set. It'll ask you to confirm you want to enable it, for which you type y followed by enter to submit it.
5. sudo pacman -S umr which is the program that will help us dump information.
6. sudo chmod +s $(which umr) so that the video drivers can access it.
7. sudo chmod 777 /sys/kernel/debug; sudo chmod -R 777 /sys/kernel/debug/dri this will give UMR access to kernel interfaces it needs to do its work. Note that if you reboot your deck, this particular step has to be done again if you want to capture a gpu crash dump.
8. Follow the proton zip file I attached at the end, and unzip it in /home/deck/.steam/steam/compatibilitytools.d/, it should end up as /home/deck/.steam/steam/compatibilitytools.d/Proton - Experimental (no runtime). Note that files and folders that start with a dot are hidden by default, you'd have to configure dolphin to allow you to see them or use the ctrl + h that toggles hidden files on/off.
9. Now you can go back to game mode, go to the game's properties and make this the game's launch parameter RADV_DEBUG=hang %command%
10. Go to Compatibility in the game's properties, and set the proton version to Proton - Experimental (no runtime)

After all that, you can finally run the game and attempt to crash it again. It's very likely the game will run slower, and there's a chance it won't crash either, so brace yourself. After you wake up the deck so that it would normally make the game crash, you have to go to desktop mode and check your home folder, where you should find a folder called radv_dumps, zip it and upload it.

Proton - Experimental (no runtime).zip

I completely understand if this is too much of a hassle, and you don't want to go through with it. There's a possibility you might be able to avoid this crash by disabling dxvk for this title, so that you can at least hopefully not have to deal with it on your end. To do so you have to change the game's launch parameter which is found on steam on the game's properties, and make it PROTON_USE_WINED3D=1 %command%

If you decide to go through with all that, at least know that as long as you aren't using RADV_DEBUG=hang it shouldn't make a difference to your games, so at least you don't have to worry about the cleanup.

Thanks for the explained guide! Everything seems easy enough to handle. Will do it tonight when i have more time.

Tested very quickly with dxvk disabled and the game doesn't launch, i installed the directx from the Steam Common Redistributables and still not launching.
Here is the error screen

@AlbertoEberhardt

debug.sh
if you drag this to konsole it should simplify steps 3 through 8, you'll still have to set the password and confirm the things that ask for your confirmation, but you won't have to write the commands manually. If it gives you permisson denid when you try to run it, go to the file properties on dolphin and mark it as executable. This is a text file so you can use kate to open and read it.

Sorry about the wined3d suggestion, I should have checked if it would work with this title first.

Thanks for the script it made things go way faster! The game did freeze, then when usually it will close itself the screen did blink and Steam restarted (just Steam not Steam OS), don't know if this is expected, but anyway here's the log files.

radv_dumps_7415_2025.10.04_19.04.13.zip

@AlbertoEberhardt Asked a driver dev, and they explain it's going to be tough to fix a gpu hang without a local repro, but for now it seems like you can get a bit more information by also adding the following to the game's launch parameter: ACO_DEBUG=force-waitcnt.

ACO_DEBUG=force-waitcnt RADV_DEBUG=hang %command%

If you rebooted deck, remember you have to rerun step 7.

Here the is the log:

radv_dumps_11095_2025.10.06_13.32.25.zip

@AlbertoEberhardt I've opened a ticket with mesa https://gitlab.freedesktop.org/mesa/mesa/-/issues/14062 check it over in case I missed anything important.

If you have the chance and time, it could help to check with a more recent steamos just to see if the issue still happens with a newer kernel and mesa version.

• steam menu > settings > system > toggle developer mode (close to the top)
• Go back to settings and you'll find the developer menu at the bottom of the list
• Go around the middle of the developer menu and toggle "Show Advanced Update Channels"
• Go back to Settings > System, Change OS Update Channel to main
• Update, reboot, and try to reproduce the issue again

Your report cover everything that is worth noting.

Updated to the main channel and was able to reproduce the crash.
Will link the log, in case is needed.

radv_dumps_11365_2025.10.07_18.33.15.zip

@AlbertoEberhardt While I can't guarantee you won't see the issue anymore (as it couldn't be repro'd on my side) I think it's worth trying to use steamos main at this point due to changes done in the past few months.

• To unlock the option you need to go to settings>system and toggle developer mode on
• This will add an entry to the bottom of the setting list (under "store")
• Go to settings > developer and toggle "show advanced update channels" which will be roughly in the middle of that page
• Go back to settings > system and in OS update channel you will be able to select "main"