search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.45k stars 1.07k forks source link

TOXIKK (324810) #2011

Open xDShot opened 5 years ago

xDShot commented 5 years ago

Compatibility Report

System Information

I confirm:

steam-324810.log

Symptoms

Game works if manually install .NET Framework included in game redistributable to the game's wine prefix (steam/steamapps/compatdata/324810/pfx/) and setting mscoree.dll as native.

The real problem is that the game can't recognise purchased Full Game DLC (https://store.steampowered.com/app/503270/TOXIKK__UPGRADE__Free_Edition_to_FULL_GAME/) and still thinks it's free version.

Also the game suffers of performance degradation (both with logging enabled and disabled), though not sure if it's somehow related.

Reproduction

Simmonz commented 5 years ago

I tried running the free version of Toxikk through Proton but it crashes seconds after displaying the game's splash screen. I added PROTON_LOG=1 %command% to the game's launch od got the following log:

steam-324810.log

I have checked whether there are updates for my system available and I am up to date

System Information:

Distro: Manjaro

GPU: RX 580 8GB

Driver/LLVM version: Mesa 19.0.3/8.0.0

Kernel version: 5.0.9-1-MANJARO

Proton version: 4.2-3

https://gist.github.com/Simmonz/83350260283bb22e522f7f8b3e66360f

madewokherd commented 5 years ago

2946.467:0058:0059:fixme:mscoree:get_runtime Unrecognized version L"v4.0.20926"

4.2-4 has a change that may help.

Simmonz commented 5 years ago

2946.467:0058:0059:fixme:mscoree:get_runtime Unrecognized version L"v4.0.20926"

4.2-4 has a change that may help.

Sadly still crashes for me. It gets a bit further. Last time it crashed before even giving me the option to agree to Unreal terms where now it allows me to agree and starts to launch the game for a second before crashing.

System Information:

Distro: Manjaro

GPU: RX 580 8GB

Driver/LLVM version: Mesa 19.0.4/8.0.0

Kernel version: 5.1.1-2-MANJARO

Proton version: 4.2-4

steam-324810.log

Lepidos commented 4 years ago

Using Proton version 4.11-11 Game crashes with: out of video memory

AsciiWolf commented 4 years ago

Using Proton version 4.11-11 Game crashes with: out of video memory

Same issue with Proton 5.0-5.

Lepidos commented 4 years ago

Proton log: https://raw.githubusercontent.com/Lepidos/ProtonLogs/master/steam-324810.log

js6i commented 4 years ago

Using Proton version 4.11-11 Game crashes with: out of video memory

Same issue with Proton 5.0-5.

As a workaround use the OpenGL back end (put PROTON_USE_WINED3D=1 %command% in launch options).

AsciiWolf commented 4 years ago

Using Proton version 4.11-11 Game crashes with: out of video memory

Same issue with Proton 5.0-5.

As a workaround use the OpenGL back end (put PROTON_USE_WINED3D=1 %command% in launch options).

Thanks! The game now works and performance is pretty good on my AMD RX 580, even without DXVK.

AsciiWolf commented 4 years ago

It seems that every time TOXIKK is started, it replaces all config files with default ones. I workarounded this by manually editing[1] the config files (UDKInput.ini, UDKSystemSettings.ini, UDKCustomChar.ini, UDKEngine.ini etc.) from ~/.steam/steam/steamapps/common/TOXIKK/UDKGame/Config, then setting chmod 444 on these files.

[1] It is also possible to make the changes in game by launching TOXIKK, changing permissions of the config files to read/write, making changes in game, then changing the permissions back to read-only.

AsciiWolf commented 4 years ago

Here is a workaround (patch) for the Full Game DLC issue!

AsciiWolf commented 4 years ago

I can confirm that the workaround works fine!

toxikk_proton_serverbrowser

AsciiWolf commented 4 years ago

Using Proton version 4.11-11 Game crashes with: out of video memory

Same issue with Proton 5.0-5.

As a workaround use the OpenGL back end (put PROTON_USE_WINED3D=1 %command% in launch options).

I can confirm that this workaround is no longer needed since the latest Proton 5.0-7 and TOXIKK now works fine with DXVK enabled. :-)

alasky17 commented 4 years ago

Hey folks! Just wanted to let you know that there should be further improvements to this game in 5.13-1. Currently, I've found that the game runs well with the only "workaround" being to set d3d9.evictManagedOnUnlock = True in dxvk.conf