Nocturnal
Published
Requires D9VK (https://github.com/Joshua-Ashton/d9vk) to run well. Simply download the latest release, extract it, copy (or symlink) /x64/d3d9.dll into /steamapps/common/HatinTime/Binaries/Win64/ and add the following as launch options: «WINEDLLOVERRIDES="d3d9=n" PROTON_NO_ESYNC=1 %command%» (without «»). Some stuttering happens when shaders are being built, but runs at a stable 60fps once the shader cache is filled.
Runs great when using D9VK (available in Proton 4.11-1). Add the following (inside «») to launch options: «PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_USE_D9VK=1 %command%». The former seems to have fixed a crash I had when loading one of the levels in Subcon Forest and the latter enables D9VK. Some stuttering when loading shaders, but otherwise great.
Runs great out of the box
Using ACO rather than LLVM on RADV, I encountered a few stutters during loading screens (presumably when building shaders), but no stutters when the level had loaded. Ran great overall.
Tried to enable the multiplayer part of Nyakuza Metro, and was able to connect and interact with other players. Admittedly didn't test this feature in depth, but it didn't appear to have any issues.
The game process starts (as indicated by Steam: - Running), but appears to get stuck with no window appearing. The process accepts SIGTERM and dies gracefully.
Still not working for me. The game process starts (Steam claims the game is Running), but no window appears. Attaching gdb to the PID yields no info.
Needs two workarounds: First, use winecfg with WINEPREFIX=/path/to/steam/steamapps/compatdata/313870/pfx/ and change the Windows Version from "Windows 7" to "Windows XP". This makes the game launch. Secondly: enable D9VK, otherwise the framerate is unbearable (1-3fps). With these fixes, the game appears to run well, though I haven't tested it for long yet.
Runs well
Crashed once during my playthough, seemed to be related to moving to a new zone. Nothing game breaking.
Experienced one crash in my ~2 hour playtime. Otherwise worked perfectly.
Having a Ryzen 3xxx, I encountered a bug (https://github.com/ValveSoftware/Proton/issues/2927) when trying to launch the game that caused it to immediately exit. This can be worked around in two ways:
- By upgrading to Linux 5.4 kernel, which includes a fix.
- By setting kernel argument "clearcpuid=514".
Linux native works well enough. Proton version is only required in order to cross-play with Windows-installations.
The Launcher.exe shipped with the game immediately exits. To fix this, replace Launcher.exe with Borderlands2.exe in <path/to/game/install>/Binaries/Win32/ so that it skips the launcher and starts the game directly.
Sometimes crashes during loading of new areas/death warps with an error about running out of video memory. Minor annoyance, but not a big issue.
Works well out-of-the-box. Good performance.
Played through the entire campaign without issues. Have not tested multiplayer/zombies.
Got the game to start using the vcrun2017-winetrick mentioned in the comments below. However, the game crashes to desktop after character creation, and is thus unplayable. Have tried: renaming MovWW-folder (no effect), installing binkw32 (no effect), starting offline (no effect), disabling Steam Cloud Sync (no effect), and combinations of aforementioned.
No longer crashes after character creation with Proton 4.2-1. Generally runs great, but has some small jitters when (I assume) shaders are being built. Nothing that detracts from the experience, though. As stated earlier, vcrun2017 needs to be installed in the wine prefix in order to launch the game. This is done as follows: WINEPREFIX="<PATH_TO_STEAM>/steamapps/compatdata/570940/pfx" winetricks -q vcrun2017.
Proton-5.11-GE-3-MF (https://github.com/GloriousEggroll/proton-ge-custom/releases)
Crashes when trying to register account.
Does not play videos.
Requires quite a bit of tinkering to get working, but runs well once set up correctly.
To get the game running:
- Download and use a recent GloriousEggroll release (I used Proton-5.11-GE-3-MF), as regular standard proton version as of 5.0.9 does not work.
- Set Browser to 1 instead of 2 in FFXIV_BOOT.cfg. This allows the launcher to work.
- When starting the game for the first time, don't use the launcher for account registration, as it will crash after filling in email/password etc., which results in a registration code in an email that cannot be filled in anywhere and a 24h lockout before you can use the same email address again.
Instead, register an account on SquareEnix's webpages and fill in CD-keys from Steam in the MogStation (see details here). - When logging in with the launcher, press Enter after filling in ID/password rather than clicking the «Log In» button with the mouse, as that will cause a javascript:ctrEvent('mainform')-error.
Doing all these steps will allow the game to launch. So far, I've been playing for about 7 hours and I'm pretty pleased with the performance.
The only issue I've come across is that it seems videos (the non in-game ones) do not play: black screen with no audio, can be skipped with Esc. It's somewhat annoying but does not detract too much from the overall experience.
As stated previously: requires disabled Uplay overlay to start. Runs OK (30-60fps), but has quite a bit of stuttering every now and then. Some semi-transparent black boxes appear around houses, which is a bit annoying. I've had the game crash about 3 times so far, most of which while in menus. Works, but cannot really recommend it.
Had to disable ESYNC to get audio working
Some minor graphical glitches, nothing that detracts from the experience.
Navi RADV artifacts gone with Mesa 19.3.2
The graphical artifacts I experienced with Mesa 19.3.1 are gone when updating to 19.3.2. I imagine it's due to the LOD artifact fix for Halo MCC (https://www.mesa3d.org/relnotes/19.3.2.html). Also tried running without the ESYNC workaround, and audio seems to work out of the box now (not sure what caused this).
So I would say it's pretty much perfect on Navi with Mesa 19.3.2 or later.
Audio issues mentioned previously have been fixed Proton 3.16-5 Beta. Some stuttering while the shader cache is being built, but this decreases as the game progresses. Perfectly playable with 50-60fps on max settings for me.
Out of sync dialogue during cutscenes using Proton 6.3-8. This is fixed by running the game with Proton Experimental.
Runs great without tinkering
Multiplayer interaction had no issues whatsoever. Solid high frame rate.
Minor issues with alt-tab, otherwise great
Mouse pointer disappears when alt-tabbing. It was possible to get it to re-appear without quitting the game, but it seemed to happen randomly by switching between windows.
Performance and gameplay was excellent.
Proton-5.9-GE-7-ST GloriousEggroll
Proton-5.9-GE-7-ST https://github.com/GloriousEggroll/proton-ge-custom/releases
Some minor artifacts in the skies for a couple of missions. Nothing that detracts from the experience.
Had to use windowed without borders rather than fullscreen.
Played through the entire campaign with no major issues. Performance was excellent.
Works well
See the resolution tweak mentioned in previous comments.
Beyond that, the game runs great. I did not encounter any issues in my 20+ hour playthrough of the main story.
Did not test the DLCs, but I have no reason to doubt that they will work either.
Runs great! Only issue encountered is that the loading screen for the main menu gets stuck and requires a tab-out to continue. Minor annoyance but easily worked around. Main game has no issues whatsoever.
Runs great out-of-the-box, no tinkering required. Quite good frame rates at high settings with no noticeable stutters.
Using the ACO compiler by default («export RADV_PERFTEST=aco» in .profile).
With the latest update to Proton (3.16-7 beta), uplay now runs properly and the game launches. I played through about five levels and did not encounter any problems. Take note that Steam has some issues updating Proton to 3.16-7, so verify that it has using DXVK_HUD=version (look for 0.96) before you try this game, otherwise uplay will not work.
Great little game; runs well.
Minor cracking observed. Not enough to ruin the experience.
Runs perfectly without tweaks. It's admittedly a bit weird to be running COMI through ScummVM over Wine when ScummVM runs natively on Linux, but it works.
Runs well, but some shader cache stuttering and one crash was experienced. Absolutely playable, although I will not give it a Platinum rating due to the aforementioned.
Runs well, but some shader cache stuttering and one crash was experienced. Absolutely playable, although I will not give it a Platinum rating due to the aforementioned.
Runs well, but some shader cache stuttering and one crash was experienced. Absolutely playable, although I will not give it a Platinum rating due to the aforementioned.
