Proton: SKYBOX VR Video Player (721090)

[leinardi]

Compatibility Report

• Name of the game with compatibility issues: SKYBOX VR Video Player
• Steam AppID of the game: 721090

System Information

• GPU: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A]
• Driver/LLVM version: 440.64
• Kernel version: 5.4.0-29-generic
• Link to full system information report as Gist: https://gist.github.com/leinardi/69512802671f6c743d2bf900b7fd61df
• Proton version: 5.0-7

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.

Symptoms

Regression using Proton 5.0-7: SKYBOX VR Video Player works fine with Proton 4.11-13 but does not work with Proton 5.0-7.

When using Proton 5.0-7, nothing is shown on the HMD and on the computer monitor there is a fixed splash of the software:

You must have a Steam VR HMD connected in order for app to work correctly (in my case a Valve Index). I also noticed that without a HMD connected, the version 4.11-13 get stuck at the same splashscreen.

Here are the Proton's logs:

• Proton 4.11-13 (working): steam-721090-4.11-13.log
• Proton 5.0-7 (not working): steam-721090-5.0-7.log

Reproduction

1. Install SKYBOX VR Video Player
2. Force to use Proton 5.0-7 as specific Steam Play compatibility tool
3. Run SKYBOX VR Video Player with a Steam VR HMD connected

[alasky17]

@leinardi I just tested SKYBOX VR and it launched successfully for me on Proton 5.0-9. Would you mind giving it another try with the new Proton version?

[leinardi]

@alasky17 I just tested Proton 5.0-9 and unfortunately the regression is still present.

steam-721090.log

Proton 4.11-13 keep working fine.

[alasky17]

@leinardi I noticed in the screenshot that you had something running to show stats while you are in VR. Could you try turning that off just in case it is involved in the regression? Also, could you get a log of the failure case with "+steam,+vrclient" logging channels added?

I didn't have any media installed to actually play with the Skybox VR when I tested -- the failure happens right at launch before the main menu pops up right?

[leinardi]

@alasky17 could you give me more info about this "+steam,+vrclient" logging channels? I tried to Google for it but I can't find anything. How can I add these channels to the log?

[alasky17]

@leinardi Sure thing :) The easiest way to add these logging channels is to:

1) Go to ~/.steam/steam/steamapps/common/Proton 5.0-9
2) Copy user_settings.sample.py and rename it user_settings.py (cp user_settings.sample.py user_settings.py)
3) Edit user_settings.py and add +steam,+vrclient to the end of the WINEDEBUG line after +mscoree and before the ending "

Proton looks for a file called user_settings.py in that location.

[leinardi]

Hey thanks a lot for the thorough explanation :)

I tried again, with MangoHud disabled, and the additional logging channels, but the regression is still there :'(

steam-721090.log

[alasky17]

@leinardi Thank you for the log! And thanks for testing with the hud disabled :)

Next -- could you upload the dxvk logs?
1) Attempt to run Skybox VR with 5.0-9.
2) cd ~/.steam/steam/steamapps/common/SKYBOX VR Video Player
The dxvk log files will be called:
SteamVR_SourceVRPlayer_d3d11.log
SteamVR_SourceVRPlayer_dxvk_config.log
3) Make sure that dxvk is being triggered at all by checking if the log files were created during the most recent run with 5.0-9:
Run "ls -l" in the SKYBOX VR Video Player folder and look at the timestamps for the dxvk log files to confirm.

If the log files were indeed created with the latest 5.0-9 failure run, could you please upload them here?

[leinardi]

Sure :) The files seems to be generated from the test I did yesterday:

$ ll SteamVR_SourceVRPlayer*.log
-rw-rw-r-- 1 leinardi leinardi 4573 giu 15 19:20 SteamVR_SourceVRPlayer_d3d11.log
-rw-rw-r-- 1 leinardi leinardi    0 giu 15 19:19 SteamVR_SourceVRPlayer_dxvk_config.log

