PlayableShow Details
Unknown
WINEDLLOVERRIDES="winhttp=n,b" %command%
Runes didn't display properly, making it difficult to play.
Installing the mod from this site made the runes work.
WINEDLLOVERRIDES="winhttp=n,b" %command%
Limit Framerate
Most button prompts are displayed as white boxes
The game installs, launches and plays fine, however, when playing with the Steam Deck's built in controller the game will mostly show white boxes as controller glyphs, making it difficult to play the game. This can be easily fixed by installing the improved gamepad support mod by Chortos-2: https://gamebanana.com/mods/398211 Since the game renders as many frames as possible the playtime can be extended by limiting the framerate, esp. on the OLED Deck with the 90 Hz display.
Great game if you like visual novels and tactics-type RPG games. Is surprisingly long. Hope you all enjoy your time with the game!
WINEDLLOVERRIDES="winhttp=n,b" %command%
Control support with the Steam Deck has graphical issues with button prompts. Community controller layouts were not working for me and were not well configured for my liking. Followed the below Steam guide by Chortos-2 which installs mod and using modified launch option to fix controller/UI issues. Link to guide: https://steamcommunity.com/sharedfiles/filedetails/?id=2854301523 Link to mod (in case guide is down): https://gamebanana.com/mods/download/398211
See previous notes about fixing controller UI options.
From my experience you can launch from Steam without issues/tinkering but to fix the UI/controller issues present (unless patched in the future) I would recommend following the linked guide. Steps are easy to understand and execute.
The game runs correctly, there's just the missing label on the buttons but it can be fixed by the community layout "working w label".
White screen after cutscene bug can be fixed if you use the August 8 2022 patch or onwards
Using lutris with GE-Proton7-29 works perfect
Cap framerate to 30
Game crashes after the first cutscene if you don't use GE-Proton7-29, but if you use it you'll have no problems at all. You can even fix the button labels if you use the "working w labels" controller layout, but it's no really needed if you don't mind the white squares.
PROTON_USE_WINED3D %command%
The cutscene crash some users reported has been patched on the 8th of August.
Enabling PROTON_USE_WINED3D=1 was necessary to get past DX11 initialization issues, most likely due to the age of my system.
The game ran at 25-30 FPS, GPU bound (it's a laptop GPU 4 generations below minimum requirements...). Definitely playable, it's a Visual Novel. ;)
button legend was missing icons
The community template was needed otherwise, the analogs did not work.
When the prologue video plays had to progress on Windows to an auto save after it
Great game just the stupid video bug
Guaranteed crash after second cutscene.
Guaranteed crash after second cutscene
Compiling proton experimental with this patch fixes the hang after the cutscene. Let's hope it will be included into proton soon or the game is fixed as to not rely on it.
Just use a save that bypasses the beginning cutscene, watch the cutscene if you want on Youtube and you can enjoy the game flawlessly.
triggers and touchpad click don't seem to work regardless of assignment/binding??
locks up after opening cutscenes
icons for controllers don't display correctly and for some reason, triggers and touchpad click don't seem to be mappable. if you can watch/skip the initial cutscene on a windows PC and another slightly on later for the title roll (seems to be an issue with animated cutscenes in general--probably there will be others further in the game), typical gameplay is otherwise without issue. definitely hold off if playing exclusively on deck/linux
Freezes after the first cutscene plays (after the tutorial battle). Tested on Vanilla, Proton Experimental, and Proton GE.
Some gamepad/controller icons are showing as blank white boxes
100% rate of freezing after the first cutscene (the one after the tutorial battle)
100% rate of freezing after the first cutscene (the one after the tutorial battle)
Game is completely unplayable except for the tutorial battle. Do not play it in this state until fixes are rolled out.
The button UI doesn't work, replaced by white squares
Trigger buttons do not work, used a community input setting that has the PC key bindings to L4/R4
Crashes after first cutscene
To get pasted the first cutscene, right click game in Steam, browse local files, navigate to \DigimonSurvive_Data\Plugins\x86_64 and delete AVPROVideo.dll, after that I have been able to play the game flawlessly
Some workarounds are required to bypass common issues:
- Using a steam community input mapping so that controller buttons work and are shown properly
- Rename
Digimon\ Survive/DigimonSurvive_Data/Plugins/x86_64/AVProVideo.dlltoAVProVideo.dll.bak. This disables the anime cutscenes (I believe there are only two of those: one right after the combat tutorial at the very start, and one an hour or so into the prologue, before receivenge the "The Adventure Begins" achievement), but bypasses the game freezing right after they've played.
Couldn't access the game again after alt+tabbing, had to restart. This is fixed if switched to borderless window in the settings.
Videos will only play using Proton-GE.
Game will crash after playing some videos.
There's a workaround described here: https://github.com/ValveSoftware/Proton/issues/6041#issuecomment-1199474786
deleting/renaming the video files in the steamapps/compatdata/871980/pfx/drive_c/users/steamuser/AppData/LocalLow/©BANDAI NAMCO Entertainment Inc_/DIGIMON SURVIVE/Movie/ directory while they are playing will prevent crashes. Less than convinient having to this manually but at least you get to play without any other major issues.
Tinkering is needed to be able to play the game.
Only small issue is that the game is not displaying the button layout in its UI. For some reason it just shows blank squares for everything but the dpad, joystick, and triggers. Other than that, runs perfectly.
While the intro scene and tutorial works, it freezes after the next anime cutscene even if you try to skip.
Guaranteed crash after the first animated cutscene.
Currently the only way to bypass this crash is to play past the cutscene on a PC, save the game, then continue playing on the steam deck. Trying to skip the cutscene on the steam deck also guarantees a crash.
gamemoderun %command%
Crashes after opening cutscene. Behavior seems present for Windows users as well.
The game doesn't show most controller icons in game and instead shows white squares in their place otherwise most cotrols work fine until I got to the first Explore ection where you press Left trigger to access the map. The game does not recognize that input.
Game hangs every time after first animated cutscene even if skipped. Should be noted that this problem is affectng a lot of people on windows too so probably not a proton issue.
See peciously noted issues.
Control icons do not show up. White squares in their place.
Video scenes to not play.
Plays fine until you hit the first video scene and then the game freezes up BEFORE playing it. On PC, there's a known bug where it freezes after, but on Deck it won't even play the video at all.
Difficult to play at the moment due to the animated cutscene causing the game to freeze, seems impossible to pass unless you get a save.
Some controller icons not displaying properly on the UI.
Game freezes/crashes after a prologue animated cutscene with both default steam settings and Proton GE.
Controller buttons are not rendered in the menus or within text
Crashes after cutscenes
Controller buttons not rendered in menus or text
When it works, it looks and runs well. The controller problem is annoying but can be worked around. Unfortunately it's just not stable enough to recommend at launch.
