[BUG] Carrier Command 2 (32-bits app) starts then stops updating the VR view

[Patola]

Describe the bug
Using SteamVR via Steam Link, the game Carrier Command 2 starts ok, but right at the moment that it should start a game it stops updating the VR view and thus becomes unplayable. The window on the flatscreen continues updating and shows that it is even responding to the controls.

This behavior can be seen on this video: https://www.youtube.com/watch?v=bHCDESpE88Y

This bug was reported in proton here: ValveSoftware/Proton#8009 but it's not a proton issue, since the game RUNS with proton with WiVRn, another openxr/openvr backend for Linux.

To Reproduce
Steps to reproduce the behavior:

1. Start Steam Link on the headset, connect to Steam to start VR mode
2. On the SteamVR interface, select carrier command 2 and start the game. Game will start OK.
3. Within the menu in-game, select start game, start singleplayer campain
4. Left and Right eyes will then get stuck in different angles and the headset image will stop updating.

Expected behavior
Game should continue working after start game is chosen.

System Information (please complete the following information):
SteamVR beta is at the same version as steamvr stable, so steamvr stable 2.14.5 should be ok.

• Steam client version (build number or date):
• SteamVR version: 2.14.5
• Distribution (e.g. Ubuntu): Archlinux
• Steam runtime diagnostics: [generate via Help -> Steam Runtime Diagnostics in the Steam client]: https://gist.github.com/Patola/9e8407c5e943fc34cbdf2a9c1d48a0eb
• Steam and SteamVR logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
• Minidumps: [run the following command: tar -zcvf ~/Desktop/steam-minidumps.tar.gz /tmp/dumps]

steam-logs.tar.gz
steam-minidumps.tar.gz

Note
There are recent proton logs on the proton issue, including one generated with options PROTON_LOG=+vrclient,+openxr,+file %command% which give very detailed information on the openvr calls, so be sure to consult that bug report.

Additional context
A proof that the problem is not in proton, since it's playable in the same proton when the openxr/openvr backend is different, can be seen in this gameplay: https://youtu.be/iDA_cOLFCtg