


12-14w TDP + 40 FPS/40HZ refresh rate
Once, the audio desynced during a cutscene sequence by about 10 seconds. Restart fixed
There was a wierd fog/lighting effect that entered the ship on the ice planet.
To all who said the game runs at 40FPS at 10W TDP, I call bull.
At 14W, there are times where the game struggles to maintain 30-35 FPS, especially on Kashyyyk and Dathomir. During the final boss encounter, there's a section where you're running while the base is falling apart, and my FPS stuttered into the 20s.
That said, the game was overall a mostly enjoyable experience.
EA Game Launch Tips
If you haven't yet run an EA game, follow these steps:
- Switch to Desktop Mode.
- Open a browser and log in to EA's website.
- Link your Steam account—this makes launching EA games a lot easier.
One could use the following launch command, which will SKIP the EA launcher entirely, but you may not get Achievements.
cmd=( %command% ); cmd[-1]="$STEAM_COMPAT_INSTALL_PATH/SwGame/Binaries/Win64/SwGame-Win64-Shipping.exe"; "${cmd[@]}"
Performance & Graphics Settings
- 40FPS with occasional dips to 30-35 FPS as noted.
- Resolution: 1280x800
- Settings: Medium
- Dynamic Resolution Scaling: Off
- Motion Blur: Off
Alternative Tests
- 1152x768 (Performance Settings + FSR Enabled): Looked fine, but I preferred native resolution, as performance was mostly the same.
- Low Settings ("Custom" Trick): Looks awful, especially the shadows.

Switched to Desktop Mode
If you're on a Steam Deck or using ChimeraOS or Bazzite, switch to Desktop Mode to set up the EA App

Had constant issues with stability and audio when setting the maximum framerate to greater than 60, but it worked basically flawlessly at with the maximum fps set at 60.

cmd=(%command%); cmd[-1]="$STEAM_COMPAT_INSTALL_PATH/SwGame/Binaries/Win64/SwGame-Win64-Shipping.exe"; "${cmd[@]}"
Renamed installScript.vdf
so that the EA App doesn't get installed.
EA App
As usual with any EA game on Linux, the biggest potential problem here is the infamous EA App. In this instance, it prevented me from using the Steam overlay, and my controller did not work properly when it was running. So, I took the following actions:
- Reinstalled the game entirely (I deleted the Proton prefix in
compatdata
as well to be sure) - Before even launching the game a single time, renamed
installScript.vdf
so the EA App does not get installed upon first-time launch. - Changed the launch command. It replaces the binary in the Proton launch command so that it bypasses the EA App and boots straight into the Unreal binary.
The biggest downside to this is that you won't be able to unlock any achievement. However, don't worry about it too much, since these barely work with the EA App anyway, and a quick google shows that Windows users have tons of achievement problems as well. If you really need achievements, just unlock 'em with one of those achievement tools. The game works way better with the EA App disabled.
Performance
Overall, the game performs really well. Despite this being a DX11 game, I was able to crank out a pretty solid 100fps for most of the time at 3440x1440 with everything on max settings. There are a few areas on a certain planet that can tank performance a bit, but never under 70fps. It's a great experience, the game runs well, and looks really great.
The game's sequel, Jedi Survivor, is infamous for having serious stuttering issues. This game also suffers from this unfortunately, although to a lesser degree. And based on my own observations, the issue is less pronounced on Linux with DXVK.
Ultrawide support.
The game has ultrawide support, but no FOV slider and unfortunately does pillarbox cutscenes (even though 99% of them are in-game). There's a fix out there by RoseTheFlower over on Github and WSGF, but I could not get it work on Linux :(

It runs surprisingly well. It should be a platinum but due to EA launcher the current gold rating is still appropriate
--SteamOS Settings--
Frame Limit: 45 FPS (90Hz)
TDP Limit: 10 Watts
GPU Clock: 900 MHz
FSR: 2 Sharpness
--In Game Video Settings--
Window Mode: Fullscreen
Resolution: 1152x720
Max FPS: 45
HDR: OFF
VSync: OFF
Dynamic Resolution Scaling: ON
Graphics Quality: Medium
Did get a pop up about EA cloud save during testing so I recommend quitting to menu then quitting the game
I got a working 60 FPS but went down the route of battery optimisation

This type of UE4 works great. I'm glad to see steady 60fps at native 1080p resolution on ARC cards with no performance issues!
DXVK_FILTER_DEVICE_NAME="Intel(R) Arc(tm) A580 Graphics (DG2)"
What can I say? UE5 is a downgrade. Shame on Epic that is not definitely Linux friendly. Well, at least, if we didn't had time to play these relatively older titles, now it's the time, because they are even more affordable in terms of costs. Bought the key from CD Keys store by the way. Very convenient.
Crash at 9 hours, entering new area. Error message: LowLevelFatalError [File:Unknown] [Line: 3365] Pak Decompression failed.
"/mnt/9e35f787-a028-48b8-8f0e-9eda11669830/SteamLibrary/steamapps/common/Proton - Experimental/proton" run "/mnt/9e35f787-a028-48b8-8f0e-9eda11669830/SteamLibrary/steamapps/common/Jedi Fallen Order/SwGame/Binaries/Win64/SwGame-Win64-Shipping.exe"; killall -9 SwGame-Win64-Shipping.exe # %command%

