


Run ME3Tweaks Mod Manager with Lutris to install mods.
The game itself is able to run with Proton out of the box without tinkering. However, if you want to install mods, extra steps are required to run the mod manager, ME3Tweaks Mod Manager, and install mods to your game on Linux, since the mod manager does not support Linux. You may refer to Parilia's guide for running ME3Tweaks mod manager with Lutris on Linux, which is based on SLABBY's guide for running ME3Tweaks Mod Manager on Steam Deck.
On the other hand, the game's save editor, Trilogy Save Editor, has a Linux version available.

gamescope -W 2560 -H 1440 -f -r 240 -m 100 --force-grab-cursor --hdr-enabled -- %command%
Without Gamescope launch commands, HDR was not detected. When forcing HDR this way, the mouse became unbound with a practically infinite DPI. Above Gamescope commands were used which fixed.
Worked fine out of box through Proton Hotfix. "gamescope --hdr-enabled -- %command%" was needed to force HDR detection, but this caused the cursor to be unbound and sensitivity to be virtually infinite. Added the recommended fix to launch parameters, "--force-cursor-grab", but this prevented game from launching at all. Read that this often has to do with scaling so I forced scaling to 100% with "-m 100" which did the trick. The working string for me is as above, but it's clear from reading that not all of it will apply to everyone's system.

Text can be small to read, nothing unbearable
During some cut scenes there were a few hiccups, but I haven't modified any settings yet to try and help with that.
I recently had logged into the EA servers for another game so when Mass Effect started installing the EA app and launcher it didn't give me a prompt to sign in, it was like it retained my information. I'm not sure if that made it more stable, but just wanted to include that info. I was also a little surprised at the screen resolution and how it changed during the EA app install portion. It looked like it was a 4:3 ratio during install and had an antiquated appearance. I've never played the Mass Effect games, but it did look quite different from "It Takes Two" the game I recently logged into my EA account with.

Works great out of the box
Alt+Tab results in key binding issues and the like
Only minor issues with key bindings messing up after alt+tabbing.

Used to work fine without changes until Saturday, July 19, 2025. EA launcher broke it. To fix it, go into desktop mode, go to EAs website and download the EA desktop app. Then run the installer using protontricks. It took a couple of tries, but it eventually installed.
See notes
If using Bluetooth controller, the main launcher requires the controller order to be swapped to select which game to play.
Initially worked fine for me out of the box with the default proton. When the EA app updated recently the game wouldn't launch and I had to switch to an older version of proton in order to get the EA app working again. A previous report indicated 7.0-6 worked for them. For me this didn't work but 8.0-5 did so some experimentation seems to be required.

After the 7/13 update of the EA App, the game would no longer launch. After common troubleshooting methods i ran EAupdater.exe in proton and got all the way through the update that launched the de-stager which failed. I discovered that the files were already decompressed, so I copied the files from /home/{X}/.steam/steam/steamapps/compatdata/1328670/pfx/drive_c/Program Files/Electronic Arts/EA Desktop/StagedEADesktop/EA Desktop/ to /home/{X}/.steam/steam/steamapps/compatdata/1328670/pfx/drive_c/Program Files/Electronic Arts/EA Desktop/EA Desktop/ and overwrote the files, essentially applying the update manually which got it working again.
I was able to fully mod ME:LE on linux by running ME3Tweaks in a windows10 installation in Oracle VirtualBox and sharing my game folder and my mods folder.

Force proton experimental to avoid crashes. Default proton didn't work sometime and the game wouldn't launch
__NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA-only __GLX_VENDOR_LIBRARY_NAME=nvidia %command%
The default proton steam recommends doesnt launch the game sometimes and just crashes. Forcing proton experimental fixed the issue and launched the game correctly everytime

Played through all 3 games, no issues whatsoever.
A few in-game glitches not but nothing Linux specific (not graphical or slow-down related).

DXVK_ASYNC=0 %command%
Pardus(Debian) / Gnome wayland / Steam / Proton Hotfix + Türkçe Yama ile oynadım. Başlarda sadece ana menü açılıyor ama oyuna geçiş yapmaya çalışınca çöküyordu, çalıştırma kodunu saçma bir şekilde steam'e tanımladıktan sonra açıldı. Normalde DXVK 0 değil 1 olması gerekiyor ama bende bu şekilde iyi çalışıyor.

