search

ValveSoftware / SteamVR-for-Linux

Issue tracker for the Linux port of SteamVR
919 stars 45 forks source link

[BUG] Game/Vrcompositor crash with Assetto Corsa Competizione VR (UE4, Nvidia) #397

Closed jp7677 closed 3 years ago

jp7677 commented 3 years ago

Describe the bug Running Assetto Corsa Competizione VR via current stable Proton (5.0-9) and a vrclient with this PR applied https://github.com/ValveSoftware/Proton/pull/4163 let the game start, but at some point in the first few minutes SteamVR (vrcompositor) crashes. Very likely the game crashes first and vrcompositor crashing is a follow up. I'm seeing these lines in dmesg:

[11897.915514] NVRM: Xid (PCI:0000:02:00): 13, pid=617873408, Graphics Exception: Class 0x0 Subchannel 0x0 Mismatch
[11897.915517] NVRM: Xid (PCI:0000:02:00): 13, pid=617873408, Graphics Exception: ESR 0x4041b0=0x80000
[11897.915519] NVRM: Xid (PCI:0000:02:00): 13, pid=617873408, Graphics Exception: ESR 0x404000=0x80000002
[11897.915828] NVRM: Xid (PCI:0000:02:00): 13, pid=57164, Graphics Exception: ChID 0064, Class 0000c197, Offset 00000f80, Data 00000000

The game runs perfectly with the same setup without VR.

To Reproduce Steps to reproduce the behavior:

  1. Install a Proton version that includes a Proton vrclient with https://github.com/ValveSoftware/Proton/pull/4163 applied. Here is such a version: https://github.com/ValveSoftware/Proton/issues/1420#issuecomment-705195039 (Here is a link https://github.com/ValveSoftware/Proton#install-proton-locally that describes how to set up up a custom Proton version).
  2. Enter the game Assetto Corsa Competizione from the SteamVR lobby,
  3. Enter the actual game (Main Menu -> Single Race -> Start Session)
  4. SteamVR crashes during this process, sometimes in the menu, sometimes when entering gameplay, and shows a notification that it wants to restart. Steam console output shows that a crash dump has been uploaded. dmesg shows above output.

Expected behavior SteamVR should not crash.

System Information (please complete the following information):

Additional context See also https://github.com/ValveSoftware/Proton/issues/1420#issuecomment-706139550 and further comments. According to https://github.com/ValveSoftware/Proton/issues/1420#issuecomment-674580748 the same setup works fine when using AMD/Mesa instead of an Nvidia card. According to https://github.com/ValveSoftware/Proton/issues/1420#issuecomment-706723540 a very similar issue can be observed in Project Cars 2. Both games use Unreal Engine 4.

Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.

gotzl commented 3 years ago

I get a crash as well (GTX1060 + Index). For me, the sequence is like this

Is this about the same what you observe? To me, it looks like the vrcompositor crash is more a consequence of the UE crash. The actual cause seems to be the Xid error which seems to result in the GPU not spitting out frames anymore....

Here the gdb bt of the vrcompositor coredump and the AC2.log.

System Information

jp7677 commented 3 years ago

Thanks for the confirmation, yes this seems to be the same issue. Your conclusion regarding which process crashes first is likely correct.

jp7677 commented 3 years ago

Above behavior is still the same with Proton 5.13-1 (it still needs the vrclient PR applied manually), Nvidia driver 455.28 and SteamVR 15.4 Beta.

jp7677 commented 3 years ago

Hi @gotzl Could you please give Proton 5.13-2 RC a try? See https://github.com/ValveSoftware/Proton/issues/4360 I have only tested for a short time, but this seemed to have fixed this issue here for me. Would be cool if you could confirm this.

Edit I'm also running Nvidia 455.38 now, may be updating to this version had some effect too.

gotzl commented 3 years ago

Thanks for pinging me! It works for me too! Really great :) I'm on 455.28 ... I've also tested only for short time. Will give it some more time later, but the GTX1060 is probably just not enough to get playable FPS ... Still, very good progress!

jp7677 commented 3 years ago

Thanks for the confirmation and for providing your driver version. I guess then that indeed the Proton RC fixed this. Very cool progress indeed and my GTX is also way to slow, I’m keeping an eye now on the GPU market to see how the new AMD and Nvidia generations unfold :)

Let’s keep this issue open for a short while, though I guess we can close this once Proton 5.13-2 is final.

jp7677 commented 3 years ago

This issue is resolved with Proton 5.13-2.