But when I went back and tried the Origin Playing for hours on the Origin version literally right before my firstĪttempt with the Steam version. But about 2 months ago I started using AMDVLKĪnd vulkan-amdgpu-pro because I got a bit better performance at the time,īut before that I'd used RADV for months.Īt first I thought the Steam version was just borked, since I'd been Titanfall 2, ONLY with RADV, didn't used to happen with RADV, and isĪs I said, I've had Titanfall 2 installed in Origin for almost a year now,Īnd play literally every day. Reproducible, happens on the regular desktop, etc. With my other Navi card (5600 XT), that issue is generally not reliably This is not the infamous ring gfx Navi issue, as I actually have that issue #ORIGIN OVERLAY NOT WORKING TITANFALL 2 DRIVER#I reliably would get a ring gfx_0.0.0 timeout and driver crash. #ORIGIN OVERLAY NOT WORKING TITANFALL 2 FULL#Version, I couldn't complete a full match (matches are about 12-15 Menus are fine, but in 6ĭifferent tries, 3 on the Steam version and 3 on the long-installed Origin 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. But that's a mesa bug, I suppose, so I'll take that up with them. With AMDVLK or vulkan-amdgpu-pro, the game runs perfectly fine, no crashes or anything. But RADV will cause GPU crashes on Titanfall 2 with both Steam and Origin versions. 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. I've confirmed it with the Origin version as well. 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. It's just the Steam Origin games that won't. And again, All my actual Origin games (including Titanfall 2) work perfectly in i3. After that, I logged back out, went to i3, tried again, and same problem as before. When I tried to relaunch the game (and since I deleted the prefix, redo the installation/Origin setup), it worked perfectly fine. I deleted the prefix, logged out and logged back into two other DEs (Deepin first, then GNOME) on the same installation. But I'd also changed desktop environments.įor some reason, this implementation WILL NOT work in i3wm. So, I deleted the prefix, and tried again. 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. I am so happy that I can even make this issue. This can be fixed by installing the game on an EXT4 drive or similar. Installing the game on a NTFS drive can render the game unlaunchable, with odd behavior from Origin as well.This appears to be the case for most Origin games.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |