Tower Unite (394690)

[karlsbjorn]

Compatibility Report

• Name of the game with compatibility issues: Tower Unite
• Steam AppID of the game: 394690

System Information

• GPU: Radeon RX 580
• Driver/LLVM version: Mesa 19.1.0-devel, LLVM 9.0.0
• Kernel version: 4.18.0-15-generic
• Link to full system information report as Gist: https://gist.github.com/karlsbjorn/e5ed055bd834b09a9ca2bbbe953731e2
• Proton version: proton-3.16-8

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.

steam-394690.log steam-394690-wined3d.log

Symptoms

When the game is loading into the plaza, it crashes with the following error message:

This does not happen when adding PROTON_USE_WINED3D=1 %command% to the launch options and it manages to load fine, but the game now has various graphical glitches that can be seen in the screenshots below:

This also happens in at least one minigame outside of the plaza (notice the snowflakes and nametag):

Reproduction

Play Tower Unite and attempt to enter the plaza or Ball Race on the 'summit' map.

[kisak-valve]

Hello @karlsbjorn, please verify you have vulkan drivers installed for your video card with something like apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386.

[karlsbjorn]

Everything seems to be installed, @kisak-valve.

Pasted output:

$ apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386
mesa-vulkan-drivers:
  Installed: 1:19.1~git190305181400.43f40dc~b~padoka0
  Candidate: 1:19.1~git190305181400.43f40dc~b~padoka0
  Version table:
 *** 1:19.1~git190305181400.43f40dc~b~padoka0 500
        500 http://ppa.launchpad.net/paulo-miguel-dias/mesa/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status
     18.2.2-0ubuntu1~18.04.2 500
        500 http://hr.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
     18.0.0~rc5-1ubuntu1 500
        500 http://hr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
mesa-vulkan-drivers:i386:
  Installed: 1:19.1~git190305181400.43f40dc~b~padoka0
  Candidate: 1:19.1~git190305181400.43f40dc~b~padoka0
  Version table:
 *** 1:19.1~git190305181400.43f40dc~b~padoka0 500
        500 http://ppa.launchpad.net/paulo-miguel-dias/mesa/ubuntu bionic/main i386 Packages
        100 /var/lib/dpkg/status
     18.2.2-0ubuntu1~18.04.2 500
        500 http://hr.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages
     18.0.0~rc5-1ubuntu1 500
        500 http://hr.archive.ubuntu.com/ubuntu bionic/universe i386 Packages

Edit:

