SasuCrowVT/TTV
Published
Proton 6.3-5 borked at sub-10 FPS. Native version works about as well as Windows. Plays at about ~50 FPS natively at 4k on Ultra+.
Frequent flickering for objects that are far away, not gamebreaking and only a minor annoyance.
Switching between proton versions and native will delete your worlds and character profiles. Backup required.
Running on current proton (6.3-5) makes the game literally unplayable. I don't have an FPS counter, but I would wager the FPS was < 10. Running it natively runs perfectly fine, about as well as you would expect from Windows. ~50FPS on Ultra+ at 4k. Older proton versions used to work better, so YMMV if you run other versions.
Use Proton 5.0
SWITCHING PROTON VERSIONS DELETES SAVES. Beware if tinkering.
The game saves in two locations: ~/.local/share/7DaysToDie and .../SteamLibrary/steamapps/compatdata/251570/pfx/drive_c/users/steamuser/Application Data/7DaysToDie/. I backed up from the ~/.local/..., but the game does not read from that folder. You need to paste BOTH the 'GeneratedWorlds' and 'Saves' folders to the compat directory in order to load a backed up world. In other words, the game does not read from ~/.local/... when loading saves.
Update to my previous post. Most of it still holds true. Playing it natively has significant performance problems that are seemingly random and sporadic. FPS drops down to at least < 20 for random periods of time that seems to get worse at night (probably some sort of shader issue?). Finally got bothered enough to figure out which proton version I used to use. 5.0-10 is much smoother, holds the aforementioned ~50FPS and is overall a much smoother experience.
There is a significant flickering effect on the shadows throughout the day. Night seems mostly unaffected.
The game sometimes locks you into fullscreen, and the only way to escape is through a TTY or force-closing the game.
The game completely interrupts background tasks. Computer grinds to halt, sometimes freezing the entire desktop and requiring a hard reset. This persists even if I force close the game through htop or KSysGuard (System Monitor)
There are significant issues when connecting online. As a host, sometimes the game won't show for some people, but will show for others. We all have to keep restarting until it magically works.
The game is playable, but following the "stable" release, it has suffered from very significant issues. I cannot play this game and run background tasks, which significantly limits my ability to play this game, as I usually have stuff going on in the background for work or other creative purposes.
Playing this game with others is especially a pain, as there is some unknown issue that makes my host session unjoinable for some, and it requires 15-20 minutes of turning it off and on again for it to correct itself. It gets severely worse if anyone is using a VPN.
I genuinely don't recommend this game on Linux in its current shape. It's a damn shame because it used to be "tinkerable", but I have been unable to fix this game with the recent patch. Maybe someone with similar issues will one day figure it out, but it's slowly killing my drive, my friends' drive, and my fiance's drive to play this game. And it looks like the devs have "Welp, it's stable now" and dumped it for their new project.
Finally, the "1.0 update" changed nothing aside from making it prettier... again. So, you know where the dev's priorities lie. The game has never been amazing on Linux. So sadly, I won't hold my breath.
I forgot to mention, the game now has significant audio compatibility issues. I use pipewire, and if OBS is running when this game is launched, then the audio for the entire system is messed up. To fix, I have to close OBS, which is a significant problem if I want to switch to this game from another during a livestream. It is also an annoyance as it conflicts with other things on the system, although not as often as with OBS. Running OBS, after launching this game works though. Using qpwgraph to virtually disconnect the game from the speakers doesn't fix the problem.
This is not the DX version. If you bought it recently, check APPID 1502980
Minor FPS issues. Game is playable.
You will miss the beginning cutscene, but this is just the theme song that is one of the trailers in the store page. If you are new to Atelier, note there are usually two video cutscenes per game. The one at the beginning, and the one at the end. You may have to youtube the ending cutscene after you beat the game, but you will have no indication that a cutscene takes place as it simply skips it.
Every transition results in your camera zooming all the way out (even though the zoom is not stuck). This can be remedied by holding zoom in and alt-tabbing mid-zoom. Unfortunately, you have to do this every time you start the game.
WINEARCH=win32 PROTON_USE_D9VK=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
Works almost completely out of the box with the correct proton version and the FFXIII patch. I followed the instructions from this post -> https://www.protondb.com/app/292120#5VhnSA17zR
I changed the launch options as per more recent posts.
The text was a mess, I had to downgrade to proton version 7.0-6.
Finally, I used |# protontricks 292120 winecfg |, but you may not have to. I only ran it while trying to figure out the cause of the messed up text.
The game is notably quieter than other apps/games on my machine, but that could just be bad audio design. The game still outputs loudly enough that a decent headphone amp can pick up the slack.
Upon loading in the first chapter (mostly through the first cutscene) and sporadically thereafter, there are some significant lag spikes that slowly smooth back into a stable experience. As others have noted, it does not detract from the experience IMO either.
It took about 20 minutes for me to figure out how to get the game to run on my machine, YMMV. It is a long game, so the amount of tinkering required is negligible. I've played the first two chapters with no significant issues, and I will update my report should I come across anything game breaking.
Runs flawlessly
Considering running this in a VMware machine so that I can use Lossless scaling, but otherwise runs perfectly nearly OOTB. I use the launch option provided by the below user and Proton-20-GE.
VR mode does not work (Only tested with Linux v1.14 SteamVR beta)
No proton GE worked, and only one (6.3-7) mainline proton worked for non-VR. Even then launching is a coin flip. Did play so I cannot say for sure if the game would crash. Though, the problem seems to be a race condition to launch. Unfortunate. :( Will have to test more at a later date. If anything changes I will update here.
Didn't work. At all.
Didn't try on my main rig, so the specs are actually those of an MSI Creator 15 (RTX 2070 + Core i7 32Gb) running Arch Linux. And, I am willing to say that it might have been a driver issue.
Tried every version of mainline proton through steam, including experimental. Also tried Proton-Ge 15 through 20. No dice. Was meant to play the game with family, so I refunded it and unfortunately cannot test it on my main machine now.
-nolauncher
((CREDIT)) silentJET85
protontricks 203160 regedit
Then in Regedit, navigate to: HKEY_CURRENT_USER\Software\Crystal Dynamics\Tomb Raider\Graphics Create a new DWORD Value called MultiCoreFlushMode and set its value to 1.
Make sure to change the beta via 'Game properties'>betas>'build743.0 - TR build 1.01.743.0' . Played in 4k max settings with no issues aside from the occasional lag spike. Sometimes, however, I had to reload a checkpoint due to in-game bugs, which may or may not be present with native Windows play or a different build.
I tried unsuccessfully to install the unofficial KDE plugin via https://github.com/catsout/wallpaper-engine-kde-plugin. There are several forks that I tried with which I had no luck. The install script also currently creates the plugin in the wrong folder, and according to many people on the github, moving it to the correct folder yields mixed results. For me, it didn't fix the issue.
However, in my case, the AUR version (plasma6-wallpapers-wallpaper-engine-git) of the same plugin works straight up out of the box, so arch linux users running KDE may find it fairly easy. It may work with people running KDE 6 using distrobox, but I would think most people's best bet is via the link above.
The experience is not seamless in any way, nor is it equivalent to Windows, which is to be expected considering the complete lack of care from the devs. You can download wallpapers if you run Proton Experimental, but you have to use KDE's wallpaper menu to actually apply each wallpaper. Some wallpapers requiring special effects will be borked, and most that use any kind of zooming or cropping will just be zoomed out.
Fortunately, a lot of them do work in an aesthetic way. However, since you have to use two different applications, a la the actual launcher and KDE itself, people with larger libraries may have difficulties finding the wallpaper they want, and not all of their preferred wallpapers will work the way they expect from Windows.
All in all, worth it IMO if you already own the software and have access to the AUR. But manage your expectations well.
