Proton: Zero Escape: The Nonary Games (477740)

[phkb01]

Compatibility Report

• Name of the game with compatibility issues: Zero Escape: The Nonary Games
• Steam AppID of the game: 477740

System Information

• GPU: Intel HD Graphics 530
• Driver/LLVM version: Mesa 18.1.9
• Kernel version: 4.14.65
• Link to full system information report as Gist: https://gist.github.com/phkb01/6fa1413be46488ba6d483e37fbf64192
• Proton version: 3.16-1

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

The game launcher does not start (out of the box, see solution below).

The game is a bundle of two games (ze1.exe and ze2.exe) with a launcher (launcher.exe).
The launcher uses .net framework 4.5.2, which is installed on first run.
However, it seems to have a problem, since the launcher fails to start.

Solution

1. After downloading the game, do not run it yet. If you did, remove the wine prefix created at $HOME/.local/share/Steam/steamapps/compatdata/477740/pfx.
2. Create the game's wine prefix (this is the command steam runs normally):

export STEAM_COMPAT_DATA_PATH="$HOME/.local/share/Steam/steamapps/compatdata/477740"
"$HOME/.local/share/Steam/steamapps/common/Proton 3.16/proton" 'run' "$HOME/.local/share/Steam/legacycompat/iscriptevaluator.exe" 'legacycompat\\evaluatorscript_477740.vdf'

1. Install dotnet with winetrick:

export WINEPREFIX="$HOME/.local/share/Steam/steamapps/compatdata/477740/pfx"
export PATH="$HOME/.local/share/Steam/steamapps/common/Proton 3.16/dist/bin:$PATH"
winetricks dotnet46

1. Run the game from steam. It will run the first run installs then launch normally.

Note: The launcher needs .net framework 4.5.2, but we install 4.6 because the dotnet45 installed by winetricks is too old (with 4.5, the launcher will start, but the video options will crash). With 4.6, the launcher works completely.

[Gokuroro]

Just confirming that this fix worked for me also.
Previous to that, I had to run the ze1.exe and ze2.exe directly using /tmp/proton_$USER/run ./ze1.exe.

[Duckbuster]

This fixes the launcher but I have other issues with the game.
For instance with 999 video's are not working at all. Making me not able to progress/start a new game.

[Duckbuster]

Installing quartz with winetricks fixed the game freezing whenever a video needs to play.
But video's still don't play, I get this error:
80959.873:003c:003d:err:msvideo:ICLocate Required media codec 'vidc MP43' not found!

Full log here:
steam-477740.log

[robzombie91]

Edit2020: The real issue with mine was that my mouse was being treated as a joystick, so i just removed it via a udev rule

[aqxa1]

Launcher appears to work out of the box, as of Proton 4.11-2 (may have worked earlier).

[SynthRose]

On Steam Proton 4.11-13 and 5.0-3, the launcher works as expected, but 999 will not run past the opening splash screens without running protontricks 4777999 quartz. In 4.11, this allows the game to function mostly normally, although animations and videos will be skipped (such as the game preview and door opening/closing animations). Most of these animations are non-essential. This is consistent with what Duckbuster reported before. However, in 5.0, 999 will hang after the opening splash screens, even with Quartz, thus making the game unplayable. I have not tested Virtue's Last Reward.

[robzombie91]

@SynthRose try installing lav filters in your wine prefix. It helped me with the cinematics but they unfortunately have no sound but its really a non issue (at least to me)

[robzombie91]

instead of lavfilters, k-lite codec pack worked alot better and also introduced sound in cinematics

[Yjnar]

Hey, not sure if this is the right place to share my issue with the second game (Virtue's Last Reward).
Game works as it should locally but has a weird scaling issue when I try to run it in Steam Remote Play. The game window is stretched in a way that I only see the middle of the game window and all the sides don't fit inside the viewport.
This issue occurs with at least Proton 5.0-9. I will do more testing to see if older Proton versions suffer from the issue or if its a regression.