Steam overlay does not function.
Game runs perfectly on my system, apart from Steam overlay not working (a bummer if you ask me). Other than that the experience has been flawless: good and consistent frame rate, no stutter or lag detected.

While the sound issue with headphones is annoying, the performance and gameplay works well at 30FPS
In-Game fps set to 30
Have to sign into EA account at least once, easiest to do this in Desktop mode
Databank entries can have small text and are very difficult to read if the game is not played at native resolution
Only sound issues appear when I open the Menu
Fog is an issue even on higher graphics settings. There are times when entering the ship the NPCs will appear to be in complete shadow no matter the amount of light
Had one instance going from Windowed to Fullscreen that the game would then not recognize my controller and took going into Desktop mode until I was able to fix the issue. Continued to play the rest of the game in Windowed mode without significant issues
Issue with controller only happened when changing from Windowed to Fullscreen once. Since then no more controller issues have ocurred
Performance always lags when pressing Start and navigating the menu, FPS goes down to ~24fps no matter the settings and sound will crackle
I played the first 70% without a crash, then I had a few issues in Dathomir but that could have been due to changing other graphic/display options.
This issue was only when trying to use headphones and might be an issue with my device specifically, but when plugging in headphones the volume would get stuck at whatever the sound was set to BEFORE launching the game. If the volume was at 20% and I launch the game, the volume up and down don't actually change volume, the slider will appear but the volume will stay at the same 20%. I would need to quit the game, move the volume to what I wanted it to be and relaunch for the volume to be at what I wanted.
Playing at 30fps I was able to set Graphics to High, except for Shadows (Medium) and the game ran relatively solid throughout except for the menu, but that was annoying and didnt stop me from enjoying the rest of the game

"/path/to/steamapps/common/Proton - Experimental/proton" run /path/to/steamapps/common/Jedi\ Fallen\ Order/SwGame/Binaries/Win64/SwGame-Win64-Shipping.exe; killall -9 SwGame-Win64-Shipping.exe # %command%
I needed to use advice from other users on bypassing EA launcher, which would not install properly.

In the first two hours, the game runs absolutely fine with 1920x1080 @ 120Hz in maximum settings. Nothing negative to say.
During the first start, there are some windows where I had to create an EA-Account…this took about a minute. For someone who has an account already, it's just a login.

A flawless and blurry free experience with the right settings for the game and the Steam Deck. Check down below to set graphics to LOW
DXVK_ASYNC=1 %command%
Disable Frame Limit and set the display to 40 Hz, Allow Tearing and Limit TDP to 10. Running from the SD card
With some settings to LOW we are sitting on 20W from 23W that was draining before, stuttering is fixed and game looks really sharp.
Temporal AA adds a great cinematic effect, but I preffer sharpness over this effect, also there are many textures that do really pop up now, so IMO game is a lot more enjoyable without Anti-Aliasing
As you may know if you already played this game before, graphics cannot be lowered from MEDIUM and there's no way to disable Temporal AA which makes the game a washed out and blurry fest. Thankfully there's a workaround:
- Enter Settings -> Video -> and hover over "Graphics Quality" which are the presets
- Press A to select it, and then press B without any other input between. This'll set all settings to LOW and disable AA
Here is my settings list:
Max FPS 45 (Irrelevant)
Vsync: ON
Dynamic Resolution: OFF ( Game looks really bad with this on and the deck is more than capable of delivering a native resolution)
View distance: MEDIUM
Shadow Quality: LOW
Anti-Aliasing: OFF
Texture Quality: HIGH
Visual Effects: MEDIUM
Motion Blur: OFF (I usually play my games with this but this game looks really blurry)
Film Grain: OFF
Chromatic: OFF
Camera Shake: ON

Had some minor FPS drops during the tutorial but that could also be owed to my hardware. Did not encounter any issues otherwise.

DXVK_CONFIG_FILE=~/.config/dxvk.conf %command%
In order to solve the severe performance issue with the game's menu you have to create a dxvk config file with the following entry: dxgi.maxDeviceMemory = 4096
, where the number is something a bit lower than your GPU's VRAM in MB. In my case the VRAM is 6144 MB, so I chose above value.
Current Proton Experimental is already a bit better in regards to the menu performance issue, but after opening the menu several times still slows to a crawl without the config fix.

Works fine if you never open the menu
Game slows to a crawl after entering the menu. This can sometimes be fixed by quickly pressing the menu button several times in a row, but it's a lottery. Best to use the menu as rarely as possible, and "Quit to Title" after to get the game running normally again. Can sometimes also happen after entering the ship.
Since the menu is mostly for customization and lore you can schedule it so you do all of that reading and customizing at once, then reload the game so it's fast again.

