protonscr

I Expect You To Die

protonopen appid 587430Game compatibility - Unofficial
ValveSoftware/Proton#5291 · opened 2021-11-06 by zaggynl · updated 2026-04-25 · 9 comments · github · game page · search this game
Zzaggynl 2021-11-06 github

Compatibility Report

  • Name of the game with compatibility issues: I Expect You To Die
  • Steam AppID of the game: 587430

System Information

I confirm:

  • [X] that I haven't found an existing compatibility report for this game.
  • [X] that I have checked whether there are updates for my system available.

steam-587430.log

Symptoms

Index Controllers keep buzzing at start of the game, when gripping them, seems to stop for a bit when switching to Steam VR menu.

During the tutorial you're asked to press the right controller trigger, upon pressing it is not registered.
There is a silenced handgun on the desk which can be picked up and fired using the trigger, this works as intended.

Reproduction

Install game, press A button to select Index as controller, skip introduction, try to follow tutorial, notice index button not registered in tutorial, fingers are moving, gun can be shot.

video demo: https://zaggy.nl/nextcloud/s/SroCRyXNMJgWaMn (I did not record audio)

Zzaggynl 2021-11-06 github

Same for beta:
image

This option seems to work, albeit that the controls are strange, touchpad for trigger and other things:
image

TThesola10 2022-02-20 github

It looks like the Index controller profiles and actions manifest are never registered into SteamVR for some reason.

Note in the examples below the absence of an "action_manifest_path" entry in IEYTD's manifest within steamapps.vrmanifest:

IEYTD (this game): 
                {
                        "app_key": "steam.app.587430",
                        "launch_type": "url",
                        "strings": {
                                "en_us": {
                                        "name": "I Expect You To Die"
                                }

                        }
,
                        "image_path": "https://steamcdn-a.akamaihd.net/steam/apps/587430/header.jpg",
                        "last_played_time": "1645022631",
                        "url": "steam://launch/587430/VR"
                }
IEYTD 2 (the sequel, for reference) 
                {
                        "app_key": "steam.app.1499120",
                        "launch_type": "url",
                        "strings": {
                                "en_us": {
                                        "name": "I Expect You To Die 2"
                                }

                        }
,
                        "image_path": "https://steamcdn-a.akamaihd.net/steam/apps/1499120/header.jpg",
                        "action_manifest_path": "/home/karim/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/I Expect You To Die 2/IEYTD2_Data/StreamingAssets/SteamVR/actions.json",
                        "last_played_time": "1639841511",
                        "url": "steam://launch/1499120/VR"
                }

This is reflected in the fact that the controls configuration page for IEYTD shows "legacy" profiles.

In addition, on my system at least, the controls configuration view takes a particularly long time to load for IEYTD in particular. I could not reproduce this with any other game or application on SteamVR, legacy or otherwise.

TThesola10 2022-02-22 github

Forcing the SteamVR manifest to use the actions manifest shipped with IEYTD (by setting steamapps.vrmanifest immutable) does not break the inputs that already worked, and does get the right input scheme to show up on the configuration page (which crashes in VR), but still doesn't allow me to pass the "trigger" step of the tutorial. That's puzzling...

Something in that particular version of Unity is causing input handling to behave very, very wrong?

Ccintoros 2024-10-27 github

This Game no longer starts with Proton 9.0-3 or Experimental, it just hangs until exited.
After switching back to Proton 8.0-5 it runs perfectly again(except the controller/tutorial problem).

Based on the logs steam-587430.log it seems OpenXR fails to initialize with newer proton versions for this game:

Error [GENERAL | xrCreateInstance | OpenXR-Loader] : LoaderInstance::CreateInstance chained CreateInstance call failed
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : xrCreateInstance failed

System Information:

  • GPU: AMD Radeon RX 6800 XT (radeonsi, navi21, LLVM 18.1.8, DRM 3.59, 6.11.5-arch1-1)
  • GPU DRIVER: 4.6 Mesa 24.2.5-arch1.1
  • KERNEL: 6.11.5-arch1-1
Aalasky17 2024-12-03 github

@cintoros Thank you for reporting this! This should be fixed with proton-experimental and the 9.0-4 RC candidate (available as a beta branch on Proton 9.0 currently). Both the controller issue and launch issue should be fixed :)

Ccintoros 2024-12-08 github

@alasky17 Thank you for the update/fix. I can confirm both Issues are fixed in 9.0-4 RC.
PS: 9.0-4 RC also works flawlessly for the other games i currently play.

Pprikhi 2026-02-09 github

This is failing for me on Proton 9, 10, Experimental & GE-10, with monado and both opencomposite & xrizer. All I get is a black screen on desktop, nothing loads into headset.

Seems like the instance is being created but immediately exits out.

steam-587430.log

steam-587430.log

xrizer.txt

opencomposite.log

Pprikhi 2026-02-15 github

Alright, sorry for the noise - my problem was needing to get a monado with 32-bit support - monado-multilib-git from the AUR has it but requires some manual fiddling of vrpaths & runtime.json files. Can vouch the game still works w/ Experimental & Proton 10(though oddly not luck w/ GE-Proton10-30).

I'm working on getting 32-bit builds integrated into envision for simpler handling of this: https://gitlab.com/gabmus/envision/-/merge_requests/137#note_2929198140

One oddity is needing is to specify PRESSURE_VESSEL_IMPORT_OPENXR_1_RUNTIMES=1 in the launch options. I don't have to do that for 64-bit games 🤔

ZZamundaaa 2026-04-25 github

The game reliably crashes for me on startup now. I tested a few Proton versions and it crashes with all of them, so it might be caused by SteamVR instead of Proton though

Proton versions