Looks like the crash mentioned in the OP was actually a problem with the game itself, as it got fixed in the most recent update. The game can now be ran with no launch options but some parts of the game are still broken (areas not loading, input doesn't work sometimes). No clue whether that's the game or Proton so I'll wait for a few more updates.

[some-username-here1]

With the recent update, currently being version 0.8.5.0, using Steam Play no longer works and instead gives out a fatal error when using version 4.11-8. Using any other version has the game giving out a different error, being DX11 feature level 10.0 is required to run the engine..

[kisak-valve]

Hello @some-username-here1, what error message are you seeing? Please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

Separately, does adding WINEDLLOVERRIDES="dxgi=n" %command% to the game's launch options have an effect?

[some-username-here1]

I tried starting the game with WINEDLLOVERRIDES="dxgi=n" %command% using Proton 4.11-8, but it gave me the DX11 requires feature level 10.0 error.

Also here's the log.

[kisak-valve]

Thanks, Proton uses DXVK to translate DirectX 10/11 to vulkan and these lines in your log hint that the vulkan isn't initializing on your system: err:vulkan:wine_vk_instance_load_physical_devices Failed to enumerate physical devices, res=-3 err:vulkan:wine_vkCreateInstance Failed to load physical devices, res=-3

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.

[some-username-here1]

here

[kisak-valve]

Thanks again, you have a Southern Island (SI) generation AMD video card. By default Linux uses the radeon kernel module with this video card, which is not compatible with Vulkan. Please give https://github.com/ValveSoftware/Proton/wiki/For-AMD-users-having-issues-with-non-OpenGL-games a read.

Also, please verify that you have the mesa-vulkan-drivers and mesa-vulkan-drivers:i386 packages installed with something like apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386 and install them with sudo apt install mesa-vulkan-drivers mesa-vulkan-drivers:i386 if they are not already.

---

Alternatively, you could try adding PROTON_USE_WINED3D=1 %command% to the game's launch options to tell Proton to use the DirectX 10/11 to OpenGL render path, but this comes with a substantial performance penalty and is not supported.

[some-username-here1]

After enabling amdgpu support for my GPU, I was able to successfully launch the game. But anytime I join another player's mini-game session, it would just crash with an error. I got into a game in another mini-game other than the main one I usually play, but once I was in, I couldn't do anything though, just view the 3D landscape from a fixed view.

Here's some logs if needed: tower-unite.zip The first two logs are of the same minigame I tried to get into, and the third log being a different minigame.

And here's my apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386:

mesa-vulkan-drivers:
  Installed: 19.1.2-0~b~padoka0
  Candidate: 19.1.2-0~b~padoka0
  Version table:
 *** 19.1.2-0~b~padoka0 500
        500 http://ppa.launchpad.net/paulo-miguel-dias/pkppa/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status
     19.0.8-0ubuntu0~18.04.3 500
        500 http://ny-mirrors.evowise.com/ubuntu bionic-updates/universe amd64 Packages
     18.0.0~rc5-1ubuntu1 500
        500 http://ny-mirrors.evowise.com/ubuntu bionic/universe amd64 Packages
mesa-vulkan-drivers:i386:
  Installed: 19.1.2-0~b~padoka0
  Candidate: 19.1.2-0~b~padoka0
  Version table:
 *** 19.1.2-0~b~padoka0 500
        500 http://ppa.launchpad.net/paulo-miguel-dias/pkppa/ubuntu bionic/main i386 Packages
        100 /var/lib/dpkg/status
     19.0.8-0ubuntu0~18.04.3 500
        500 http://ny-mirrors.evowise.com/ubuntu bionic-updates/universe i386 Packages
     18.0.0~rc5-1ubuntu1 500
        500 http://ny-mirrors.evowise.com/ubuntu bionic/universe i386 Packages

EDIT: here's the same error that occured with the first two logs (tried getting into the Plaza this time):

[some-username-here1]

Not sure if this is an issue on just Linux via Proton, but as of the 0.9.0.1 update, now I'm unable to join any servers or send any messages in the chat.

Is this issue on Windows also, or...?

[raku-cat]

In lieu of making a new issue I figured I'd try posting here first. The current state of this game in desktop mode is basically functioning equal to as on windows as you can see from reports here: https://www.protondb.com/app/394690 With that said, they've done some updates recently for the VR implementation, when I tried it using multiple proton versions I was never able to get it to work, and from what I can gather it seems to be a proton issue. Proton 7 series just launches the game normally as though the vr option was not picked, Proton 8 series crashes to desktop with no error dialogs or crash reporters, and Proton 9 series (including GE) crashes to an error report dialog: The headset display is unchanged from the default background during all of these attempts and shows no signs a game is starting. Here is a full log of attempting to launch the game: https://gist.github.com/raku-cat/82a56b8f2873e2866723c90d166ee369

[kisak-valve]

Hello @raku-cat,

trace:vrclient:winIVRClientCore_IVRClientCore_003_GetGenericInterface 00000000007B27E0
trace:vrclient:ivrclientcore_get_generic_interface 000078563550FE3C 0000000142683800
trace:vrclient:create_win_interface trying to create IVRCompositor_022
trace:vrclient:create_winIVRCompositor_IVRCompositor_022 -> 0000000000663B90
trace:vrclient:winIVRCompositor_IVRCompositor_022_GetTrackingSpace 0000000000663B90
trace:vrclient:winIVRInput_IVRInput_004_GetSkeletalActionData 00000000006502F0

immediately followed by an access violation (c0000005) in vrclient_x64.dll looks likes some lines of interest in your Proton log.

[raku-cat]

I see, is there anything to be done on my end to debug further based on this?