Mon ouïe
Published
Not able to enter any race in VR
Menus work (including showing the cars being selected in the VR view, etc.), but as soon as I enter a race one of two things happen:
- the game crashes immediately, and SteamVR shortly after or
- the game freezes and, after two minutes, Unreal Engine crashes with a message stating "GameThread timed out waiting for RenderThread after 120.00 secs".
In the first case, dmesg
includes errors such as:
NVRM: Xid (PCI:0000:2d:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 0: 2D KIND Violation. Coordinates: (0x0, 0x0)
This issue persists with all Proton and SteamVR versions I was able to try. I found similar reports in a github issue, but that issue was fixed by Proton 5.13.
(This only happens in VR, game runs correctly when playing on a monitor)
Works out of the box, at least for non-VR users
Was not able to play in VR when choosing the OpenXR start option, whether using SteamVR or Monado
Can enter the menu in VR, but can't enter the main experience itself
While starting the game, a few errors stating "There is no Windows program configured to open this type" pop up. The game starts after closing them, but clicking on the buttons to start the main experience does nothing except make some noise.
Windows users have reported a similar issues on the steam forums: https://steamcommunity.com/app/1232310/discussions/0/2261312148327537299/
Played through the first two areas, the game runs perfectly smoothly on the highest settings at 1440p
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.dll
toAVProVideo.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.
Runs perfectly fine out of the box.
VR
VR on the Valve Index runs as expected (this feature is not supported by the native version of Distance).
Requires Proton Experimental's beta to run currently. Performance is comparable to the windows version with the same hardware.
Sometimes need to try to start the game multiple times before the game window actually shows up
Used a custom proton version as the game would otherwise immediately crash. Plays out perfectly with the indicated proton version.
Proton 5.9-GE-3-ST
Runs great, including in VR on a Valve Index (native version does not start in VR).
GPU crash after spending a few seconds in the menu
Issue coud be RDNA3 specific because I haven't seen other RDNA3 reports.
Shortly after starting the game, the system freezes and the screen flickers to black. After that, sometimes the game simply crashes, sometimes the entire screen stops updating (but other applications still seem to be running, e.g. sound is still playing from a music player in the background). Rebooting is required to restore the system to a usable state.
Does not start up. Appears to be related to the anti cheat system used by the game.
Sometimes crashes when exiting a race
The game still works on newer versions of Proton, but the last version to be able to support VR was Proton 4.11-10 (which can still be compiled from source), see https://github.com/ValveSoftware/Proton/issues/908
Great performance on high setttings. Ran into a black screen and 100% usage of one core during the very first run, but have not been able to reproduce this since.
Running through Proton because the native version does not support VR. Everything working fine on a Valve Index.
Performance issues make the game unplayable in VR.
With some versions of Proton, the game does not render properly on the VR headset (Valve Index), even though the correct view is shown in a window on the main monitor.
Runs out of the box on the steam deck
Some buttons are fairly small on the steam deck screen