Comment on page
If you're encountering issues with Northstar launching on Steam, a very quick fix that usually works is deleting the compatdata for Titanfall2.
You can do this by going to your Steam directory, going to
steamapps/compatdata, then look for the folder called
1237970(the App ID for Titanfall2). This folder contains the data used by Steam in order to make games function using Proton (assuming you're using Proton for said game). This folder, however, sometimes has issues with launching Northstar.
It is recommended you close Steam before this. Deleting this folder then attempting to launch Northstar with NorthstarProton again should fix the issue. Steam will generate another
compatdatafolder for Titanfall2 automatically.
If you have already logged in to EA App with Proton Experimental, the blank EA App should not prevent you from playing Northstar. However, if you find that it does or if you simply wish to use the EA App, the following should resolve these issues.
- 1.Make sure that you have protontricks installed
d3dcompiler_47into your Titanfall 2 Proton compatdata.
- 1.For SteamDeck (and Protontricks Flatpak), run
flatpak run com.github.Matoking.protontricks 1237970 d3dcompiler_43 d3dcompiler_47in a terminal session (Konsole on SteamDeck).
- 2.Otherwise, run
protontricks 1237970 d3dcompiler_43 d3dcompiler_47in a terminal session.
This guide is for pipewire-media-session, not wirepluber which has a different location and is formatted in LUA.
Before, copy all the necessary configuration files:
mkdir -p ~/.config/pipewire/media-session.d/ && cp /usr/share/pipewire/media-session.d/alsa-monitor.conf ~/.config/pipewire/media-session.d && cp /usr/share/pipewire/pipewire.conf ~/.config/pipewire/
Restart PipeWire after each step.
- 1.Enable sample rate switching.
#default.clock.allowed-rates = [ 48000 ]to
default.clock.allowed-rates = [ 44100 48000 ]in
- 2.Disable suspend.
#session.suspend-timeout-seconds = 5to
session.suspend-timeout-seconds = 0in
If the above doesn't help, you can also try:
- 3.Setting alsa headroom (
#api.alsa.headroom = 0to
#api.alsa.headroom = 1024.
If it doesn't solve the issue try 2048 however if it does try lower values: 512, 256, 128, 64, 32. Use a lowest value that works.
- 4.Changing the alsa period size (
#api.alsa.period-size = 1024
#api.alsa.headroom = 0
api.alsa.period-size = 256
api.alsa.headroom = 1024
If it doesn't solve the issue try different values: 2048, 512, 256, 128, 64, 32. Use a lowest values that works.
Running the game on fullscreen through Linux might lead to a black screen preventing you from launching the game. Edit your
-noborder -windowor edit
<wineprefix>/drive_c/users/<username>/Documents/Respawn/Titanfall2/local/videoconfig.txtto solve this.
You may feel that the game stutters frequently during the first hour of play. This is normal, it's just DXVK having to compile shaders at draw time due not having a ready state cache. The more you play, the less stuttering there will be in the future.
Proton: extract and put it in
~/.local/share/..or next to .exe if shader pre-caching is turned off.
Wine: extract and put it next to game's .exe. Also remember to rename it if the .exe has a different name.
DXVK-async is automatically installed and enabled if using the NorthstarProton runner.
Download dxvk-async, extract and put it in
~/.local/share/lutris/runtime/dxvkthen type the name of the folder in
DXVK version, to enable add
/path/to/steamapps/compatdata/1237970/pfx/drive_c/users/steamuser/Application Data/Origindefault is
Access can be restricted using a file manager or terminal:
chmod -R 555-> access only
chmod -R 755-> access + save
It's also possible to create command aliases to type something short, such as tfoff/tfon.
If you ever used ReShade together with Titanfall2 in the past it will have created a bunch of DXVK DLLs that are incompatible with Northstar. If Northstar fails to fully initialize with an exeption and you have previously installed ReShade on Windows delete the following files from