Proton
Proton copied to clipboard
ValveSoftware
Titanfall 2 (1237970)
Compatibility Report
- Name of the game with compatibility issues: Titanfall 2
- Steam AppID of the game: 1237970
System Information
- GPU: AMD RX 580 8GB
- Driver/LLVM version: Mesa 20.3.3, LLVM 11.1.0
- Kernel version: 5.11.9
- Link to full system information report as Gist: https://gist.github.com/serebit/fd50035232b81e3547158553fa535fde
- Proton version: 6.3-1
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
Symptoms
- The Steam overlay is unavailable for some users, whether using a native runtime or the official Steam runtime. This appears to be the case for most Origin games. No known fix.
- Installing the game on a NTFS drive can render the game unlaunchable, with odd behavior from Origin as well. This can be fixed by installing the game on an EXT4 drive or similar.
- Using Proton 5.13 can cause crashes after about 45 minutes. This can be fixed by disabling esync via the
PROTON_USE_ESYNC=1env var. - Running the game in fullscreen can cause the game to be unable to reacquire fullscreen after alt-tabbing. This can be resolved by running the game in windowed borderless, if available.
- Windowed borderless (which must be enabled via config or Origin launch options) sometimes fails to work, leaving a border on the window. No known fix.
- "File corruption detected" error on launching the game. Toggling the language back and forth repeatedly can temporarily allow the game to run. No known fix.
Additional Comments
I am so happy that I can even make this issue. Titanfall 2 is one of my favorite games of all time, and to see it on Steam and running near flawlessly through Proton is a dream come true.
@serebit the game has run flawlessly through Wine with Lutris for a year at this point. But still, I'm also ecstatic, though... I can't get the game to run. I already have the Origin version, and it has run flawlessly from the moment I got it. I play it every day, I have about 1000 hours so far (all on Linux).
But I just installed the Steam version, and once I get to the Origin sign in, I enter my user ID and password, and then the Origin window pops up but it's completely blank, and nothing happens. I had to kill -9 ... every process to even get it to stop. I have no idea what the problem is.
Arch Linux 5.7.4-8-tkg-pds Proton 5.0-9
It's not letting me connect to Origin, that's the issue. The "Connecting to Origin" window just stays up indefinitely. When running standalone Origin through Wine, that window is present for like, 2.5 seconds and then it connects and Origin pops up. But on Steam, it's just indefinite.
So, I deleted the prefix, and tried again. And it worked. But I'd also changed desktop environments.
For some reason, this implementation WILL NOT work in i3wm. I've confirmed this at this point. I deleted the prefix, logged out and logged back into two other DEs (Deepin first, then GNOME) on the same installation. When I tried to relaunch the game (and since I deleted the prefix, redo the installation/Origin setup), it worked perfectly fine. After that, I logged back out, went to i3, tried again, and same problem as before. And again, All my actual Origin games (including Titanfall 2) work perfectly in i3. It's just the Steam+Origin games that won't. I tried GNOME, it worked there too.
That said, there is a terrible Mesa bug with Titanfall 2 that will cause ring gfx_0.0.0 timeouts and crash the GPU with (at least) Navi GPUs. You can't finish a full match. I've confirmed it with the Origin version as well. It used to not do that, either. But I've been using vulkan-amdgpu-pro and AMDVLK back and forth for Titanfall 2 the last few months, because they perform better than RADV. But RADV will cause GPU crashes on Titanfall 2 with both Steam and Origin versions. It wasn't present on 20.0 (or 19.3). With AMDVLK or vulkan-amdgpu-pro, the game runs perfectly fine, no crashes or anything. But that's a mesa bug, I suppose, so I'll take that up with them. But if anyone sees this and you have a Navi (or potentially other AMD) GPU then just use AMDVLK and you won't get crashes.
Hello @gardotd426, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Also, please clarify if you were using RADV/LLVM or RADV/ACO with the game.
Hey @hakzsam how's it going, Yes, ACO crashes. Menus are fine, but in 6 different tries, 3 on the Steam version and 3 on the long-installed Origin version, I couldn't complete a full match (matches are about 12-15 minutes). I reliably would get a ring gfx_0.0.0 timeout and driver crash.
This is not the infamous ring gfx Navi issue, as I actually have that issue with my other Navi card (5600 XT), that issue is generally not reliably reproducible, happens on the regular desktop, etc. This ONLY happens on Titanfall 2, ONLY with RADV, didn't used to happen with RADV, and is reliably reproduced.
As I said, I've had Titanfall 2 installed in Origin for almost a year now, and play literally every day. But about 2 months ago I started using AMDVLK and vulkan-amdgpu-pro because I got a bit better performance at the time, but before that I'd used RADV for months.
At first I thought the Steam version was just borked, since I'd been playing for hours on the Origin version literally right before my first attempt with the Steam version. But when I went back and tried the Origin version, making sure to change over to RADV, the same thing happened. Three times in a row. I went back to the AMD vulkan driver, and played another 4 hours.
I suppose I can try forcing LLVM (I always usually force ACO whenever I use RADV, and did in this case as well), but I don't know how hopeful I am. I mean at least I can play with AMDVLK/vulkan-amdgpu-pro, but most people don't know that's even an option, let alone how to switch back and forth, so hopefully we can get this sorted so no one else has this issue.
Obviously a renderdoc capture isn't a possibility here, so I'm unsure what I can try to gather for you all, aside from journald logs and proton logs. Oh wait, what about umr?
On Fri, Jun 19, 2020 at 8:53 AM Samuel Pitoiset [email protected] wrote:
Can you reproduce with RADV_PERFTEST=aco?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646619325, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y335XYB6CMCUYEINH5ADRXNNUVANCNFSM4OCFH2AA .
@hakzsam I just realized you may have been asking about it not working in i3, but since you're a mesa dev I assume you're asking about the driver crashes, lol.
I didn't know I could do that when the whole system crashes.
On Fri, Jun 19, 2020 at 9:28 AM Samuel Pitoiset [email protected] wrote:
Try to record an apitrace maybe?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646635655, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y33YGAYYLYJXBTDDVFJDRXNRXJANCNFSM4OCFH2AA .
EDIT: For those like me, where Mesa RADV es making the game crash. Install AMDVLK drivers and add this as launch options:
VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/amd_icd64.json:/usr/share/vulkan/icd.d/radeon_icd.i686.json" %command%
By some reason this only works on Xorg session and not Wayland
I'm playing the game on a GTX1050ti with 440.64 drivers on Kubuntu 20.04.
I had some issues with installing Origin initially, but I deleted the prefix and started over. The game now appears to run fine, but performance starts to drop over time, as well as audio channels , until barely any sounds are played at all. Also the game is likely to freeze when loading in that state. Entering a Titan appears to accelerate the problem? Need to investigate a bit more.
EDIT: Since he's now deleted his original, this was what I was replying to:
How do you do this? If I try using the amdvlk drivers with VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/amd_icd64.json" %command%, even origin won't boot...
@alosarjos yeah, and that's not going to work. Because Origin is 32-bit. You're only giving it a 64-bit driver to use.
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json.
@RalfVB how much VRAM do you have? You might need to go into the settings and lower the VRAM allocation. I've never seen this happen in 7-8 hour long play sessions on AMD cards either, so it could be an Nvidia driver problem.
@alosarjos for future reference, please don't delete your original post when you edit it. Leave the original, and add the edit at the end.
Anyway, using 32-bit RADV with 64-bit AMDVLK has caused numerous problems for me in the past. Just use 32-bit and 64-bit AMDVLK. VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json.
Amendment to my original post (and I'll edit it after posting this): the game has a problem getting into fullscreen. I don't know why, it's a bizarre behavior, but every time I click on the icon after alt-tabbing there's about a 10% chance it'll actually go into fullscreen. Most of the time it'll almost get there and then re-minimize.
Yeah, this is only present on the Steam version, the Origin version can alt-tab fine. But I've noticed the same behavior on the Steam version. It might be because you're supposed to add -noborder to the launch options and use borderless windowed mode, I'm not sure.
On Fri, Jun 19, 2020 at 10:46 PM Campbell Jones [email protected] wrote:
Amendment to my original post (and I'll edit it after posting this): the game has a problem getting into fullscreen. I don't know why, it's a bizarre behavior, but every time I click on the icon after alt-tabbing there's about a 10% chance it'll actually go into fullscreen. Most of the time it'll almost get there and then re-minimize.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646925518, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y33ZX23UVKCFU6JTT5ODRXQPILANCNFSM4OCFH2AA .
@gardotd426 This'll be interesting to check out. Borderless windowed mode did not work correctly on Windows for me; it introduced a ton of framedrops. We'll see if Linux handles this any better.
I ran borderless windowed mode on the Origin version for months and it ran at the full 144 fps at all times. You might have to disable vsync if you have it enabled.
On Fri, Jun 19, 2020 at 10:56 PM Campbell Jones [email protected] wrote:
@gardotd426 https://github.com/gardotd426 This'll be interesting to check out. Borderless windowed mode did not work correctly on Windows for me; it introduced a ton of framedrops. We'll see if Linux handles this any better. It seems like alt-tab works correctly, at least.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646926713, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y33Z72W5XBCN5536DQILRXQQPNANCNFSM4OCFH2AA .
Yep, borderless windowed works. I had to start the Origin client via the command line to change the game's launch options, but once I did? Flawless.
Ayyeee, I did a halp
On Fri, Jun 19, 2020 at 11:15 PM Campbell Jones [email protected] wrote:
Yep, borderless windowed works. I had to start the Origin client via the command line to change the game's launch options, but once I did? Flawless.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646929579, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y33YZPWIOUHCNYQ6EYVLRXQSWXANCNFSM4OCFH2AA .
There is actually one issue that I've found with borderless though-- occasionally the game will forget to render a certain area on the screen in the bottom right corner for about a second. Less annoying than being unable to alt-tab, though.
Are you sure that's not the Steam overlay trying to give you a notification and bugging out? I've never experienced this on Origin.
On Fri, Jun 19, 2020 at 11:24 PM Campbell Jones [email protected] wrote:
There is actually one issue that I've found with borderless though-- occasionally the game will forget to render a certain area on the screen in the bottom right corner for about a second. Less annoying than being unable to alt-tab, though.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646930748, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y33Z2YNQWBDZJHLIVVYTRXQTXTANCNFSM4OCFH2AA .
You'd think, but:
- It's not shaped like the Steam overlay indicator, it's above the bottom of the screen and about three times as wide as the indicator would be
- The Steam overlay doesn't work! :p
It doesn't work for you? I got steam overlay notifications in the short time I tried to play it on Steam (before the crashing started). I just went back to Origin because it's what I always play on, and I have all my launch options and stuff already set up with Origin. I mainly wanted to buy it on Steam just in case Origin ever borks itself on Linux, and to help contribute to Valve and also help incentivize the whole EA always releasing their games on Steam from now on thing.
On Fri, Jun 19, 2020 at 11:28 PM Campbell Jones [email protected] wrote:
You'd think, but:
- It's not shaped like the Steam overlay indicator, it's above the bottom of the screen and about three times as wide as the indicator would be
- The Steam overlay doesn't work! :p
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646931215, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y334QLGCKJZGIAYRKIC3RXQUGNANCNFSM4OCFH2AA .
Yeah, but this just happens with some games. I don't think it's specific to this game, it might just be my distribution.
@alosarjos for future reference, please don't delete your original post when you edit it. Leave the original, and add the edit at the end.
Anyway, using 32-bit RADV with 64-bit AMDVLK has caused numerous problems for me in the past. Just use 32-bit and 64-bit AMDVLK.
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json.
Oh, sorry. Anyways, with amdvlk origin just crashes.
Can confirm I also have the stuttering problem as mentioned in the OP. Basically a sort of stop-go stop-go stop-go stop-go, thing, where the "go" bits are really smooth, but it briefly pauses every second. This happens in the menus as well as in the game. Leaving it in the menus for 30 minutes to see if it was shader related did not improve it.
Manjaro, kernel 5.4.44 NVidia RTX 2060, driver 440.82 GNOME desktop (not sure if relevant)
@alosarjos It works perfectly fine for me. Been using it for months. Copy and paste your launch options here. Actually copy and paste, too.
@screwylightbulb try it with a different DE. GNOME has severe trouble with Titanfall 2 in my experience. I had to legitimately quit using GNOME because Titanfall 2 is my most-played game and it was unplayable with GNOME (and only GNOME).
If switching to another DE (make sure to list which DE it is) doesn't help, make sure Vsync is disabled.
I stay pegged at the 144 at 1440p with a 5700 XT. No stuttering whatsoever.
@alosarjos It works perfectly fine for me. Been using it for months. Copy and paste your launch options here. Actually copy and paste, too.
@screwylightbulb try it with a different DE. GNOME has severe trouble with Titanfall 2 in my experience. I had to legitimately quit using GNOME because Titanfall 2 is my most-played game and it was unplayable with GNOME (and only GNOME).
If switching to another DE (make sure to list which DE it is) doesn't help, make sure Vsync is disabled.
I stay pegged at the 144 at 1440p with a 5700 XT. No stuttering whatsoever.
I've tried the different 32 and 64 bit version of Mesa RADV and AMDVLK. Now, I'm on Gnome... So maybe there is something there... Thing is. Going full mesa, game will just crash, I'm unable to finish a single match without crashing (AMD 5700). Using AMDVLK for the game and mesa for Origin will boot, but only on Xorg session, on Wayland the game tries to launch, showing a window in black, and then crashes and everything closes. Tried AMDVLK for both game and origin, origin will become a black window and crash.
Right now the only way to play this on my PC is going into Xorg session, using Mesa RADV 32bits for Origin and AMDVLK 64 bits for the game.
All this on an updated Arch, BTW
@gardotd426 I tried a plasma session as well as a bare bones openbox session, and I even tried to swap out the login manager from lightdm to sddm. Same behaviour in all cases.
I can run other heavy-ish games like Batman: Arkham Knight without any issue.