The EA Launcer couldn't complete it's initial install/setup with the default proton so I had to switch to Proton7.0-6 for the install to work. After that I had to switch to GE-Proton9-27 for the game to work. Every so often the EA Launcher had an update and I had to switch back to 7.0-6 for the update then back to GE9-27.
From time to time, usually after talking to aother character. I would get a large framerate drop. If that didn't clear up by itself, I would just save then restart the game. This happened quite often in the first game, a few times in the second game and only twice in the third game.

mangohud %command%
Had to use proton 7.0-6 to get the EA app to install. After that everything works wonderfully under GE-Proton10-4
When I pause the game and the screen automatically locks after a while, the game crashes on login.

ME2: Runs almost without issues.
When scoping with snipers, I had to move the mouse fast enough to register.
Also if I exit the window and return to it, the mouse would not be bounded to the window and would be able to escape to the other monitor. This could be esily fixed by opening and closing the EA overlay with Shift+F1
The game crashed about 4 times during the gameplay. 3 of the crashes were in one exact cutscene. On the fourth try, the cutscene would go trough.
About year ago I couldn't launch because of the EA app. Recently it started working with Proton 8. Than it suddently stopped working, but the steam default proton started working.

The stupid EA App is having occasional seizures
Finding which version of proton to run the EA App on was a PITA
Main issue is finding which version of proton to use. Although people list 9.0 as a working version, it didn't work for me. I tried the other ones that are recently mentionned (Experimental, 10 GE) but the one that ended up not making the EA App crash or hang while waiting for the game to start was Proton 8

Used ProtonUpQT to get GE 10-4, works perfect. Proton Experimental/Hotfix did not work for me, 8.0-5 worked but was VERY slow starting and loading games.

Infrequent crashes. They happen quite rarely, and I have idea whether they're Linux-related.
No performance issues at all. As mentioned above, the game does sometimes crash, but only rarely. There is definitely some forced mouse acceleration/smoothing that I needed to disable via mods. Modding works great with the ME3Tweaks Mod Manager run through Protontricks. If you're running an ultrawide monitor, the black bars in cutscenes can be removed with FlawlessWidescreen, which is available if you run the game with SteamTinkerLaunch as the compatibility tool in the game's properties on Steam, and enable the FlawlessWidescreen option in its settings. For me, I have to manually reapply the fix in the FlawlessWidescreen application each time the game launches, and it only applies after tabbing out and back into the game a couple times.

To reach the login screen, I had to launch the EA Desktop client manually using Protontricks:
protontricks -c "wine 'C:\\Program Files\\Electronic Arts\\EA Desktop\\EA Desktop\\EADesktop.exe'" 1328670

Proton GE 10.4 seems to work flawlessly for this game. I was able to install the EA app and run the game in a single Proton version.
gamemoderun %command%
Completely playable with the lated GE build. I used ProtonupQT to install 10.4. 10.4 allowed the EA app to install and for the game to run.

Game launches EA App prior to starting the game. I managed to login to EA, but it never launches the game, it always dies before starting.
I tried installing EA App via lutris and as non-steam game. game stil didn't lunch
Just don't bother

Works pretty well, although it drains battery fast without lowering the graphics and using FSR
Lowered resolution and used deck's built in FSR

The game itself works like a charm. The mandatory EA App, on the other hand, is a pain to install.
As of the time of writing this, the EA App will not install while running on the current version of Proton, and will exit out with an error code. If this happens, try using older versions until you find one that works. I had major success using Proton 8.
After the app is installed, you can safely exit out and switch to the latest version of Proton, and the game will run perfectly fine.

gamemoderun %command% DXVK_ASYNC=1 %command%
Uninstalled and renistalled and appeared to get further with launcher switched to indicated proton version and was able to play ME1 untill I realised I don't like TPS games

Tried alot of variations. Got to the create an EA login screen, successful but thats it. I see a launcher screen briefly and it crashes
I am using AMD APU only

