The 2024-04-25 Fallout 4 update (1.10.980 and later) has broken F4SE and the rest of the native code modding scene similarly to Skyrim's "Anniversary Edition" patch. An update is available, but I'm sure it can use more testing. Do not email with questions about progress.
Thank you for all of the support! I assume people would rather have me working on the update than making individual responses, but in general thanks for the nice words and support.
2024-04-27: The first step of the update process is done, doing a first pass at updating all of the addresses for the new version of the game. Another long step begins now, validating the addresses and seeing if there were any structure layout changes. This would not benefit from external testing. 2024-04-28: Building regression tests for games on this engine is painful. To progress on something else that needs work before release, I'm porting over the plugin manager changes and loader changes from SKSE64 and SFSE. This modernizes plugin version detection, and minimizes the virus scanner false positive issues by using a single loader executable that doesn't need to change with each version. 2024-04-29: Secondary preloaders and f4se_steam_loader.dll are no longer needed. Plugins now use the declarative version system from SKSE64/SFSE. Plugin manager is back up and running. Struct comparison between the two versions continues, but I haven't found anything interesting that changed so far. If the next session (not necessarily tomorrow) keeps finding nothing, I'll probably put up a prerelease version to get test results. 2024-04-30: I've put up a very early build so that mod developers can test their plugins and mods against 1.10.980. I appreciate feedback, but right now I can only realistically handle focused feedback from mod developers who know how their scripts work. Reports like "when I call GetWaterType on this specific cell with editor ID [whatever] it returns the wrong result" would be ideal, but I'll be doing investigation as needed. 2024-05-01: Investigating feedback. 1.10.980 itself has some major stability problems that I can reproduce with just vanilla content, so there's probably (hopefully) going to be a follow-up patch soon. Updating for that will not take anywhere near as long as 1.10.980. The unstable base makes finding problems in my code more difficult than it should be. 2024-05-02: A few fixes from mod author reports and requests. Let's see what happens if I widen the audience a bit. 2024-05-03: Apart from the usual misdirected complaints about other people needing to update their mods (expected), things seem pretty good so far. If you can make make the game crash with a single mod, have QA-style repro steps, and the problem doesn't happen when being run without the loader, please let me know. 2024-05-04: Fixed GetResourceLibraryProcAddress - if you are a plugin author trying to update your plugin, that plugin has additional exported addresses, and the plugin loader is doing something weird with it, this will fix the problem. Fixed SplineUtils::ConnectSpline. Most of the updates going forward are going to be very uninteresting, with me just watching the forums and other places to see if people are crashing in a way that isn't caused by the vanilla game, maybe doing small fixes like mentioned earlier. Once I find something seriously wrong or something that is impacting plugin authors then I'll put out a new version with the fixes. 2024-05-10: Bethesda has announced a hotfix patch that will be released on the 13th. This, as is normal, will break things, but nowhere near as badly as the 1.10.980 update. I'll have an update out as soon as possible to support the patch. Hopefully some of the vanilla crashes will be fixed. 2024-05-13: Hotfix released, should have an update after lunch. Seems stable aside from some plugins with bad version data. I am contacting the authors where possible. 2024-05-20: Currently it doesn't appear that any updates to F4SE are needed. Still observing plugin stability.
All native code plugins (.dlls) need to be updated by their creators for 1.10.980. Old native code plugins not loading is not a problem with F4SE. The Starfield loader has given Windows Defender problems in the past. This is a false positive.
The MCM beta 1.40 has incorrect version data and crashes on startup with 1.10.984. An update is available. Better Console also has bad version data and crashes on startup with 1.10.984.
Follow it cause you need to learn how to download the repositories and how to open the steam console. Once you got that down you have to download these and install them in order replacer EVERYTHING whenever it is needed.
(Keep in mind that you are re-downloading the game from what has been saved in STEAMDB, do it one by one, don't hog your download speed by trying to do it all at once. File size should be about 22-ish GBs once you have everything. Once again FOLLOW the guide so you know where the repos will be downloaded and where / how you'll want to move them around.)
Once that is done you have to delete most new files from the creation club that will be in your DATA, these are the culprits that will cause your game to crash since Bethesda updated them in masse I can't be sure which one is safe to keep and which one isn't, so for now it is best to put them in a Back Up folder. Now, anything that has "ccBG" at the beginning of its name in the DATA folder should be safe to remove, that is the code they give to creation club content, however, if you use mods, you probably already know that these are not very much compatible with anything extra from nexus you add to the game.
Once you have all that done REMEMBER to play the game in offline mode / to shut off wi-fi on your steam deck (as is my case) or to delete any manifesto that will force the game to update, cause it will break everything again. Once you have everything I stated done you can probably re-install the current (non-updated) version of the Script Extender and start playing. I've not encountered any crashes or data corruptions. Save games seem clean enough that I have no missing ESP / ESL / Meshes / Textures. If anything goes wrong or you don't feel confident enough that this won't screw your fallout 4 install folder then don't try it. For MO2 this should be safe enough since mods are kept separately from the game elsewhere.
@ianpatt if you could pin this so people know not to bother you it would be great.
All depots are listed on this page : https://steamdb.info/app/377160/depots/ Make sure you donload the version released before April 25 ! I also believe you'll have to download your language depots in addition to the standard packages.
So anyone else running into the The Procedure entry point SteamUser could not be located in the dynamic link library
There's likely 1 of 2 issues causing this for you 1) steam_api64.dll 2) Your deployed mods
Follow these steps: 1) Open your Mod Manager and Purge your mods (don't worry this doesn't delete all the mods you downloaded) -- Also, if you used Vortex or MO2 to install F4SE (which you shouldn't) disable it in your mod manager!!! -- Also, if you installed the unofficial FO4 Patch manually, you're gonna need to uninstall that as well 2) Go to your Fallout 4 install directory and make sure all the F4SE files are gone, don't forget the stuff in the \Data folder and \Data\F4SE --Also, go in to your DATA directory and look for any files that start with ccBG and DELETE those files if you haven't already Alternatively, you can make a Backup folder and copypasta them there and then delete, your choice
3)MANUALLYinstall F4SE 4) Run the game from your mod manager or from the f4se launcher, your choice. -- Make sure that you can load your save, it's gonna whine at you about the missing mods, fo'getaboutit
If you can start the game and load your save, even with the bitching, ALT F4 5) Now you can go back in your mod manager and REDEPLOY your mods
If it's still not working, you're going to need a clean copy of the steam_api64.dll from 04/16/2024 Don't ask me where to get one Copy in the steam_api64.dll in to the ROOT of your Fallout 4 installation before continuing with steps 3 and on above
If this still didn't work for you, well, there may be no hope for you until F4SE gets updated...
I did and loading with skse shows you intro of fallout london but once i load it shows the 2 london esm are missing ,same with a new game. Not sure what i did but it works now.
My steam game suddenly force updated Fallout 4, and after downgrading F4SE now doesn't work, I can't launch the game from it at all. The screen becomes black, and then it CTD's. I reinstalled it for safe measure to the last version of F4SE for preupdate and nothing broke for me.
Hello, I'm having an issue with F4SE where whenever I try to use F4SE to play Fallout 4, I end up facing CTDs near Hangman's Alley. Does anyone know how to solve this?
Oof! I got as far as the depots and my eyes started rolling up in my head b/c I'm too dense to understand it all. Even with the guide it's too much for my pea brain. Ah well. I tried.
I could really use some help. I have fallout version 1.10.163 and F4SE version 0.6.23 and it's refusing to launch my game stating that my game version is 1.10.984 and I need to update F4SE. My game is for sure version 1.10.163, it shows in the menu when launching without any mods. I tried both the old file here and on the F4SE website and both are the same.
So I have a dumb question. But It's been ages since I had to update the Script extender so thank you in advance for your paitence. Do I need to unistall the old version of Script extender before installing this? I used the old Silverlock version so I didn't use a mod manager for the script extender If that matters. Also yes, I'm still using Nexus Mod manager for my other mods. I know it's a dinosaur but it still works. Thanks
I downloaded version 1.10.163 to mod Fallout 4, but f4se gave a warning to run it in administrator mode. Is this normal? He didn't give such a warning last time.
This means that you have some software installed that is globally hooking processes on your computer. Sometimes running the loader as an administrator works around that problem, sometimes it doesn't. Often it's easier to just figure out what you have installed that is causing the problem.
Hey, could someone explain to me why the F4SE deleted itself? What's more, I tried to install it again, but when I try it tells me that I don't have the authorization, I can't continue my game like this.
Alright, what's going on?? I have game version 1.10.163 and f4se version 1.10.163 and it's refusing to launch my game saying that my game version is not compatible with the f4se version I have, which are the same? Any ways to get the old f4se back, the one that supports version 1.10.163? I'm using the 0.6.23 version of f4se so I really don't know what's going on because when I launch the vanilla game, it clearly says version 1.10.163. Please help?
4036 comments
Thank you for all of the support! I assume people would rather have me working on the update than making individual responses, but in general thanks for the nice words and support.
2024-04-27: The first step of the update process is done, doing a first pass at updating all of the addresses for the new version of the game. Another long step begins now, validating the addresses and seeing if there were any structure layout changes. This would not benefit from external testing.
2024-04-28: Building regression tests for games on this engine is painful. To progress on something else that needs work before release, I'm porting over the plugin manager changes and loader changes from SKSE64 and SFSE. This modernizes plugin version detection, and minimizes the virus scanner false positive issues by using a single loader executable that doesn't need to change with each version.
2024-04-29: Secondary preloaders and f4se_steam_loader.dll are no longer needed. Plugins now use the declarative version system from SKSE64/SFSE. Plugin manager is back up and running. Struct comparison between the two versions continues, but I haven't found anything interesting that changed so far. If the next session (not necessarily tomorrow) keeps finding nothing, I'll probably put up a prerelease version to get test results.
2024-04-30: I've put up a very early build so that mod developers can test their plugins and mods against 1.10.980. I appreciate feedback, but right now I can only realistically handle focused feedback from mod developers who know how their scripts work. Reports like "when I call GetWaterType on this specific cell with editor ID [whatever] it returns the wrong result" would be ideal, but I'll be doing investigation as needed.
2024-05-01: Investigating feedback. 1.10.980 itself has some major stability problems that I can reproduce with just vanilla content, so there's probably (hopefully) going to be a follow-up patch soon. Updating for that will not take anywhere near as long as 1.10.980. The unstable base makes finding problems in my code more difficult than it should be.
2024-05-02: A few fixes from mod author reports and requests. Let's see what happens if I widen the audience a bit.
2024-05-03: Apart from the usual misdirected complaints about other people needing to update their mods (expected), things seem pretty good so far. If you can make make the game crash with a single mod, have QA-style repro steps, and the problem doesn't happen when being run without the loader, please let me know.
2024-05-04: Fixed GetResourceLibraryProcAddress - if you are a plugin author trying to update your plugin, that plugin has additional exported addresses, and the plugin loader is doing something weird with it, this will fix the problem. Fixed SplineUtils::ConnectSpline. Most of the updates going forward are going to be very uninteresting, with me just watching the forums and other places to see if people are crashing in a way that isn't caused by the vanilla game, maybe doing small fixes like mentioned earlier. Once I find something seriously wrong or something that is impacting plugin authors then I'll put out a new version with the fixes.
2024-05-10: Bethesda has announced a hotfix patch that will be released on the 13th. This, as is normal, will break things, but nowhere near as badly as the 1.10.980 update. I'll have an update out as soon as possible to support the patch. Hopefully some of the vanilla crashes will be fixed.
2024-05-13: Hotfix released, should have an update after lunch. Seems stable aside from some plugins with bad version data. I am contacting the authors where possible.
2024-05-20: Currently it doesn't appear that any updates to F4SE are needed. Still observing plugin stability.
All native code plugins (.dlls) need to be updated by their creators for 1.10.980. Old native code plugins not loading is not a problem with F4SE. The Starfield loader has given Windows Defender problems in the past. This is a false positive.
The MCM beta 1.40 has incorrect version data and crashes on startup with 1.10.984. An update is available.
Better Console also has bad version data and crashes on startup with 1.10.984.
Firstly, you'll need this guide.
https://framedsc.com/GeneralGuides/steam_update_guide.htm
Follow it cause you need to learn how to download the repositories and how to open the steam console. Once you got that down you have to download these and install them in order replacer EVERYTHING whenever it is needed.
download_depot 377160 377162 5847529232406005096
download_depot 377160 377161 7497069378349273908
download_depot 377160 377163 5819088023757897745
download_depot 377160 377164 2178106366609958945
download_depot 377160 435870 1691678129192680960
download_depot 377160 435871 5106118861901111234
download_depot 377160 435880 1255562923187931216
(Keep in mind that you are re-downloading the game from what has been saved in STEAMDB, do it one by one, don't hog your download speed by trying to do it all at once. File size should be about 22-ish GBs once you have everything. Once again FOLLOW the guide so you know where the repos will be downloaded and where / how you'll want to move them around.)
Once that is done you have to delete most new files from the creation club that will be in your DATA, these are the culprits that will cause your game to crash since Bethesda updated them in masse I can't be sure which one is safe to keep and which one isn't, so for now it is best to put them in a Back Up folder. Now, anything that has "ccBG" at the beginning of its name in the DATA folder should be safe to remove, that is the code they give to creation club content, however, if you use mods, you probably already know that these are not very much compatible with anything extra from nexus you add to the game.
Once you have all that done REMEMBER to play the game in offline mode / to shut off wi-fi on your steam deck (as is my case) or to delete any manifesto that will force the game to update, cause it will break everything again. Once you have everything I stated done you can probably re-install the current (non-updated) version of the Script Extender and start playing. I've not encountered any crashes or data corruptions. Save games seem clean enough that I have no missing ESP / ESL / Meshes / Textures. If anything goes wrong or you don't feel confident enough that this won't screw your fallout 4 install folder then don't try it. For MO2 this should be safe enough since mods are kept separately from the game elsewhere.
@ianpatt if you could pin this so people know not to bother you it would be great.
download_depot 377160 377161 7497069378349273908
download_depot 377160 377162 5847529232406005096
download_depot 377160 377163 5819088023757897745
download_depot 377160 377168 7717372852115364102
download_depot 377160 435870 1691678129192680960
download_depot 377160 435875 2953236065717816833
download_depot 377160 435880 1255562923187931216
download_depot 377160 377161 7497069378349273908
download_depot 377160 377162 5847529232406005096
download_depot 377160 377163 5819088023757897745
download_depot 377160 393882 7540680803954664080
download_depot 377160 435870 1691678129192680960
download_depot 377160 435878 8276750634369029613
download_depot 377160 435880 1255562923187931216
download_depot 377160 377162 5847529232406005096
download_depot 377160 377161 7497069378349273908
download_depot 377160 377163 5819088023757897745
download_depot 377160 377165 7549549550652702123
download_depot 377160 435870 1691678129192680960
download_depot 377160 435872 5590419866095647350
download_depot 377160 435880 1255562923187931216
download_depot 377160 377161 7497069378349273908
download_depot 377160 377162 5847529232406005096
download_depot 377160 377163 5819088023757897745
download_depot 377160 393882 7540680803954664080
download_depot 377160 435870 1691678129192680960
download_depot 377160 435878 8276750634369029613
download_depot 377160 435880 1255562923187931216
download_depot 377160 377161 7497069378349273908
download_depot 377160 377162 5847529232406005096
download_depot 377160 377163 5819088023757897745
download_depot 377160 393882 7540680803954664080
download_depot 377160 435870 1691678129192680960
download_depot 377160 435878 8276750634369029613
download_depot 377160 435880 1255562923187931216
download_depot 377160 377162 5847529232406005096
download_depot 377160 377161 7497069378349273908
download_depot 377160 377163 5819088023757897745
download_depot 377160 377164 2178106366609958945
download_depot 377160 435870 1691678129192680960
download_depot 377160 435871 5106118861901111234
download_depot 377160 435880 1255562923187931216
download_depot 377160 435882 8482181819175811242
download_depot 377160 480631 6588493486198824788
download_depot 377160 393885 5000262035721758737
download_depot 377160 480630 5527412439359349504
download_depot 377160 393895 7677765994120765493
download_depot 377160 377161 7497069378349273908 (Fallout 4 content_a)
download_depot 377160 377162 5847529232406005096 (Fallout 4 exe)
download_depot 377160 377163 5819088023757897745 (Fallout 4 content_b)
download_depot 377160 377164 2178106366609958945 (Fallout 4 english)
download_depot 377160 435870 1691678129192680960 (Fallout 4 - Automatron)
download_depot 377160 435871 5106118861901111234 (Fallout 4 - Automatron English)
download_depot 377160 435880 1255562923187931216 (Fallout 4 - Wasteland Workshop)
The following were not added because there were no recent depot for it so I would assume the update didn't touch it:
Far Harbor
Contraptions Workshop
Vault-tec Workshop
Nuka-World
Hi-res Pack
Для русскоговорящих ниже манифесты для загрузки:
download_depot 377160 377161 7497069378349273908
download_depot 377160 377162 5847529232406005096
download_depot 377160 377163 5819088023757897745
download_depot 377160 393881 4735225695214536532
download_depot 377160 435870 1691678129192680960
download_depot 377160 435877 2675794883952625475
download_depot 377160 435880 1255562923187931216
download_depot 377160 377161 7497069378349273908
download_depot 377160 377162 5847529232406005096
download_depot 377160 377163 5819088023757897745
download_depot 377160 393881 4735225695214536532
download_depot 377160 435870 1691678129192680960
download_depot 377160 435877 2675794883952625475
download_depot 377160 435881 1207717296920736193
download_depot 377160 435888 2814340383581262374
download_depot 377160 480631 6588493486198824788
download_depot 377160 393891 631542034352937768
download_depot 377160 490650 4873048792354485093
download_depot 377160 393899 1428451409051936353
and delete all "ccBG*" files in Data folder
Make sure you donload the version released before April 25 !
I also believe you'll have to download your language depots in addition to the standard packages.
There's likely 1 of 2 issues causing this for you
1) steam_api64.dll
2) Your deployed mods
Follow these steps:
1) Open your Mod Manager and Purge your mods (don't worry this doesn't delete all the mods you downloaded)
-- Also, if you used Vortex or MO2 to install F4SE (which you shouldn't) disable it in your mod manager!!!
-- Also, if you installed the unofficial FO4 Patch manually, you're gonna need to uninstall that as well
2) Go to your Fallout 4 install directory and make sure all the F4SE files are gone, don't forget the stuff in the \Data folder and \Data\F4SE
--Also, go in to your DATA directory and look for any files that start with ccBG and DELETE those files if you haven't already
Alternatively, you can make a Backup folder and copypasta them there and then delete, your choice
3) MANUALLY install F4SE
4) Run the game from your mod manager or from the f4se launcher, your choice.
-- Make sure that you can load your save, it's gonna whine at you about the missing mods, fo'getaboutit
If you can start the game and load your save, even with the bitching, ALT F4
5) Now you can go back in your mod manager and REDEPLOY your mods
If it's still not working, you're going to need a clean copy of the steam_api64.dll from 04/16/2024
Don't ask me where to get one
Copy in the steam_api64.dll in to the ROOT of your Fallout 4 installation before continuing with steps 3 and on above
If this still didn't work for you, well, there may be no hope for you until F4SE gets updated...
Not sure what i did but it works now.
What's more, I tried to install it again, but when I try it tells me that I don't have the authorization, I can't continue my game like this.