ValveSoftware / ValveSoftware/Proton
Titanfall 2 (1237970)
Open
Nobody has claimed this yet.
Game compatibility - Unofficial
Regression
XAudio2
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
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:
- that I haven't found an existing compatibility report for this game.
- 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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the listed launch, overlay, filesystem, fullscreen, and file-corruption symptoms with Proton 6.3-1 and the reported system details. A useful contribution would need to narrow the report to one reproducible failure and establish a validated resolution; no source file or test is named here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100