Unknown
Game will occasionally just stop launching, re-validate or reinstall the game. GE-Proton10.7 seems to work with the launcher & game.
PROTON_ENABLE_WAYLAND=1 %command%
DX12 will sometimes not launch on this system without checking 'Fullscreen' in launcher
Without changing the prefix or Proton versions the game will fail to launch or crash as soon as Warframex64.exe is started. My only fix was to wipe the Proton prefix and re-validate & optimize in the Warframe launcher.
I don't think the GE branch is needed to play, Proton 9 w/ gamescope works with DX12 (at least on AMD), other than minor frame drops occasionally the game runs really good.
Switch to DX11 if you're running a Nvidia GPU.
alt tabbing back into the game sometimes breaks fullscreen. but doing it a few more times fixes it.
this time i installed the game on a different drive that was using btrfs :) ntfs sucks lol
wine launcher.exe %command%
alt-tabbing out of the game sometimes breaks it and you cannot re-enter the game visually but only audibly.
sometimes the game slows down while confirming settings changes and entering/exiting menus.
when i hit play the button changes to say stop, then goes back to saying play. my game is downloaded from a drive in ntfs format that used to be used for Windows 10. this may cause an issue for this game specifically as other games i play dont really have this problem. running the launcher through wine was the only way i could find to get it to run. once the game launches then steam can no longer track game time.
RADV_PERFTEST=ngg,rapm,radv_rt=1,sam,cache_compressor,wave32,dualcu VKD3D_CONFIG=dxr11,dxr,no_upload_hvv mesa_glthread=true AMD_DEBUG=zerovram,nodma RADV_VIDEO_DECODE=0 PROTON_ENABLE_NVAPI=0 %command%
Can't play fullscreen windowed.
Frametime rubberbanding on any proton version above 9. GE 10.4 included.
I played with the stutter for a while and it was playable.
Couldn't get it to work with gamescope due to the custom launcher the game has, but the game does work fine perfectly out of the box without
I only seem to have found sudden FPS drops in Höllvania (1999), around 5-10fps at times.
Did a test on Steel Path Hellscrub (Survival) for about 15mins, maximum i saw dropped was 60fps to 45fps on intense moments (lots of explosions, VFX on screen), which is honestly impressive for my now outdated PC. Even recorder a small portion of it if anyone cares. https://youtu.be/iNBKen-xOpo
Works right out of the box with GE-Proton10-4. Minor initial fullscreen hiccup, fixes it automatically after restarting the game.
That's perfectly normal for warframe to not run in fullscreen on a new computer, however changing to fullscreen it will stay in same windowed size regardless the resolution. To fix this, simply set your desired resolution in my case 1920x1080@144. Do NOT choose Borderless fullscreen, use normal fullscreen instead.
Confirm changes, exit the game and the next time you start playing it will be fixed.
To my incredible surprise, I had problems running the game in the past even with GE-Proton. Nowadays, even the game launcher works as intended. Players will only experience a minor hiccup from windowed to fullscreen, as the game will not initially comply. That being said the game works flawlessly with no visual bugs, gliches or slowdowns.
So far I have not seen any noticable performance on stock GPU settings versus on undervolted Windows 11, however so far I havent' been able to confirm. I need to install mangohud to keep monitoring the GPU output, and also try to find reliable overclockign software on Fedora.
mangohud DRI_PRIME=0 RADV_PERFTEST=ngg,rapm,radv_rt=1,sam,cache_compressor,wave32,dualcu VKD3D_CONFIG=dxr11,dxr,no_upload_hvv mesa_glthread=true AMD_DEBUG=zerovram,nodma RADV_VIDEO_DECODE=0 PROTON_ENABLE_NVAPI=0 %command%
Only reason i'm using DRI_PRIME=0 is because my dedicated graphics is classified as 0.
gamemoderun %command%
Launcher kept throwing up update launch failed, could not run executable. Had to set the launch option to get it load the game. Runs smoothly after that.
PROTON_ENABLE_WAYLAND=1
mangohud gamemoderun DXVK_FRAME_RATE=75
It works like native
Launcher is bugged and shows black on news background but other than that launcher works as an launcher for playing and downloading game
PROTON_ENABLE_NVAPI=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PULSE_LATENCY_MSEC=60 %command%
Quando altera modo janela sem bordas para tela cheia o jogo trava e fecha, quando aperta alt+tab o jogo trava e minutos depois fecha.
Enquanto joga sozinho funciona muito bem mas quando esta jogando com varios jogadores ele trava bastante e demora no carregamento.
O jogo foi testado em um hd mecânico mas recomendo usar um ssd de qualidade para ter uma experiencia melhor!
gamemoderun %command%
Sometimes, the mouse behaves with huge delay to the input
Basically works out of the box.
Sometimes I'd have to restart the game because it wouldn't allow me to move or control my mouse, restart would fix that.
Works just fine
Some stuttering, which seemed to stop after maybe 5-10 minutes of playing.
Aside from the stuttering, the game runs the same as on Windows.
%command% gamemode
Stutters and sluggish moments I believe due to the shaders. After about an hour of play I have no more slows.
You can play the game without tinkering, turning on gamemode through launch options is just a bonus.
gamemoderun %command%
When you switch to Fullscreen and alt tab, you either a) need to tab back in 20 times to finally get in OR b) game's bricked and you can't get back into it at all until you reset.
I usually play in Windowed Fullscreen and it works great though, seems to be Fullscreen only issue.
Seems like occasional stutters are pretty common. It calms down after a bit but on session start you kinda get bombarded by them. Could be an issue on my side and I'm too stupid to realize lol
I have tested a few proton versions and all of them work just fine. This one gave me least visual anomalies (such as on the launcher itself, with other versions half the launcher is just black but with this one everything is fine).
Other than that you can run the game just fine without any tinkering.
The game is playable and there was no tweaking with settings.
In general Warframe is working quite fine on this rig, but needs some additional tinkering and knowledge.
DX12: borderless window mode halts the game. Fullscreen mode is working.
Keyboard: automove bug. ingame character moves into one direction without keyboard stroke. Mouse: Viewing direction bug (maybe fixed now). In Netracells after transfering from Operator/Drifter to Warframe the Warframes viewing direction was shifted at a remarkable angle to the left. Didn't experience this bug for a while so I guess it is fixed now.
DX11 in general not working (game crashes), DX12 works only in fullscreen mode but crashes randomly without any hints in logfiles (EE.log, Proton log files)
On this laptop, all the problems mentioned have only occurred since the release of the Jade update in 2024. Whether they are due to the game Warframe, the game updates, the hardware or the hardware drivers remains unclear. So far, I have not been able to completely eliminate all the issues that have arisen. But overall Warframe is still "playable" with some caveats.
Game works about as well as it does on Windows without any tweaks, maybe even better. Running with DX11 in borderless window
Game runs well, minor issue with duobooting with windows
I had this installed on a second ssd on windows with other games, most of the others ran no issue but i had to re-install Warframe. After that runs perfect!
Trying Various Proton Versions
I receive no audio stream from the game itself. This works fine for other games.
%command% gamemode
Coming from Windows for the first time and the game runs exceptionally well on Linux. Some areas saw lower GPU utilization and increased framerates in comparison. Game does take a couple seconds when ALT+TABbing and launcher is a little finnicky with some elements blanking out, not a big deal. DX12 is recommended from me, much more stable framerate in CPU bound scenarios (which is the majority of the time) have fun tenno!
Game runs well after disabling "High Quality Shaders". Be aware of high CPU usage during caching.
WINEFSYNC=1 WINEESYNC=1 gamemoderun %command%
CPU Usage spikes to almost 100% during loading and for a little while during the start of a mission. Presumably it's caching or something and it may get better in time. Disable "High Quality Shaders" for a decent FPS boost.
After a tiny bit of tinkering, the game runs well. Outside of the high CPU usage during loading screens, and low frame rates during the start of the mission (which may improve in time, after a cache has been built), I have better overall performance on Proton than I do on Windows 10.
gamemoderun %command%
LinuxWins
Game worked perfectly out of the box. No tinkering required.
The launcher was black initially until i clicked a button for settings and the textures and graphics returned.
gamemoderun %command%
Recently been getting an update failed screen on launcher. Fixed this by ensuring I had i386 architecture installed and drivers
gamemoderun %command%
All tinkering is my default setup, it is to increase stability and performance of games. If you open settings in launcher, after closing them it will make the moving part completly blank. It fixes itself with elements moving, you can do it yourself by changing tabs in launcher.
ALT-Tabbing while using fullscreen can possibly prevent you from coming back to Warframe. You have to be patient while it loads back again. Alternatively, play in Borderless Fullscreen.
Do not forget to optimize download cache if you have not done it yet. (In game launcher settings)
I use GloriousEggroll's version of Proton.
Worked out of the box. Very good!
Windows-like experience, if a little faster.
switching to desktop and back sometimes causes issues
Not as fluid as i would have liked,.. but i still works great
mangohud gamemoderun LD_PRELOAD="" %COMMAND%
There's an issue since last Friday, where the launcher returns an Update failed! error. In the Warframe Launcher.log theres an error: GetVolumeInformation(Z:\home) failed. Error code: 144
Steam returns the following during the update attempt: wine client error:0: recvmsg: Socket operation on non-socket
There's a temporary solution to this, you need to delete the prefix for Warframe located in: .steam/debian-installation/steamapps/compatdata/230410
Careful tho, your config file is located here, you will want to create a back up for it. .steam/debian-installation/steamapps/compatdata/230410/pfx/drive_c/users/steamuser/AppData/Local/Warframe/
If you do this most of the time it will launch. But once you have a successful start, you will have to delete the prefix again to be able to launch the game again.
