the Sim Settlements forums!

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Addon Pack Registration Failed. Anybody Else Experience This?

Messages
39
Played an hour last night to set up SS2 for myself, and find myself at Red Rocket with the Stranger after only an hour of playtime.
When I loaded my saved game, I got this message:

Addon pack registration failed. The registered name in the config object field sAddonFilename: SS2.esm does not match the registered forms.

I can only select "OK" to close the screen.
Is this something I should be concerned about?
I only have the tutorial plot down, and only an hour into the game, so restarting isn't an issue.

Edit:
I quit the game and updated Vortex. The message has disappeared now.
 
Last edited:

Demishadow

New Member
Messages
9
In case someone runs into this again, I started getting this when something goofed with Vortex and FO4 started launching without F4SE. If you get this error, checking F4SE would be a good place to start.
 

PaPaWicked85

New Member
Messages
3
Found the fix. When installing F4SE, sometimes simply extracting the zip folder to your game registry isn't enough.

-Open up the F4SE archive using 7-zip
-Navigate to the main folder and click "Data", but do not open it. It should be highlighted.
-Up top, click "copy". This will open up a box, same as extracting. Select the main "Fallout 4" folder. Should be C:\ProgramFiles(x86)\Steam\steamapps\common\Fallout4 unless you have it in another directory.
-Click "OK". You'll briefly see a green bar, overwrite if asked, and voila, all done! Open up the game and check to make sure the error messages have stopped.

I don't know why, but in Fallout 4, unlike Skyrim, simply extracting the zip file into your game directory leaves a bunch of required scripts sitting in the data folder, and they require you to move them manually by themselves. Weird quirk, but hey it's Bethesda.
 

BinaryMisfit

Well-Known Member
Patreon Supporter
Community Rockstar
Messages
325
Found the fix. When installing F4SE, sometimes simply extracting the zip folder to your game registry isn't enough.

-Open up the F4SE archive using 7-zip
-Navigate to the main folder and click "Data", but do not open it. It should be highlighted.
-Up top, click "copy". This will open up a box, same as extracting. Select the main "Fallout 4" folder. Should be C:\ProgramFiles(x86)\Steam\steamapps\common\Fallout4 unless you have it in another directory.
-Click "OK". You'll briefly see a green bar, overwrite if asked, and voila, all done! Open up the game and check to make sure the error messages have stopped.

I don't know why, but in Fallout 4, unlike Skyrim, simply extracting the zip file into your game directory leaves a bunch of required scripts sitting in the data folder, and they require you to move them manually by themselves. Weird quirk, but hey it's Bethesda.
If you look at the F4SE readme there is 2 steps to installation:

  1. Copy the f4se_loader, f4se_<gameversion> and f4se_steam_loader DLL's to the game root.
  2. Copy the Scripts in the Data folder to the Data folder in FO4
This process is the same for SKSE. Vortex can do this for you as it has built in support for F4SE deployment. If using MO2 the scripts can be added as a plugin but the DLL's still need to be installed into the game root manually.
 

PaPaWicked85

New Member
Messages
3
If you look at the F4SE readme there is 2 steps to installation:

  1. Copy the f4se_loader, f4se_<gameversion> and f4se_steam_loader DLL's to the game root.
  2. Copy the Scripts in the Data folder to the Data folder in FO4
This process is the same for SKSE. Vortex can do this for you as it has built in support for F4SE deployment. If using MO2 the scripts can be added as a plugin but the DLL's still need to be installed into the game root manually.
Yeah, I was reading about this here because a friend was having the same problem. When F4SE was mentioned, I took a look at the Data files on my copy as well as my buddy's. Noticed a few differences so I asked if he copied the Data folder over to which he said he didn't. Had him do that and no more errors. Just came to report here in case these folks or anyone else has the issue, they can track it down easily.
 

msalaba

Well-Known Member
Community Rockstar
Messages
1,988
Yeah, I was reading about this here because a friend was having the same problem.
When I first installed F4SE, I did the same. I really didn't understand the instructions (or modding in general) at the time and suffered for it. Its amazing how happy software is when it has access to all its data files! ;)

It should be noted there are some mods out there that overwrite F4SE files. This can cause many head scratching problems that can be solved simply by re-extracting the F4SE files into the fallout 4 directory.
 

Rad Rat

New Member
Messages
16
Are you all sure this is a F4SE problem and not just an interment problem caused by something else? I have manually re-installed and let vortex do it.
I have had that stop the message or sometimes it has not. In any case I am not sure this even impacts anything unless that is why my MCM is not working.
But just ok-ing those messages and moving on I notice no difference in game play. I only ever get this on coming back in from a total exit if it occurs. After I save then any reloads it does not occur again untill firing up from scratch but then not always. What does this message even mean, registered to what? The only context I can find is related to SS2.
 

PaPaWicked85

New Member
Messages
3
Are you all sure this is a F4SE problem and not just an interment problem caused by something else? I have manually re-installed and let vortex do it.
I have had that stop the message or sometimes it has not. In any case I am not sure this even impacts anything unless that is why my MCM is not working.
But just ok-ing those messages and moving on I notice no difference in game play. I only ever get this on coming back in from a total exit if it occurs. After I save then any reloads it does not occur again untill firing up from scratch but then not always. What does this message even mean, registered to what? The only context I can find is related to SS2.
100% certain. You cannot use vortex to install F4SE. I mean, you can, but it won't work correctly, if at all. F4SE requires manual install. The instructions even say so. If your MCM isn't working, that's likely the cause. Download the F4SE zip folder. Extract into your Fallout 4 folder. Extract Data folder into your Fallout 4/ Data folder. Overwrite if asked. If you did it correctly, upon entering the main menu press the tilde key (~) to open the console. Type "getf4seversion" without the quotations, and press enter. You should see a bunch of text/ numbers pop up in the console box. If it says "command not found" or something to that effect, you didn't install properly and must reinstall. If it does, press tilde one more to close the console. Load up your game and check your MCM. If it's working, you did everything right. If not, check your F4SE install. If F4SE is correctly installed but MCM doesn't work, that's MCM or another mod causing conflict, and you should check the MCM page on the nexus for answers. Hope this helps.
 

