The new INI method has given me fits and is unstable for me.
It doesn't load textures properly, causes a CTD when attempting to enter certain areas it doesn't like [FEV Lab and Prydwen Upper Decks], greatly increases the frequency of slow loading textures, often ignores installed texture mods, and is generally unstable for me. There is also not a significant difference in load times. Yes, there is some, but overall switching over to this new method has been a horrible idea.
I think it has trouble deciding which textures to prioritize when more than one is installed that modifies the same object. For example, I have a mod that modifies a large number of landscape textures, and another one that improves just rocks. They both handle rocks, and when installing with NMM the manager asks which one to use. It doesn't overwrite them because if I uninstall one mod, the other is still there. I've checked this in the past by installing textures that I decided I didn't like and removing them, only to have the previous modded texture I was using still be there once I loaded the game again despite not reloading it with NMM. It keeps both files and seems to try to prioritize which to use.
The new Archive Invalidation doesn't seem to be able to figure out which to use.
At any rate, when I use the new INI settings, it can't figure out which to use, and just stays with the vanilla texture instead. This conflict also causes textures to load slow leading to a lot of blurred low res textures when I first enter an area.
I don't have these issues using the old method. The landscape textures load fine, and then the proper rock texture loads replacing the landscape and vanilla textures for rocks just as I loaded them with NMM.
The new INI edit is unstable and pretty much sucks, it gets confused and doesn't load things properly in my experience, especially in regard to textures.
I can't endorse this new edit, it's just not working right. I recommend that anyone who is having difficulties like mine just stay with the old edit:
So when I launch Nexus Mod Manager, I have mods installed, but none of my plugins are showing. The only plugin that shows if Fallout4.esm, and all the mods are activated.
It looks like your the one trolling here with your post. I haven't know that stuff altho i've played previouse bethesda games and was using mods before (probably because i used NMM which did that stuff for me) One thing I would add to this tutorial is the location of the fallout4prefs.ini which is in C:\Users\Username\Documents\My Games\Fallout4
Is the Fallout4Prefs.ini to in your instructions referring to the one in R:\Steam\steamapps\common\Fallout 4\Fallout4 and or the one in C:\Users\NSAGHCQxxRedacted\Documents\My Games\Fallout4 ? Edit, and what does that entry accomplish? I forget what that is about...
Oh, and as a long time Nexus user, I think your guide is fine for new comers assuming they are not total no nothings about PC file systems and basic management. I think of course there are those that will still be lost and writing up a far more detailed guide would be a major bit of work. I suppose that is why I see people saying your guide is worthless. It isn't. Thanks for effort. It's been years since I fooled with modding FO3, NV, Skyrim, and I appreciate memory refreshers as I forget half of what I learned.
I will try to update the guide, make it better from the feedback I am getting here.
I know how to it so my perspective of those who don't is a bit abstract to know the proper needs/steps necessary to accomplish this task.
The line in Fallout4Prefs.ini should enable the new Data files selection to appear in the launcher.It doesn't at the moment like it used to do in previous games, that's why we need to introduce the entry manually in plugins.tx. What I suppose it does as well is keeping the launcher from overwriting what you just introduce as a new load order, if you don't have it you need OFC to follow my first instruction and make plugins.txt read only, I still do this just to make sure the file is loaded in game.
For what type of mods you have to do those instruction ? I normally download mods from nexus and place them in data folder and they work. I only had to change sResourceDataDirsFinal=STRINGS\, to sResourceDataDirsFinal=STRINGS\, INTERFACE\, TEXTURES\, SOUND\ in Fallout4.ini. So I'm guessing simple retexuture mods dont require that changes to plugin.txt ?
The file is EXACTLY what it says it is, a tutorial on how to install Fallout 4 plugins. My thanks to the author.
Not sure how much more explicit he/she would have to be for some folks to understand "No matter how basic it is to install Fallout 4 plugins, some people keep asking how to do it, I understand that a lot are new users of Nexus and some playing Beth's games for the first time.
So this is a a short tutorial how to do it.", but apparently some folks didn't get it.
Give Feedback
26 comments
without "
It doesn't load textures properly, causes a CTD when attempting to enter certain areas it doesn't like [FEV Lab and Prydwen Upper Decks], greatly increases the frequency of slow loading textures, often ignores installed texture mods, and is generally unstable for me. There is also not a significant difference in load times. Yes, there is some, but overall switching over to this new method has been a horrible idea.
I think it has trouble deciding which textures to prioritize when more than one is installed that modifies the same object. For example, I have a mod that modifies a large number of landscape textures, and another one that improves just rocks. They both handle rocks, and when installing with NMM the manager asks which one to use. It doesn't overwrite them because if I uninstall one mod, the other is still there. I've checked this in the past by installing textures that I decided I didn't like and removing them, only to have the previous modded texture I was using still be there once I loaded the game again despite not reloading it with NMM. It keeps both files and seems to try to prioritize which to use.
The new Archive Invalidation doesn't seem to be able to figure out which to use.
At any rate, when I use the new INI settings, it can't figure out which to use, and just stays with the vanilla texture instead. This conflict also causes textures to load slow leading to a lot of blurred low res textures when I first enter an area.
I don't have these issues using the old method. The landscape textures load fine, and then the proper rock texture loads replacing the landscape and vanilla textures for rocks just as I loaded them with NMM.
The new INI edit is unstable and pretty much sucks, it gets confused and doesn't load things properly in my experience, especially in regard to textures.
I can't endorse this new edit, it's just not working right. I recommend that anyone who is having difficulties like mine just stay with the old edit:
sResourceDataDirsFinal=STRINGS\, TEXTURES\, MUSIC\, SOUND\, INTERFACE\, MESHES\, PROGRAMS\, MATERIALS\, LODSETTINGS\, VIS\, MISC\, SCRIPTS\, SHADERSFX\
It's a lot more stable and reliable.
instailing mods fallout 4
https://www.youtube.com/watch?v=cybjYUA8caU
skip pass 3mins
you give us a file.. with a rather crappy desc.. and expect these "new people" to know what to do... yea. ok. thumbs down anyone?
bEnableFileSelection=1
Is the Fallout4Prefs.ini to in your instructions referring to the one in
R:\Steam\steamapps\common\Fallout 4\Fallout4
and or the one in
C:\Users\NSAGHCQxxRedacted\Documents\My Games\Fallout4 ?
Edit, and what does that entry accomplish? I forget what that is about...
Oh, and as a long time Nexus user, I think your guide is fine for new comers assuming they are not total no nothings about
PC file systems and basic management.
I think of course there are those that will still be lost and writing up a far more detailed guide would be a major bit of work.
I suppose that is why I see people saying your guide is worthless. It isn't. Thanks for effort. It's been years since I fooled
with modding FO3, NV, Skyrim, and I appreciate memory refreshers as I forget half of what I learned.
I will try to update the guide, make it better from the feedback I am getting here.
I know how to it so my perspective of those who don't is a bit abstract to know the proper needs/steps necessary to accomplish this task.
The line in Fallout4Prefs.ini should enable the new Data files selection to appear in the launcher.It doesn't at the moment like it used to do in previous games, that's why we need to introduce the entry manually in plugins.tx. What I suppose it does as well is keeping the launcher from overwriting what you just introduce as a new load order, if you don't have it you need OFC to follow my first instruction and make plugins.txt read only, I still do this just to make sure the file is loaded in game.
Also any news on NMM supporting Fallout 4 ?
For graphical or sound you don'y need to follow these steps.
No Idea about when NMM will work, you better ask Nexus staff for that one.
Not sure how much more explicit he/she would have to be for some folks to understand "No matter how basic it is to install Fallout 4 plugins, some people keep asking how to do it, I understand that a lot are new users of Nexus and some playing Beth's games for the first time.
So this is a a short tutorial how to do it.", but apparently some folks didn't get it.
Some people only know how to play a game - "try to put the others down". Doesn't really affect me has I have worse things to suffer for.