$ cp *.exe *.dll ~/".steam/steam/SteamApps/common/Fallout 4" Now, following the readme for F4SE, we need to copy in the dll and executables to the Fallout directory: $ cd f4se_*/ Now unpack it and copy its contents into the Fallout 4 install directory: $ cd m/dl/ This changes on a frequent basis, tracking Fallout 4 builds.
#Fallout 4 script extender not working 2018 how to#
Valve has instructions on how to do that here.Ģ: Purchase and install Fallout 4 in Steam.ģ: Download the current version of F4SE. You'll need to opt in to the Steam Client Beta that will get you Proton support. To save other people who just want to get their game working in Steam, here's what I did.
I got F4SE working in Proton on my Steam environment by binary-hacking the Valve Proton binaries to manually apply the above source patches. These patches haven't been upstreamed to WINE, nor has Valve incorporated them into their Proton build (nor do I have any idea how closely Valve intends to track upstream WINE). Someone has a pair of source code patches to WINE that get WINE working with F4SE. Unfortunately, the Fallout 4 Script Extender (F4SE) feature is necessary to access a fair bit of modded content, including more-elaborate changes to the Fallout game. There are but two issues that I can see on my system - a merely cosmetic one (if 'godrays' are enabled, a feature that provides beams of light shining down from the heavens the game, produces graphical artifacts) and the more serious matter of Fallout 4 Script Extender not working. For all those Fallout 4 fans who want to play it with all modded content on Linux, read on.Ĭurrently, Fallout 4 - a very popular game - works out-of-the-box on Linux if one is using a beta version of the Steam client, due to Valve shipping Proton, a tweaked build of WINE, with Steam.
0 kommentar(er)
