Vepar
Published
Works without issues.
Works perfectly fine!
Ray tracing performance is worse than on windows, but other than that, played 120 hours without any issues, ultra settings, no FSR, no RT in 1440p.
I installed it on Heroic cause i don't have it on Steam, i have it on Epic, but should work on steam too without issues.
Great Truck sim, no problem running!
Played singleplayer, and convoy mode, both work without issues at the default mode (Dx12). I don't have any DLCs but i don't think they'd be too different of an experience since they're just another map in the game. And the game works.
Native game that runs great!
The 1440p resolution was unstable, but setting it to 1080p worked great. Which is kind of better because 1440p makes things look too small.
No proton required. I didn't even know i was playing a native version until i wanted to back up my save file and saw there is no proton prefix lol. So just install and play!
If you don't mind playing with KB/M, works good natively!
No matter what i tried, i couldn't get the Steam controller to work. It worked exactly once when i used Steam (runtime), and then it stopped working again. Keyboard and mouse work, but for some reason, the Steam Input isn't recognized at all. Might work with a normal xinput gamepad, might not, Steam controller is all i have.
Switching to any proton made the game crash after the intro logo. Native doesn't work with Steam Input for me, but otherwise has no issues as far as i can tell.
The game works out of the box, Steam and proton integration are wonderful. Use "-provider Portal" to play with your Anet account.
gamemoderun WINE_FULLSCREEN_FSR=1 DXVK_ASYNC=1 %command% -provider Portal
With X11 and Kwin compositing, the game skips frames when FPS is not EXACTLY like your refresh rate. The game FPS counter reports 60+ but looks like it's half of that or less. Turning on Vsync in game makes this worse. Either use Wayland, or disable compositing before you play if this happens. This is identical on GE or Experimental.
The game works out of the box on Steam, but you might want to tinker with it to get the best experience possible, but that's not strictly necessary, you can just plug and play. Use experimental or GE whichever one gives you better performance, "-provider Portal" for your Anet account, and DXVK_AYNC to preload the shaders cause the game loads them constantly, it works better if you preload them. Gamemoderun if you have it is nice, and WINE_FULLSCREEN_FSR just makes the game look a bit prettier with practically no performance loss so, why not. All of that is optional of course, and if you play with your Steam account, don't put "-provider Portal" in the launch options.
It works good enough for an enjoyable experience.
The game said it's running in full screen, but the monitor kept turning off after the period for locking i set in the KDE settings. I had to manually block sleep and locking in order to play uninterrupted. Not a big deal, but this is the only game so far that did not block monitor sleep.
Some micro stutter during some stage transitions, but other than that, works smooth!
Install wininet with winetricks or protontricks, doesn't work without it.
Install wininet and play.
gamemoderun WINE_FULLSCREEN_FSR=1 %command%
Login works just fine, as does visiting other galleries.
Pretty unique game, very glad it works on linux. Pretty heavy on the requirements though, hence the gamemoderun and FSR comments, so i could run it at a lower resolution without losing too much fidelity.
Crash when trying borderless window mode. Worked only in fullscreen.
Cloud saves from previous playthroughs on Windows were missing.
Drops to 1 FPS after about 5-10 minutes and becomes unplayable.
Crashes and won't start a new game if you don't disable the intro cinematic.
Not sure what's causing the slowdown, it acts like a memory leak, but i haven't been able to find a way around it, so the game is sadly unplayable.
Should work without tinkering, just default Steam proton, but i feel like for my hardware GE works a bit better.
gamemoderun WINE_FULLSCREEN_FSR=1 DXVK_ASYNC=1 %command%
I read on some reports here that you should first install Overlord, then run it once (create a profile), close. Then install Rising Hell, and play. I haven't tried doing otherwise, but this worked perfectly so i guess better safe than sorry. You may or may not need to do this.
No issues running the game!
Runs on the default proton, no need to force a specific version!
Using protontricks, it's easy to install both Physx and the Community patch. Other methods noted are overcomplicated and don't have to be.
RADV_PERFTEST=gpl %command%
There's an overcomplicated guide out there on how to get this game to work by installing Physix and the community patch that involves renaming the executable so that steam runs into something else, then running the game through steam, shifting wine prefixes and whatnot, and everyone else that wrote a report for this game seems to follow this but there's a better way.
Use protontricks.
- In the GUI, select Sacred 2 Gold.
- Select the default wine prefix.
- Run an arbitrary executable.
Then find the Physx installer in the game's folder, run that, and when you download the patch, run cm-enable.exe the same way. This will install both Physx and the Community patch without the complicated need to rename the game executable so that Steam could run it. That's why we have protontricks, use it.
That's it, the game runs after that, and DON'T use PROTON_USE_WINED3D=1, the game will lag constantly. Just play the game without it.
TInkering required, but perfectly playable after you use protontricks to install those 2 executables, Physics and cm-enable. Just select the game prefix, and select to install arbitrary executable. That's it.
Also, apparently, the patch introduces some bug according to this: https://docs.google.com/document/d/1E1w4kITmNQVy67bliuvwwwaQMKS5gURbTU3sSdObriM/edit?tab=t.0
The last paragraph is a fix, and just involves editing a text file and changing "1000" to "1". So, easy enough. Don't follow the rest of it though, just use protontricks, it should work perfectly fine instead of messing with the game exe and wine prefixes.
Works out of the box!
Works great! I just installed it and it worked, no tinker steps needed.
No issues running and playing!
Didn't even need to force choose a proton version, it just works!
Works great, but force experimental, and if it crashes on loading save games, use wine3d11 instead of vulkan.
PROTON_USE_WINED3D11=1 %command%
Depending on i guess your hardware and drivers - it might work out of the box, but native version has audio issues, and proton version crashed on loading save games when using default vulkan.
Rns out of the box!
No specific proton needed. Modded and unmodded versions run fine, provided you correctly installed the mod loaders and mods of course.
The launcher needs dotnet48 or it crashes, so install it with winetricks.
If you get a "token error" when starting the launcher, make sure you have "gnutls" and "lib32-gnutls" packages installed. Once i installed those, the token error went away and i was able to start the launcher.
This is for Heroic Launcher users. Steam steps are different.
Make sure you install dotnet48 with winetricks, and using winecfg, add a D: drive, then point the path of that drive to where Heroic is installed. For me it was /run/media/username/drivename/Heroic. Point the drive to Heroic install (where it installs all your games), not to the ESO folder. And as stated, gnutls and lib32-gnutls to fix the token error. After that, it installs, launches, downloads and plays great!
Out of the box experience!
Shold just work. I finished it completely without any issues.
Works out of the box, no tinkering!
I haven't yet finished it on linux but i don't forsee any problems. Game works as expected.
Worked out of the box, no issues.
Didn't try multiplayer, but i don't see why it wouldn't work, the rest of the game worked great so, i don't forsee any issues, especially since multiplayer is through steam on this edition.
Works great out of the box!
Started the game, joined a match and finished it without any issues.
Multiplayer only game so, yes, multiplayer works perfectly fine.
Runs great - in the beta branch.
It wouldn't run, gave some error, missing executable i think out of the box, but opting into public beta fixed that and made it run without issues.
Install VTMB Unofficial Patch version 11.3 (or higher).
The game needs the Unofficial patch by wesp5 to function. Even on windows, so this can't be a non-tinkering report. But ever since patch version 11.3, the tinkering you have to do is set to a minimum. Download the unofficial patch 11.3 (or higher) from ModDB, and install - it installs without issues using wine. Then, DON'T launch the game from the steam library, go to the game folder, and look for a file named "Loader.exe". Run that. You can add it to Steam as a non-steam game for easy access, or run it directly from a file. This is a linux optimised .exe loader that will run the game on linux without any issues that you would get running from steam (with or without unofficial patch). It gives you the menu to run the game with the basic patch, or plus patch, and it's working as if it's running natively! It's THAT good!
Asks for a CD key. Did some googling and apparently both steam and gog version use the same one: BEF7-PED2-ZUR7-JED6-8386 (found in steam discussions here: https://steamcommunity.com/app/559680/discussions/0/2518023667606314960/) Entered the key and it ran normally. It shouldn't ask for a cd key, but if it does, enter this one, it worked for me.
The CD key bug seems to be present even on windows versions, but it seems to be an easy fix.
Runs natively!
Didn't try multiplayer, but i have no reason to believe it wouldn't work. Singleplayer works perfectly!
