ChilloutVR (661130)

[SoraBytes]

Compatibility Report

• Name of the game with compatibility issues: ChilloutVR
• Steam AppID of the game: 661130

System Information

• GPU: AMD RX 5600 XT
• Driver/LLVM version: Mesa 22.1.4
• Kernel version: 5.15.55-2-lts
• Link to full system information report as Gist: SystemInfo
• Proton version: Proton Experimental (Bleeding Edge)

I confirm:

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

Symptoms

When you join any world and interact with a media player the game crashes.

Reproduction

Create a new instance world (public, friends, friends of friends etc), interact with a media player the game crashes.

steam-661130.log
Player.log <- Line 2225

[CrispyPin]

Until this is fixed you can use --disable-videoplayers in the launch options

[CrispyPin]

I have a different issue though, the game crashes after about 2 minutes regardless of what I do. It has now crashed more than 5 times in a row and yesterday I had no issues.

This is suspiciously similar to #1199 (comment) in vrchat, and I don't know of a fix.

The last message in Player.log is always

Crash!!!
SymInit: Symbol-SearchPath: '.;Z:\home\crispypin\.steam\debian-installation\steamapps\common\ChilloutVR;Z:\home\crispypin\.steam\debian-installation\steamapps\common\ChilloutVR;C:\windows;C:\windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 534, UserName: 'steamuser'
OS-Version: 10.0.0

EDIT: this was fixed by removing the proton prefix, no clue what caused it in the first place though.

[yshui]

This could be the same problem VRChat fixed by updating their AVPro player.

[roryyamm]

I'm getting sound underruns while using ALSA. Any way to fix that?

[CarbonNotes]

The Intro video plays, but appears to have issues:

Otherwise, the game seems to work well (And it's even possible to use the Linux build of Unity to upload avatars and worlds as long as you set the build target to Windows)

[lautriva]

Probably related issue
When I start the game, its stuck on a black screen with only mouse cursor visible

Temp fix I found: if I press the spacebar during the black screen, the game runs as normal (bring me to "successfully logged in" screen)
Maybe the intro video cannot load and spacebar is used to skip it?

[kisak-valve]

Hello @CarbonNotes, 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.)

Separately, can you test how the game behaves with the game's launch options set to WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%?

[abb128]

I launch the game in VR, it logs in and puts me in the home world, and it crashes after about two minutes regardless of what I do, even if I just AFK. The game runs fine up until the crash.

These are the launch options I used in the log but the behavior is the same when it's blank: PROTON_LOG=1 WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command% --disable-videoplayers

steam-661130-p.zip

[CarbonNotes]

Maybe the intro video cannot load and spacebar is used to skip it?

That sounds correct. I believe you don't have h264 enabled in your Steam runtime, or you are using an older version of Proton.

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.)

steam-661130.log.gz

WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%

That fixes the loading screen video.

EDIT: Looks like switching to Experimental Bleeding Edge also fixes the video playback without DO_NOT_CREATE_DXGI_DEVICE

[CarbonNotes]

I launch the game in VR, it logs in and puts me in the home world, and it crashes after about two minutes regardless of what I do, even if I just AFK. The game runs fine up until the crash.

I think I'm hitting this issue too... PROTON_NO_FSYNC=1 doesn't help.

I intermittently had the same issue on VRChat as well, and that appeared around the time they switched to their current version of Unity. Chillout and VRChat currently use the same Unity version.

On my system, this shows up as VRAM usage consistently increasing until the game suddenly crashes. It doesn't always do it, though. For reference, I believe my system has AMD Smart Access Memory enabled.

[abb128]

VRAM usage consistently increasing until the game suddenly crashes

I tested the game a bunch of times while keeping a close eye on VRAM usage and was unable to observe this on my machine. VRAM remains steady and normal (at say, 48%) after loading into the world and does not change. When the game crashes the VRAM simply drops to the level it was before launching the game and that's it. My system does not support AMD Smart Access Memory.

[CarbonNotes]

VRAM remains steady and normal

Were you also watching GTT? When I use RADV_PERFTEST=nosam, instead of VRAM growing, GTT usage increases until the game crashes. I use Radeontop to monitor the usage.

[abb128]

I checked GTT through radeontop and it is indeed slowly increasing. Of 8165M GTT, it starts at 30% when the game is loaded and steadily increases (despite not doing anything ingame) until hitting about 61% and crashing. If I launch the game in desktop mode GTT remains stable and game doesn't crash.

For testing purposes I tried reducing my GTT size to 2048M. The usage still continues to grow until it reaches 100%, at which point it drops down to about 80%, then keeps growing and the pattern repeats once or twice before staying steady at 100%. The game still crashes after about two minutes.

[CarbonNotes]

So it appears that you are experiencing the exact same issue as I am (just manifesting slightly differently on a different system configuration; SAM vs no SAM).

Seeing as I also experienced an issue with the exact same symptoms on VRChat (which uses the exact same version of Unity) I'm going to make an educated guess that this is likely a Unity-related bug, or a bug related to one of the common shared plugins/libraries that both VRChat and ChilloutVR use; and is not specific to either VRChat or Chillout.