The game freezes for a second or so when I exit the menu.
Works great out of the box so long as I don't add any launch options, maybe the EA app doesn't interact well with those?

Works OOTB
Faced some minor stutters in the prologue and upon reaching Bagano, but nothing unbearable
Managed to install, open and play the game without any issues. Went from the prologue to the Bagano vault and I had a flawless experience so far. Actually kind of surprised, I thought there would be some compatibility issues with the EA launcher

With the menu FPS bug, there is no way to actually play the game since menu is required to follow upgrade etc
"~/.steam/steam/steamapps/common/Proton - Experimental/proton" run "~/.steam/steam/steamapps/common/Jedi Fallen Order/SwGame/Binaries/Win64/SwGame-Win64-Shipping.exe"; killall -9 SwGame-Win64-Shipping.exe # %command%
Game starts and works at 60 fps (capped) , as soon as you open the start menu and close it again, it degrades immediately to <40fps.

运行稳定,帧数保持流畅,游戏也很棒。就是资料的字体太小了,字幕倒凑合看。80%60fps, 19%48-60fps, lower than 30fps when lanch new map.
菜单界面里的各种资料收集物的文字太小了,无法完全渲染清楚,就算插了显示器也是看不清的。Menu library words too small.

No issues, works like native
I see some people have issues but i havent had any yet.
"~/.steam/steam/steamapps/common/Proton - Experimental/proton" run "~/.steam/steam/steamapps/common/Jedi Fallen Order/SwGame/Binaries/Win64/SwGame-Win64-Shipping.exe"; killall -9 SwGame-Win64-Shipping.exe # %command%
Ea laucher fails to install, even with older versions of proton.

I tried all the combinations, as said by previous reporters, to no avail.
~/snap/steam/common/.local/share/Steam/steamapps/common/Proton - Experimental/proton" run "/PATH/TO/STEAM/steamapps/common/Jedi Fallen Order/SwGame/Binaries/Win64/SwGame-Win64-Shipping.exe"; killall -9 SwGame-Win64-Shipping.exe # %command%
Tried every solution provided by previous reporters, to no avail. The game still don't launch.
At game launch, the first time the EA client app appears, runs some updates and downloads some libraries, and it keeps running for about 3~5 min, after which it dies. After that, the EA launcher doesn't ever appear again.

45 FPS in game cap and quick access 45 Hz cap.
flickering textures while half rate shading is on
Weird problem with resolution being broken on start (4:3 with small res). Can be fixed by changing window mode to fullscreen again while in game. This probably happened because of steamOS 3.6 update.
When moving to the new location stutters to 10 FPS (game installed on SD card)
medium settings with high textures, variable shading off. dynamical res on or off depending on area.

"/PATH/TO/STEAM/steamapps/common/Proton - Experimental/proton" run "/PATH/TO/STEAM/steamapps/common/Jedi Fallen Order/SwGame/Binaries/Win64/SwGame-Win64-Shipping.exe"; killall -9 SwGame-Win64-Shipping.exe # %command%
After installing the game via Steam, the game would not start. Only an EA launcher pop up would show for a split second. I tried various versions of Proton / GE Proton without luck. Runs like a charme after i applied the workaround @ShadowyBear mentioned in their contribution.

Game launched but does not register steam deck as x-input controller. Tried Default Proton, Experimental and Proton GE.
Only way I could get the game to launch was to map the controller as K+M

There is a strange issue with the fog that casues to to be higher than it should as well as some minor lighting issues. Overall still fun and enjoyable.

Played with Steam Controller, no issues, great performance.

"/home/YOUR-USER-NAME/.steam/debian-installation/steamapps/common/Proton - Experimental/proton" run "/home/YOUR-USER-NAME/.steam/debian-installation/steamapps/common/Jedi Fallen Order/SwGame/Binaries/Win64/SwGame-Win64-Shipping.exe"; killall -9 SwGame-Win64-Shipping.exe # %command%
The game wouldn't recover/pull save games from Steam Cloud.
Managed to get the game running after installing GE-Proton9-11 and force set the game to be launched with it. Also, needed to add the launcher options provided by @ShadowyBear some posts below. (Thanks!) My game would always crash right after launching a new game, after the animation with Cal sitting on the floor, just before the intro video sequence starts. Solution was to check the game file integrity by Steam, which found two corrupted PAK files. After doing this, the game launches with no issues.

vk_radv mangohud %command%
Runs OOTB. Steam's built in Proton Experimental works fine.

I had to enable/disabled steam input a couple of times before starting the game. After that all worked great
I have like 10 hours without any glitch (besides sometimes not detecting the controller, but fixed with a restart of the game)

Proton Experimental is my default, but the game would not start. Had to select Proton 9.0-2 for it to start.
XBox Gamepad was not detected the first few times I started this game. Did some tinkering and not it works. Don't know what I changed.