VerifiedShow Details
Unknown
PROTON_ENABLE_WAYLAND=1 mangohud %command%
Under Wayland, the game tends to crash when changing resolutions. This can be fixed by setting the primary display via WAYLANDDRV_PRIMARY_MONITOR=YOUR_MONITOR_ID in the launch options.
Under Wayland, it is necessary to disable Steam Input, as it is not supported. My leverless was recognized fine once I disabled this, whereas it wasn't recognized at all before.
Setting lightning & texture settings above "High" causes major performance degradation
The game suffers from noticeable input lag when running under xwayland. Thanks to GEProtons Wayland support, this has been completely fixed. However, there are some adjustments needed to get everything to run nicely.
- If you have issues with slowdowns during online matches, run
sudo sysctl kernel.split_lock_mitigate=0before starting up the game. - If your distro supports it, enabling ntsync also helps to further stabilize the frame times - at least on my system. Under current Arch, this can be done with
sudo modprobe ntsync. - If you are running the game on a television that does not support native 60Hz and up (e.g. 59.95Hz), enabling VSync in the game settings will fix dropped inputs, although it will add a tiny bit of input lag (which is still noticeably less than when running under xwayland).
Generally, you will want to enable Shader Warming on Startup and Input Delay Reduction regardless of your display server protocol. Note that the Steam overlay will not work under Wayland at the moment, so if you intend to use the ingame shop, you will have to start the game using xwayland.
To sum it up, I would argue that running under Wayland allows for competitive gameplay, while xwayland will only suffice for casual gameplay. For the latter, the game will run out of the box with any current Proton version, but setting kernel.split_lock_mitigate=0 might be needed regardless. Optionally, feral gamemode will do this for you aswell.
Runs just like on windows, even on ntfs drive on ubuntu 25.04
gamemoderun LD_PRELOAD="" %command%
- NVIDIA issue not specific to SF6 | Occasionally fails to launch after a recent NVIDIA driver update, with errors relating to failure to create DX11 device. Resolve by clicking OK and launching the game again.
- Steam overlay does not activate. Can circumvent by launching Steam from the commandline, or by changing LD_PRELOAD launch option to LD_PRELOAD="$(echo $HOME)/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so". Not recommended permanently as it seems to introduce performance issues during online play.
Recommender tinkering
- Enable Steam overlay by launching Steam from the commandline or including LD_PRELOAD="$(echo $HOME)/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so" in your SF6 launch options. Seems to introduce performance issues during online play, so only use it temporarily or launch Steam from the commandline.
- Fix texture tearing issues by enabling the org.gnome.mutter experiment features: scale-monitor-framebuffer, variable-refresh-rate, & xwayland-native-scaling
Recommended in-game settings, not specific to Linux
- Set Graphics > Input Delay Reduction to On
- Set General > Other Settings > Shader Warming on Startup to Perform
gamemoderun LD_PRELOAD="$(echo $HOME)/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so" %command%
Note: Issue is not specific to SF6
- Occasionally fails to launch after a recent NVIDIA driver update, with errors relating to failure to create DX11 device. Resolve by clicking OK and launching the game again. This will likely be fixed in a future NVIDIA update.
Recommended tinkering
- Enable Steam overlay by including LD_PRELOAD="$(echo $HOME)/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so" in your launch options (or by launching Steam from the commandline)
- Fix texture issues by using dconf editor to enable the org.gnome.mutter experiment features: scale-monitor-framebuffer, variable-refresh-rate, & xwayland-native-scaling
Recommended in-game settings, not specific to Linux
- Set Graphics > Input Delay Reduction to On
- Set General > Other Settings > Shader Warming on Startup to Perform
mangohud %command%
roda liso no bazzite, deu umas engasgada na primeira vez que eu entrei na partida mais depois ficou liso igual bunda de nene. 0 input lag.
Everything works out of the box
Everything worked just fine after installing. Been playing the world tour, practice, online matches with friends and even ranked matches.
Great
no notes. works like it should. no tinkering like its meant to be
It had a steady 60fps when first installed but after restarting the system I experienced drops to around 50-55fps
Game freezes when countering a throw
While playing through the tutorial, the game asks you to counter a throw. The moment I counter the throw and get a burst of blue effects, the game freezes. Music continues but the rest of the game is frozen, with a still screen of the moment. This happened no matter what Proton version I tried, and also happened trying all of the launch options people list here.
Apart from the "white fog" bug, this works better than on windows for me
Sometimes a white "fog" covers most of the stage. This happens very infrequently and rebooting the game fixes the problem.
Without Proton-GE I got some awful white blotches where particles should've been on stage. Do yourself a favor and use Proton-GE.
It works fine with default proton configuration
gamemoderun %command%
Textures on certain stages will occasionally fail to load correctly. While you can still play the game in this state, the incorrect textures results in colorful and extremely distracting opaque objects. Forcing the game to pre-compile (called "shader warming" in SF6) textures isn't guaranteed to help.
Occasional texture issues aside, this game generally runs well, even in online modes.
As the other reports have mentioned, you may experience poor performance online if your system has the split_lock_mitigate setting enabled.
Game mode can automatically toggle the setting when you're playing. Make sure that your user is in the gamemode group or the performance fixes related to split lock won't be applied.
Logging in the first time for online play is annoying. When the on-screen keyboard pops up, all the input fields are outside the viewable part of scrollable panes.
Logging in the first time for online play is annoying. When the on-screen keyboard pops up, all the input fields are outside the viewable part of scrollable panes.
There's no real touch screen support, it's just a mouse. Touching the screen while in play sometimes switches the game to displaying keyboard controls. Pressing A, B, X or Y reverts it.
World tour fights run at around half the normal speed until activating the option to limit these to 30 fps in the settings.
Runs fine with all graphical settings at max, except the option to limit world tour fights to 30fps needs to be activated for these to run at normal speed.
Runs the same as windows, no issues locally or playing online.
300+ hours on this title, 1/3 on Linux. No issues
Sometimes particles are blown out bright white making it unplayable
Ignoring the graphical glitch everything works perfectly
DXVK_ASYNC=1 gamemoderun %command%
Texture issues
- Extreme issues where textures break and either permanetly stay like that or rapidly flutter
- Minor issues where textures briefly stretch and snap back
Occurs most often in World Tour mode, which would also cause the game to freeze, and improves once subsurface scattering is disabled and the internal rendering is changed from 5 to 4. Even with these changes the problem still occurs semi-frequently in Fight Hub, and World Tour is effectively unplayable.
Freezes and crashes
Graphical glitches are often accompanied by the game freezing/crashing soon after.
I've been able to play ranked quite happily, and if that's all you care about you can definitely play it, but not being able to play World Tour and get outfits is a bummer.
The game is fully playable with no decernable input lag nor crashes, the only exception being a slowdown issue from having multiple monitors
LD_PRELOAD="" gamemoderun MANGOHUD_CONFIG=gpu_name mangohud %command%
An intermitent and seemingly random "stutter" effect occurs, but it is not related to any hardward slowdown or overload. After attempting many fixes (including reinstalling/downgrading nvidia drivers, installing the flatpak version of steam, changing proton versions, and tweaking nvidia driver settings), it seems to be an issue related to the X11 display server. If you are using multiple monitors with different framerates, this hard to describe framedrop-esque effect occurs. The framerate/responsetime/GPU activity doesn't actually change, but visually, the slowdown occurs. If I unplug all but the main monitor, the issue disappears.
Couldnt get past the versus screen
Tried with different proton versions, always got engine crashes on the versus screen or when loading the multiplayer hub
on higher graphics settings I will often see player models tear in extreme ways, obscuring all other elements on screen
the more content I load the more likely a crash is to occur.
Tinkering has changed nothing in my experience.
sed -i s/"ShaderWarmed=TRUE"/"ShaderWarmed=FALSE"/g /home/$(whoami)/.local/share/Steam/steamapps/common/Street\ Fighter\ 6/config.ini && gamemoderun %command%
Force shaders to be warmed at every startup via launch options sed command.
Without gamemoderun, the framerate may be choppy in battle.
Crossplay does not work. Matchmaking will never pair you with some console player and if you try to play with a friend on console in a custom room, the game will be in slow motion. Tried many Proton versions, many configs, docked with cable internet and wifi. PC vs PC works flawless though.
mangohud gamemoderun %command%
Rarely, there is a shader issue which turns dust and smoke into really colorful clouds. Happens only on some stages, usually goes away quickly.
Very rarely, the game hangs your entire computer. Happens once every 3-4 month, not more often.
You definetely need to make sure that either you or your gamemode disables the split lock mitigation - see other comments or game issue in Proton repository. Otherwise, it's perfectly playable. Mods also work.
the fps drop ploblem
I was able to solve the fps drop problem with the following. Thanks for the info.
sudo sysctl kernel.split_lock_mitigate=0
No problems with World Tour and Fighting Grounds. I haven't tried Battle Hub.
Playing Fighting Ground works fine, but only after tweaks. For me Battle Hub is broken.
After a recent update the game runs at a low fps due to splitlock protection. It can be disabled by running
$ sudo sysctl kernel.split_lock_mitigate=0
(I followed these instructions.)
After which, the performance is good.
Sometimes things like smoke and paint effects don't render correctly
Game seems to always soft lock in Battle Hub, when interacting with just about anything. Not nice since I would like to play sets longer than ranked ones. (I haven't tried the single player mode to see whether it has the same issue.)
× I used the experimental version of proton. The frame rate dropped.
Since updating to version 1.0620.000, the frame rate has consistently dropped to around 15fps, including in the menus. The game is virtually unplayable. I had been able to play for over 500 hours up until the day before the update.