Some levels have minor performance issues, Citadel is slightly choppy when entering rooms with a lot of NPCs. So far after 8h one of the planets had major FPS issues. Rest worked flawlessly. Only played ME1 so far.
Some occasional performance issues, but they could be caused by this being an old game. Haven't had problems with EA, left it on.

Perfect out of the box. 4k resolution.
I only played ME1 for two hours. It is perfect out of the box, at 4k resolution.

Added holster button.
Launcher must be run at least once in desktop mode.
Some text may be difficult to read for visually impaired people.
Recommend setting max FPS to 45 for framerate stability.

VKD3D_FEATURE_LEVEL=12_2 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 DXVK_ASYNC=1 %command%
Did not try without launch options. Worked without any issue and performed flawlessly. There was about a 30 - 45 sec black loading screen with audio after selecting one game from the 3 available games.

the ea-app installs fine with proton 7.0-6 after the game stopped (crashed) it runs fine with proton experimental or ge 9-26
gamemoderun %command%
just the loading time takes a little long it could be useful to delete compatdata at the beginning

gamemoderun %command%
Finished all 3 games. Sometimes the games don't start (EA Launcher fail to start), but usually i simply restart it and it runs.

Doesn't launch
Shows EA loading bar and than just exits.

Game still has bugs from original ME3 like the shield bug. Simple fixes below resolve issues. Gamescope fixes 60 FPS limit bug.
LD_PRELOAD="" gamescope -W 2560 -H 1440 -w 2560 -h 1440 --fullscreen --force-grab-cursor -- game-performance %command% -game 3 -autoterminate
Disable both Steam and EA overlays. Steam can be done via the game properties in Steam, for the EA launcher you have to edit the config file located at "~/.local/share/Steam/steamapps/compatdata/1328670/pfx/drive_c/users/steamuser/AppData/Local/Electronic Arts/EA Desktop/user_********************.ini". The .ini number string is 20 characters long and is unique to your own EA account. Add "user.igoenabled=0" to the end of this file to disable the EA overlay completely for ME LE.
Mouse sensitivity is still tied to FPS, an old ME3 bug. At higher rates than 60 FPS, mouse sensitivity will slowly decrease the higher the FPS goes. At higher FPS limits like the recommended max 144 FPS, you may have to increase sensitivity ingame, just adjust to your preference.
First, without gamescope, game was limited to 60 FPS max no matter what settings I tried in game. Also, the old "shield" bug from original ME3 release is actually still present even in the LE version, but instead of 60 FPS, the new limit is 144 FPS. Setting the FPS limiter in the game higher than 144 FPS will result in slow shield recharge, and enemies being able to aim much faster. Game logic is still tied to FPS. Simply disable vsync and set the in game FPS limit in settings to 144 (or whatever is lower than your monitors refresh rate!) to fix the bug.
Without gamescope, game feels stuttery even at the 60 fps limit. Gamescope fixes this, and game runs flawlessly on my hardware in all 3 games at 144 FPS. I have completely beated ME1 and ME2 in linux, and am playing ME3 now. Also ensure you force proton experimental otherwise ME3 will freeze on launch with blackscreen if you use the default proton-cachyos, ME1 and ME2 were not effected. In launch flags, "-game 3 -autoterminate" will skip the game launcher entirely and load directly into ME3, and then exit to desktop on quit. Change the number in the launch params to whatever game you are currently playing.

Launcher would not always recognize input
Small text
Some audio would cut out completely if you stayed in a conversation too long.
Can only use one input at a time in launcher. Make sure to set as priority controller
Games played at 900p with FSR enabled.
45fps, 9Watt limit, lowered resolution to 960 x 600 and used fsr at sharpness 3.

Runs flawlessly with no issues. Sadly the EA launcher popup breaks mangohud, so no FPS or frametime statistics because of DRM.
game-performance %command%
Game runs fine on default proton, no need to run on CachyOS to get it to run.

MANGOHUD=1 DXVK_ASYNC=1 gamemoderun %command%
Massive stuttering and frame drops occurred randomly.
The game required several launches to get the EA launcher working properly, so don't be dismayed if it doesn't work the first time. The only major downside is massive frame drops and stuttering, but I believe this to be a problem inherent to Legenary Edition even on Windows. It runs well with both Proton experimental and GE.