Astorish
Published
Works without tinkering, practically perfect all around.
When going into the FIRST mission of a game session, going while drunk WILL crash the game. Does not occur after the first mission, drink away.
Just make sure that steam and proton aren't broken on your OS or something like that.
No startup, spits out a bunch of hex in terminal. Completely arcane to me.
All I could make out was that it might be a problem with Wine, and I have seen one other person mention this on WineHQ, but no solution. Might work fine after some tweaking, but I don't know what I'm doing. If I find a solution I'll make an updated report.
If you can play using the NixOS stable channel, I recommend doing so, but I needed to use the unstable channel in order to even start the game. On unstable I was able to run the game, but it was using LLVMpipe as the default graphics option, putting all the burden on my CPU's integrated graphics and crippling performance. With no in-game option to solve this, I put the following into /etc/nixos/configuration.nix as a workaround:
(steam.override { extraProfile = '' unset VK_ICD_FILENAMES export VK_ICD_FILENAMES=${config.hardware.nvidia.package}/share/vulkan/icd.d/nvidia_icd.json:${config.hardware.nvidia.package.lib32}/share/vulkan/icd.d/nvidia_icd32.json ''; })
Those are two single quotes, not double quotes. This can be dumped in with all of your nixpkgs under environment.systemPackages = with pkgs; [ This forces nvidia graphics. After that, for whatever reason, the 32bit version of the game was impossible to launch. Still totally playable, even with sound errors.
Essential SFX and music sound fine, but some sfx sound like they are picked up on someones mic and played through discord.
If you have the option, avoid integrated graphics. Game should be perfect in that case, running 32bit of course. Otherwise: suffer. ... I didn't use this, but for non-Nvidia GPUs with the same problem you might find this useful: https://github.com/NixOS/nixpkgs/pull/126435
[NixOS] Didn't start, error report instead of game window.
I've seen a similar problem on other games, but for the life of me couldn't figure out the cause(s) or any potential solutions. For posterity, the error had something to do with the Graphics_DisplayM.cpp file, with HRESULT: 0x80004005.
Disregard my previous report, I'm a fool who somehow had the wrong drivers installed. Everything works fine, as far as I could tell.
Remember to update your system properly.
[NixOS] Worked perfectly, and might even be more stable than on Windows, but only after tweaking some settings. Default did not work at all.
PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command%
Using any other configuration would get me results ranging from out of memory errors to unspecified dxvk errors. It wouldn't ever get farther than the launcher without Proton 5.0-10 and PROTON_USE_WINED3D=1. Esync is off because it (supposedly) improves stability, but I haven't experimented. I play solo, so I can't confirm if multiplayer works with this setup.
[NixOS] Possible hardware issue, but unplayable with proton. Launches when the stars align, with terrible performance. "Native" works.
Switching to Proton 5.0-10 and using "protontricks 105600 dotnet452 %command%" in launch options, then switching to 7.0-1 temporarily allows launching the game.
The game was forced to use lavapipe, causing unbearable slowdown.
Without any modification, trying to launch the game with newer Proton versions causes an XNA framework error (no suitable graphics device) without launching, and using 5.0-10 creates a message asking me to launch the game from my steam client (which I was). The methods I could find to fix this were old and do not work. Using the tinker steps above, I could at least get the game to launch on proton 6.3-8 and above, but it used LLVMpipe (my CPUs graphics) which led to low performance (8fps). A different game had a similar problem, where it defaulted to LLVMpipe, but it still recognized the dedicated GPU (I got that game working eventually). Even if I could solve this problem, it reverts to its pre-tinker state (or seems to), and no longer launches. The pseudo native version at least works, albeit with reduced performance compared to windows.
There are some problems when running with proton (bad performance, lack of visual effects in some mods, lack of any visuals when using the smooth lighting options), but it will work. Native works perfectly, but I had to remove the "dotnet" and "dotnet.exe" files at */Steam/steamapps/common/tModLoader/dotnet/6.0.0/ I do have dotnet installed seperately, I don't know if that is required.
