Whitelist Request

Can you please do this, the difference is really between almost unusable as it is now and without issues after setting it to the latest proton version.

Seems to still work perfectly for me with latest SteamVR beta and Proton 6.3-6

For many months now this game hasn't worked for me (frustratingly it worked once only since getting a VR headset and never again), and protondb shows similar reports. It starts loading, with big gaps between frames (which thanks to nvidia reprojection are now visible), but during loading it just quits. I've tried every version of proton available and reset the prefix etc, without success. Should I open a new issue?

Hello @amalon, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

Sorry for delay getting around to this! Been trying a few things again, including using steam-native (fixes steamvr settings not coming up) but google earth vr still doesn't run. Here's a proton log file: steam-348250.log. Based on me tailing the logfile while it loads, the crash appears to happen around line 750:

5330.208:0114:0128:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x1c7fe2c,4,(nil))

System information here

Today when I tried, proton experimental (with steamvr beta 1.22.9) can now start google earth VR!! just one rather major problem:

This is with preview set to both eyes. It appears to be rendering only the left half of each eye, so everything is distorted and moves too fast. Otherwise though its managing a steady frame rate and steamvr window reports a render time of around 8ms

Very exciting. It now works for me with SteamVR beta 1.22.11 with proton experimental (I wonder if due to "Fix for visual distortion with GL applications (e.g. X-Plane 11) introduced earlier in this beta cycle v1.22." in 1.22.10)

Crashes for me with all of the offered proton versions (including proton), SteamVR 1.22.12. Nvidia 510.68.02, Linux 5.18.0, NixOS 22.05. Shows the window on the desktop for a bit before suddenly disappearing without warning.

Edit: nice thing about NixOS is I could easily downgrade and retest on SteamVR 1.22.12, Nvidia 470.86, Linux 5.10.115. Earth VR works fine there on Proton Experimental.

Edit2: Spoke too soon, it crashed in proton experimental while I was flying around, and then refused to restart, showing the same behaviour as with the previous version.

Got some good time in VR today with various things working better than in the past. Things work pretty well in terms of startup for Google Earth VR, but it does still reliably crash after a few minutes unfortunately. I had to use proton experimental, and additionally, if I start Google Earth VR immediately after SteamVR, it works, but if time elapses, Google Earth VR stops on startup (no segfault in dmesg). I'm unable to re-enter Google Earth VR unless I restart SteamVR after a crash.

[ 2194.069052] VKRenderThread[21542]: segfault at 7fe49a486918 ip 00007f5052e64718 sp 00007f502a7fed90 error 6 in vrclient.so[7f5052c00000+6f0000]
[ 2194.069067] Code: 64 4b 00 e8 5a 86 e2 ff 48 8b 98 18 00 00 00 49 8d 44 24 20 48 89 43 10 49 8b 54 24 20 66 0f ef c0 49 8b 44 24 18 48 83 e2 fe <48> 89 42 f8 49 8b 54 24 20 48 83 e0 fe 48 89 10 31 c0 41 0f 11 44
[ 2398.195257] VKRenderThread[25075]: segfault at 7fefd849a918 ip 00007fdccd864718 sp 00007fdcaddfed90 error 6 in vrclient.so[7fdccd600000+6f0000]
[ 2398.195267] Code: 64 4b 00 e8 5a 86 e2 ff 48 8b 98 18 00 00 00 49 8d 44 24 20 48 89 43 10 49 8b 54 24 20 66 0f ef c0 49 8b 44 24 18 48 83 e2 fe <48> 89 42 f8 49 8b 54 24 20 48 83 e0 fe 48 89 10 31 c0 41 0f 11 44
[ 2452.792501] VKRenderThread[26891]: segfault at 7fefd849a918 ip 00007fd911464718 sp 00007fd8f17fed90 error 6 in vrclient.so[7fd911200000+6f0000]
[ 2452.792534] Code: 64 4b 00 e8 5a 86 e2 ff 48 8b 98 18 00 00 00 49 8d 44 24 20 48 89 43 10 49 8b 54 24 20 66 0f ef c0 49 8b 44 24 18 48 83 e2 fe <48> 89 42 f8 49 8b 54 24 20 48 83 e0 fe 48 89 10 31 c0 41 0f 11 44
[ 2511.978104] VKRenderThread[28100]: segfault at 7fefd849a918 ip 00007f817b264718 sp 00007f815b7fed90 error 6 in vrclient.so[7f817b000000+6f0000]
[ 2511.978127] Code: 64 4b 00 e8 5a 86 e2 ff 48 8b 98 18 00 00 00 49 8d 44 24 20 48 89 43 10 49 8b 54 24 20 66 0f ef c0 49 8b 44 24 18 48 83 e2 fe <48> 89 42 f8 49 8b 54 24 20 48 83 e0 fe 48 89 10 31 c0 41 0f 11 44
[ 2759.128937] VKRenderThread[30842]: segfault at 7f8998680918 ip 00007f9be1864718 sp 00007f9bc1dfed90 error 6 in vrclient.so[7f9be1600000+6f0000]
[ 2759.128945] Code: 64 4b 00 e8 5a 86 e2 ff 48 8b 98 18 00 00 00 49 8d 44 24 20 48 89 43 10 49 8b 54 24 20 66 0f ef c0 49 8b 44 24 18 48 83 e2 fe <48> 89 42 f8 49 8b 54 24 20 48 83 e0 fe 48 89 10 31 c0 41 0f 11 44

Looks to be the same segfault as experienced in Torn (https://github.com/ValveSoftware/Proton/issues/5425).

I can recreate the above crash from pwaller using Google Earth VR through Proton Experimental on a Steam Deck connected to a Quest 2 through ALVR.