Not sure if is expected but the SteamVR_SourceVRPlayer_dxvk_config.log is completely empty.

SteamVR_SourceVRPlayer_d3d11.log

[alasky17]

@leinardi Thank you! Could you take another log of the failure, this time with +relay added to user_settings.py? This will add a ton of logging and make the launch very slow and the log very big, so it is a good idea to quit as soon as the error happen. You will likely need to compress the log in order to attach it. I use "xz -T0 name_of_log.log" (that is a zero, not the letter).

Also make sure to remove +relay from user_settings.py after, or it will make all of your other proton games excessively slow as well :)

One more question -- what version of SteamVR are you running (standard, beta, etc)?

[leinardi]

so it is a good idea to quit as soon as the error happen

I don't actually get any error, the app get just stuck on the splashscreen and nothing else happens. I'll quit after a few seconds after it shows.
I'm using the beta channel of SteamVR.

[leinardi]

Currently getting this error while launching SteamVR:

Rebooting Steam did not help, I'll try to reboot the entire OS

EDIT
A session relogin fixed it. Currently working on the log file (which uncompressed is 1.3GB!!!!!)

[alasky17]

@leinardi Sorry for being a bit confusing -- that is exactly what I meant :) And I am on the beta channel too, so that rules out one more thing :/ If you can't get the log file to compress small enough to upload here, I have a separate place where you can upload it that I can link to.

[leinardi]

Wow, nice compression rate: from 1.3GB to 52MB.

It's to big to be attached here, I uploaded it on Dropbox, let me know if is OK or if you prefer using some other service:
https://www.dropbox.com/s/m0siid4t3gwp82a/steam-721090.log.xz?dl=0

Also, please let me know when I can delete it.

[alasky17]

@leinardi I got it :+1: Feel free to delete. Thank you!

[frostworx]

just wanted to mention that I just tried the app after a longer time with a new installation/wineprefix using proton-5.0-10-rc2.
on the initial launch the program started fine but playing a video got stuck. Tried again with proton 4-11-13 and the video (and others) played fine, but after trying again with proton 5-0-10-rc2 the videos played fine as well.
maybe the wineprefix just broke somewhere?
In case you have some use for it here are proton logs for
proton 4-11
steam-721090-4.log
and
proton-5.0-10-rc2
steam-721090-5.log

[alasky17]

@frostworx The steps you wrote would imply that the issue is with the win10 prefix. Going back to 4.11-13 will downgrade the prefix to win7, and upgrading back to 5.0-x will not upgrade it back to win10.

@leinardi I don't think this is your issue based on the description of the failure you have given. Before trying to change the prefix Windows version, I think it would be worth making sure that your Vulkan install is working:
1) Run "vulkaninfo" in a terminal

2) It should spit out a ton of info. If it doesn't, then troubleshoot that until vulkaninfo works :)

FWIW, instructions to try forcing the prefix to win7 to see if that helps:
run: WINEPREFIX=~/.steam/steam/steamapps/compatdata/721090/pfx winecfg

This should pop up the winecfg dialogue and the Windows version has a dropdown box where you can change it for the prefix. I'm pretty sure you need to install wine somewhere first in order to have this tool. You can easily install a version of wine with your package manager (apt install wine).

[frostworx]

instead of forcing winver over the existing WINEPREFIX I'd simply rename the old one and restart from scratch with a new one.

[leinardi]

@alasky17 vulkaninfo.txt

I checked the Windows version and is always set to Win7, no matter which version of Proton I use:

Proton 4.11-13 works, Proton 5.0-10 (next branch) does not.

[alasky17]

@leinardi Thank you for checking -- that is what I would expect. Downgrading to 4.11-13 will force the version to win7. If you create a fresh prefix on 5.0-10, it will be win10 until you launch the prefix on 4.11-13.

I think this is a red herring though since @frostworx was able to launch the game just fine and only video playback was borked -- I don't think they are running into the same error unfortunately :/