FilBot3
Published
I used Proton-GE-6.18-2. I had issues with Proton Experimental.
I used Proton-GE-6.18-2 with Steam (Flatpak)
Because of EAC, this game is unplayable currently. Unless you like 2 minutes spurts with no friends.
While I had English Audio selected, it came out in Italian with English subtitles.
Let's me play for about 2 minutes, then disconnects me. Then kills the bot so my friend had less people playing with him.
Easy Anti-Cheat. It's the bug. Still doesn't work with Proton 6.19 GE-2
Easy Anti-Cheat, EAC, still is a problem. Couldn't get it to work with Proton-7.3-GE-1, only Proton EXP 7.0.
Using Flatpak, I insatlled the Proton GE flavor. Using Proton-Up is also possible. Then choose the GE-Proton version by forcing compatibilit
Sometimes processing shaders is slow. After about 10min of game play, it smooths out.
Cross-play is enabled. So I'm not sure if it's me that's slow, or them. It hink I loaded in faster.
Installed, nothing launched.
Using Flatpak Steam and Proton 6.5-GE-3, I was not able to get Destiny 2 to launch at all. Works on Google Stadia, but no cross-play.
The game defaulted to 800x600. I had to manually change the resolution to 1920x1080.
The game runs mostly fine. The launcher may seem sluggish at first, but once in the game, things seemed to work just fine.
Sometimes the mountains in winter maps show weird shapes, but they didn't seem to cause the game to slow, and the closer I got they filled in.
It seemed that after 1 1/2 to 2 hours the game would disconnect and not say it would. However, I wasn't able to interact with things and my friend's toon was just doing something repeatedly. I had to close the game and relaunch it to reconnect and continue playing.
Just the mentioned disconnect, no notification, and then nothing being able to be interacted with.
Just the disconnect issue where if you're not paying attention, you can get disconnected after a while and notice that you cannot interact with things. Then the game won't actually close when you logout, so you have to forcibly kill it. On GNOME, that's as easy as hitting Super, then closing the window.
I didn't do anything beyond install Steam+Proton and v5.09 on Fedora Workstation 32.
For some reason MWO would say my video card is unsupported even though it worked weeks ago on the same hardware under Windows.
This was fairly easy. Hardest part would be the installing the Flatpak and libraries.
The game pad, Google Stadia Controller, worked much better than it did with Windows. It would randomly glitch out and cause my character to go in circles in Windows. On Linux, no such problems. Other than that, it's just my skill at the game.
ALT+Tab would cause the game to be stuck in photo mode. Pressing ENTER then ESCAPE would make that go away. Doing this too much would cause the game to crash though.
After completing the main story line and watching the credits, the game now crashes after loading the ad for getting MH:W - Iceborne.
After completing the main story line and watching the credits, the game now crashes after loading the ad for getting MH:W - Iceborne.
Using Proton-6.8-GE-1 and also Proton-6.3-5 allowed the game to play the normal story line, but after completing it, now the game consistently crashes not allowing me to play it or get to any other menus.
UE4 Prereq x64 installing x86 package invalid ACL
The game is build on Unreal Engine 4 and it tries to install the x64 dependencies, but fails to do so because of some sort of Invalid ACL error.
The logs are: https://gist.github.com/FilBot3/598ee870b6b804ad2887a0857a76d18b
I then installed protontricks and tried to install vcrun2015 through 2019, but the later doesn't exist. Using Flatpak makes it a little tricky.
In the first area where the contract is accepted, and then in some of the exploration areas, there is jitteriness.
Upon talking to the chirurgeon on level two and waving the mouse around a bunch, the game will seemingly freeze up and I have to kill the process from the terminal.
Using Proton-6.9-GE-2, the game installed, started, and played fairly well. The only places the game seems to "chug" is in the non-combat zones where there is a lot of dialog. Once combat actually starts, it seemed to go fairly well. All controls worked as expected. The only part that has continually caused issues is dealing with the chirurgeon before the second mission. I have to coninually go through each dialog to get the upgrade, then waving the mouse around too much causes it to freeze.
Sometimes I would notice artifacts while loading, like other pieces of loading screens or random images appearing. Then while in the game, it was slow until I had received the notification that I was sailing seas with all players.
Sometimes clicking certain buttons wouldn't register so I had to use the keyboard shortcuts. Such as when trying to exit the application.
I think due to my hardware being from 2013, it could attribute to the issue. I am also running on an Nvidia 970.
I had to use an updated version of winhttp.dll and also use protontricks to set Sea of Thieves to Windows 7 instead of Windows 10.
I followed these sites/blog posts about how to get it setup. However, I did not install any special Proton runtime. I enabled Steam Beta, then used Proton 5.0.9 and then used protontricks and dropped that winhttp.dll into my steam folder.
https://www.reddit.com/r/linux_gaming/comments/gy90po/sea_of_thieves_is_now_working_on_linux/
https://gameriv.com/how-to-play-sea-of-thieves-on-linux/
However, your mileage may vary. Gotta be able to troubleshoot.
Introductory video and audio were out of sync, and teh video didn't play while the audio played while doing the first mission.
The introductory video for a new campaign showed the broadcast interruption screen, then the audio played, and continued to play all while I was starting the first mission. I did not wish to modify the game at all, so this video failed for me. There are reports of others with the video working after adding some media codecs.
Using Flatpak Steam and Proton 6.5-GE-3. The beginning video did not play, audio was off sync and continued to play during first minutes of first mission. Then everything else seemed to work as expected.
Would act like launching after shaders, but died.
I was able to install the game, and Steam Play started processing the shaders, but the game would act like it was launching, then die. This is the Steam version of the Titanfall 2 game, not through Origin Launcher.
I'm also using Steam Flatpak, and Proton 6.5-GE-3.
Glorious Eggroll
Some lag at first. Played mostly Frontier Defense. Game smoothed out afterwards.
When I tried to install Titanfall 2 Deluxe Edition via just Steam+Proton, the game would install, but not launch. However, when I installed Origin by adding a non-Steam game, then using Origin to install and launch Titanfall 2, the game worked almost flawlessly. I did experience some minor jitter at the beginning of each match, but after that, the game smoothed out for the rest of the match and I did not notice any glaring issues.
Mostly played Frontier Defense
I also used Proton GE 6.8-GE-2
I dont' know why ProtonDB is giving this a thumbs down, when it actually worked...
Doesn't seem to be working on Steam
The game installs, seems to start Ubisoft Connect, but then fails to launch. I don't know where people are getting the idea that this game works.
You will need to make sure you install the following application from your LIBRARY menu: Proton EasyAntiCheat Runtime before you try to run
Install Proton EasyAntiCheat Runtime from LIBRARY for this game to work.
Nothing shows up and game crashes.
I'm on Fedora 36 Silverblue using Steam Flatpak. GNOME kind of glitches, then it crashes. Doesn't work yet. There is a GitHub issue for the game as well.
The game does run on plain Proton. I think it runs better on GE-Proton, but others seem to get better mileage out of Experimental.
Sometimes the textures were weird even after building shaders.
When playing the Psyker, when I press 5 to melee attack with staff, my game would drag until the animation was done. Too much and it would crash.
If I played too long, or a power fluctuation would hit, the game would lock up. Then also randomly it would lock up and freeze GNOME entirely. I would have to restart gdm and then gracefully reboot to get back into the game, but at that point, just wait a bit.
Just the crashing during the game after long play periods.
Even with EAC, I was able to get on and play with my friends and randos. It was real fun. My game would seem to load much fater than those on Windows.
Turn the graphics down, and cap your FPS in the game to 60fps. When I used MangoHud on PC, I had multiple lock ups until I disabled it. I assume something to do with EAC and unhandled errors.
