Não é uma boa experiência, mesmo com tudo no baixo.
Ran with Proton Experimnetal no problems with the enritre playthrough!
On Linux, you have to unplug the controller and plug it in again for it to be recorgnized.
I have to switch to keyboard layout on startup, and then to the default controller to make the game detect the built-in controller.
Crashes frequently
Tried experimental and protonGE-25
It crashed 3 times in 6 hours. I don't like the game so I'm not wasting time to fix it, I'll find something to play.
Works
Worked once i applied the changes described here: https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows
MANGOHUD=1 gamemoderun %command%
RADV_PERFTEST=gpl,nggc,sam
Previous fixes that were mentioned are no longer needed, the game loads saved games perfectly fine now on Proton Experimental! I haven't tried any other Proton version since the fix. The game also no longer mentions that you are on a HDD when you are not.
Switch between exclusive/borderless did not work
Frequent crashes. Not the issue that others have seen. Patch injection didn't work.
With the latest update, Star Wars Outlaws now works perfectly out of the box. The previous workaround I posted is no longer needed.
MANGOHUD=1 RADV_DEBUG=nodcc RADV_PERFTEST=aco %command%
dxinput off
Game freezes when trying to load a saved game
Random stutters
This is an update from my previous report. Previously I could not load a saved game at all, and is an issue if you don't do any tinkering. Thanks to another reporter on here, I can confirm that fixes from this link fixed it and I am able to load into a saved game now: https://github.com/HansKristian-Work/vkd3d-proton/issues/2092#issuecomment-2523442025 (read more than just this comment that it is linked to).
I do get some stutters off and on, and changing graphic settings that have been recommended (like turning down contact shadows) didn't help at all. Still playable, just annoying during combat situations.
This is fixable.
Problem
- Crashes while loading a savegame or shortly after
Solution
This can be fixed by using the workaround explained here: https://github.com/HansKristian-Work/vkd3d-proton/issues/2092#issuecomment-2523442025 Read the comments above and below, too.
In a nutshell, you have to download two *.dll files (d3d12.dll and d3d12core.dll) and use them to replace the original *.dll files in a specific Steam directory. After doing so, Outlaws works like a charm.
Note that you need to download "vkd3d-proton-merge-59224fd7ac0afe1caace63abf035c5fc47340188.zip" from here: https://github.com/HansKristian-Work/vkd3d-proton/actions/runs/12201080683
The download icon will only appear, if you sign in with a Github account.
If you’re using the Flatpak version of Steam, copy the two dll files into this directory: ~/.var/app/com.valvesoftware.Steam/.steam/steam/steamapps/common/Proton - Experimental/files/lib64/wine/vkd3d-proton.
Thanks to HansKristian-Work for providing this solution!
I can only play with external controllers. You have to switch the order of the controllers to make it detect it. Similar issue with Avatar
Space works well, but planet environments are choppy
After the Wild Card DLC was released, when I launched the game it would prompt me to install the game rather than launch. Worse, it mad the steamdeck eject the external drive I have it installed on. I haven't reinstalled since as it's not a great experience on deck anway.
RTX Direct Lighting seems to cause problems and you'll need a very high-end GPU to enjoy it at its best, but plays well enough to be fun.
Once I set exclusive fullscreen it would not go back to borderless window without deleting the Windows user game folder.
System menu once locked up when enabling RTX Direct Lighting.
TLDR: probably best to turn off RTX Direct Lighting, especially if you are having problems loading a saved game. FULL DETAILS: I installed it on 21st Nov 2024 in Steam and based on comments here I set Proton to Experimental, but no other tweaks. Game launched ok and main menu was fine. Started new game and intro cutscene was fine. Once in game I had a look at graphical settings. Everything had been automatically set to low as I only have a RTX 3070 on this machine - hope to try it on my 4070 soon, but sadly I suspect this game needs a 4080 / 4090 or upcoming 50xx GPU to run at high or ultra. I left everything at low but turned on RTX Direct Lighting to give some degree of boost to the eye candy. On my 165Hz ultrawide 1440 monitor the frame rate was very good, dropping noticably with RTX Direct Lighting turned on, but still pretty good and very playable but definitely not butter smooth, as I could perceive a slight lag between input and screen update. It seemed flawless as I played right through the prologue section up to the checkpoint where the team drops you off on the cliffs to raid the vault. Next I tried to play again about 8-9 days later. Main menu was fine but it would quickly seize up on loading the saved game to resume. I tried changing video and graphics settings but nothing worked, it always seized. When I switched into exclusive fullscreen it would refuse to switch back to borderless window, and the only way I could get it back to borderless was to delete the user game folder: ~/.steam/root/steamapps/compatdata/2842040/pfx/drive_c/users/steamuser/Documents/My Games/Outlaws. After messing about for a while I turned off RTX Direct Lighting on a hunch and finally the saved game loaded and I was able to resume play. Once in game again I tried turning RTX Direct Lighting back on and it then glitched and would instantly go back to the graphics menu every time I tried to exit the menu. I decided the RTX feature is borked and will not try turning it on again. Anyway, I was then able to play the vault raiding section of the story without issues and get to the next planet. In conclusion, yes it will work and you can have plenty of fun with it, but don't expect to be able to see it at its best with all the eye candy turned on.
LD_PRELOAD="" %command%
Use LD_PRELOAD="" %command% launch option to fix significant stutter in game after 30 minutes of gameplay caused by Steam's borked 'in-game recording' feature.
Ubisoft Connect cannot authenticate the product
Ubisoft connect fails to let you play
Won't load into game from main menu
The game worked fine, twice. And the past couple days the game just won't load the save file or even start a new game anymore. I click to resume or new game and it will just get stuck on the loading screen. No error. No crash. Nothing in the logs. It just gives up. I tried low settings, ultra, with/without DLSS, FSR, etc... I tried many different Proton/GE-Proton versions (to the point the game would no longer activate so I had to wait 24 hours before trying again, I assume because of Denuvo thinking I am on a different system).
I give up for now. Will update with another report if I get it working on a future version of Proton or GE-Proton. My specifications on the right are all up to date. Or might just boot into Windows to finish this thing.
I can launch Star Wars Outlaws without any customization and the game works flawless. I set the graphic to Ultra with my ultrawide screen.
My configuration is : Kubuntu 24.04 Noyau:6.8.0-49-generic RAM:32 GB Pilote GPU: Mesa 24.0.9 GPU: AMD Radeon RX 7800 XT CPU: AMD Ryzen 7 7700X
In graphic settings.cfg, set ["streamer dedicated budget"] = 1024 as well as a few other cosmetic options not available in-game (like disabling bloom and glare).
Disabled steam-input for dualsense. With steam-input enabled, camera would spin when dualsense was connected.
Typically gigabyte motherboards would have above 4g decoding enabled but rebar disabled. I had horrible stutters in this game until I also explicitly enabled rebar in bios.
Increasing streamer dedicated budget in graphic config.cfg should be considered a requirement. The default value is way too low and will cause poor performance and low quality textures, even on ultra.
Set ["streamer dedicated budget"] = 1024 in graphic settings.cfg.
Disable steam input to get dualsense to work, otherwise your camera will spin.
Major stuttering every few seconds regardless of in-game graphics settings
GPU crashed once in 16 hours of play. Crash happened while streaming through Discord.
Adjusting the graphic settings.cfg can help you get rid of bloom and glare, which makes the game look much better. Increasing ["streamer dedicated budget"] appears to reduce but not eliminate stuttering. Stutters occur about every 3 seconds and last for roughly a quarter of a second, post-tweaks.
Had one crash during a cutscene, but it was fine after that.
selecting GE-Proton9-16 as available compatibility
Seems to run fine so far. Some moderate hitching in new scenes, but it feels like shader compiling on the fly.
I haven't tried non-experimental, but I have experimental enabled by default, so technically I didn't do anything special to launch the game. Overall it appears to be working as expected, if a little hard on my config, I'm still getting around 60FPS on 3440x1440 on high settings with the RT settings on minimum and no FSR. Perfectly serviceable for a story game, I could probably push it higher if I needed to for the shooting.
Lutris install script used to install Uplay Connect.
Crashed at start up until forcing the use of experimental proton.
Game would not close cleanly and resulted in a black screen. Attempting to force close did not work, had to reboot machine.
I got the game as part of the bundle and thus had to launch from Uplay Connect instead of Steam which made install and playing harder. Lutris is used to handle Wine and installing/running Uplay Connect and overall works fine after forcing use of Experimental Proton.
The game crashes on loading screen.
It might work with latest experimental, supposedly. I've not tried anymore as it Damaged My HW!
