Is it necessary to set fallout.ini file to not read-only?

[Lasharamax]

Hi guys. Does anyone know whether it's necessary to make fallout.ini file not read-only in case of Vortex MM? I really struggle with it, because every time I install texture mods it causes many troubles with textures not applying (ofc Archive Invalidation is set to "on"). Thanks

[sopmac45]

That has nothing to do with Vortex or NMM and this forum is for Vortex only.

 

You should post that question in the proper forum.

[Lasharamax]

That has nothing to do with Vortex or NMM and this forum is for Vortex only.

 

You should post that question in the proper forum.

Emm...This question is directly relevant to Vortex features, so I did right. And the question is super easy tbh

[Guest deleted34304850]

When you say archive invalidation is "on" what setting is that? I'm not at all familiar with it.

 

What I do have, which is going right back to when Fallout 4 came out is as follows;

 

In FalloutPrefs I have bEnableFileSelection=1 in the section marked {Launcher]

 

and in FalloutCustom.ini, in the section marked [Archive] I have bInvalidateOlderFiles=1 and sResourceDataDirsFinal=

 

None of my fallout4.ini, falloutcustom.ini or falloutprefs.ini are marked as read only. This must be something local to your environment because aside from making some backup copies, I do not think Vortex changes these files, or their permissions.

 

One other question - for clarity - your title says this;

 

Is it necessary to set fallout.ini file to not read-only?

 

Not read only would imply read/write - do you mean your file is read only and you want it to be read/write or is your file read/write and you want it to be read only?

 

btw i wouldnt say that a question is easy - it may have an easy answer but the question itself, as you can see, can be worded so that it is ambiguous.

Edited April 14, 2019 by 1ae0bfb8

[Lasharamax]

if the question is easy, then what's the answer?

not actually sure why you think it's related to vortex and/or nmm. as far as i know, vortex doesn't make any edits to fallout.ini - why do you think it does?

Even if a question is easy it doesn't mean that everyone knows the answer, right? This question should be easy for everyone who has a basic understanding of how this software works, and I am not one of them, unfortunately. I said nothing about Nexus MM (and yea "MM" is just a short form of "mod manager", not NMM). And the question was about Vortex Archive Invalidation that is directly related to this topic (just check posts below)

[AugustaCalidia]

Hi guys. Does anyone know whether it's necessary to make fallout.ini file not read-only in case of Vortex MM? I really struggle with it, because every time I install texture mods it causes many troubles with textures not applying (ofc Archive Invalidation is set to "on"). Thanks

Please provide more detail using the guidelines found here: Vortex Support Forum.

[FlamingCheeseMonkey]

If textures are not being applied that may suggest that you may have disabled the auto-deploy function of Vortex, which means that after you've finished installing mod(s), or changing up the conflicts, you'll want to hit the "Deploy Mods" button in the "Mods" section of the software.

 

Edit: This is, of course, assuming that you have the ini set up correctly. Which Fallout game are you playing by the way?

 

I'm asking because for Fallout 4, I know for a fact that some author's recommend that users list every single texture bsa in the list within ini, while there are guides that say to put nothing in the list, as the game will apparently read all of them automatically (although this doesn't seem to work for some/most people[?]).

Edited April 14, 2019 by FlamingCheeseMonkey

[rmm200]

I can only tell you my settings.

For FalloutNV, Fallout.ini is read only. FalloutCustom.ini is RW.

For Fallout 4, Fallout4.ini is RW. Fallout4Custom.ini is RW

This is in Documents/My Games.

Everything works for me.

[HadToRegister]

Here's what I have, using Vortex for all


Fallout 3 - Fallout.ini is NOT Read Only

FaloutNV - Fallout.ini is NOT Read Only

Fallout 4 - Fallout4.ini is NOT Read Only


Fallut 3 ini also has -

 

bLoadFaceGenHeadEGTFiles=1 (helps to stop face textures not matching neck, like you see in FO4)

bInvalidateOlderFiles=1

bUseArchives=1

_______________________________

FONV ini also has -

bLoadFaceGenHeadEGTFiles=1

bInvalidateOlderFiles=1

bUseArchives=1

______________________________

FO4 ini also has -

bInvalidateOlderFiles=1

(and the Workbench cheat)

[Workshop]

bInfiniteItems=1

[AugustaCalidia]

Using Vortex I have these settings:

 

Fallout 3 - "Fallout.ini" not read only (r/w)

 

Fallout 4 - "Fallout4.ini" not read only (r/w); "FalloutCustom.ini" not read only (r/w)

 

Assuming your question concerns Fallout 3, does your "Fallout.ini" [Archive] section have the the last four lines shown in the attached photo? If not, then archive invalidation is not working.