BinaryMisfit

Well-Known Member
Patreon Supporter
Community Rockstar
Messages
325
100% certain. You cannot use vortex to install F4SE. I mean, you can, but it won't work correctly, if at all. F4SE requires manual install. The instructions even say so. If your MCM isn't working, that's likely the cause. Download the F4SE zip folder. Extract into your Fallout 4 folder. Extract Data folder into your Fallout 4/ Data folder. Overwrite if asked. If you did it correctly, upon entering the main menu press the tilde key (~) to open the console. Type "getf4seversion" without the quotations, and press enter. You should see a bunch of text/ numbers pop up in the console box. If it says "command not found" or something to that effect, you didn't install properly and must reinstall. If it does, press tilde one more to close the console. Load up your game and check your MCM. If it's working, you did everything right. If not, check your F4SE install. If F4SE is correctly installed but MCM doesn't work, that's MCM or another mod causing conflict, and you should check the MCM page on the nexus for answers. Hope this helps.
Actually this is incorrect.

Vortex support correctly deploying any of the Script Extenders and has the ability to write to the root of the game. There are 2 ways to do this:
  • If Vortex detect mods the F4SE zip it will offer to auto deploy and correctly deploy it via a separate install process.
  • If manually installing, make sure you have the dll in the root and a Data folder with the scripts. In Mod Options change the Mod Type to DINPUT.
FYI, the same method works for ENB's. You can use Mod Type ENB which will deploy the DLL and ENB folders to the game root.
 

Metal121

Member
Messages
43
Thanks PapaWicked, That solved it, its reportign in ~ and MCM working now.

100% certain. You cannot use vortex to install F4SE. I mean, you can, but it won't work correctly, if at all. F4SE requires manual install. The instructions even say so. If your MCM isn't working, that's likely the cause. Download the F4SE zip folder. Extract into your Fallout 4 folder. Extract Data folder into your Fallout 4/ Data folder. Overwrite if asked. If you did it correctly, upon entering the main menu press the tilde key (~) to open the console. Type "getf4seversion" without the quotations, and press enter. You should see a bunch of text/ numbers pop up in the console box. If it says "command not found" or something to that effect, you didn't install properly and must reinstall. If it does, press tilde one more to close the console. Load up your game and check your MCM. If it's working, you did everything right. If not, check your F4SE install. If F4SE is correctly installed but MCM doesn't work, that's MCM or another mod causing conflict, and you should check the MCM page on the nexus for answers. Hope this helps.
Used Vortex almost since it come out and always installed F4SE with it. So I'm 100% sure it works with Vortex. If you learn Vortex it's have more and better options and control than MO2, at least in my opinion. As binary said, make sure the packed file has the dll in root and script in Data and it works flawless.
 

msalaba

Well-Known Member
Community Rockstar
Messages
1,988
F4SE problem and not just an interment problem caused by something else?
I have run with F4SE enabled on 7 different playthrough of many different SS2 versions and have had no issues.
You cannot use vortex to install F4SE.
I must be a rare exception who had Votex install F4SE and it worked due to divine intervention...
Type "getf4seversion" without the quotations, and press enter.
You can also hit the settings button on the main screen. In the bottom corner of the popup it should say F4SE v(version number here)
In Mod Options change the Mod Type to DINPUT.
Can you elaborate on this? I assume this is a Vortex thing? (n00b Q!)
 

BinaryMisfit

Well-Known Member
Patreon Supporter
Community Rockstar
Messages
325
I have run with F4SE enabled on 7 different playthrough of many different SS2 versions and have had no issues.

I must be a rare exception who had Votex install F4SE and it worked due to divine intervention...

You can also hit the settings button on the main screen. In the bottom corner of the popup it should say F4SE v(version number here)

Can you elaborate on this? I assume this is a Vortex thing? (n00b Q!)
Yes.

1610822081091.png
 

Rad Rat

New Member
Messages
16
This still will often fail to load on the first cold launch attempt, sits at the black screen longer then usual, then when it comes up no F4SE.
Then if I quit and relaunch the short cut it will come up fairly fast and always be loaded then. This I don't get, the files are either there to load or they are not and obviously since it can work they are there. A total drag and drop of the unzipped folder into the fo4 root so launcher, dll's, updates data etc, can't get much more total than that. At least it works, just a little annoying on the first start.
 

MsBathory

Member
Messages
68
This still will often fail to load on the first cold launch attempt, sits at the black screen longer then usual, then when it comes up no F4SE.
I get that if I don't launch Steam first. If I do, F4SE launches on the first go without fail. Totally unconfusing thing is, some people say they have the exact opposite experience. Gotta love consistency. :confused:
 

msalaba

Well-Known Member
Community Rockstar
Messages
1,988
I get that if I don't launch Steam first. If I do, F4SE launches on the first go without fail. Totally unconfusing thing is, some people say they have the exact opposite experience. Gotta love consistency. :confused:
I can't tell you how many time I've done that! Then as I see the Steam boot poppup, I'm like "great, I did it again..."
 
Top