Jump to content

Better backup your ini files before deploying (at least for FO4)


BurnTyre

Recommended Posts

Tonight, Vortex wiped my fallout4prefs.ini and saved an empty file instead upon deploying new mods (one, to be exact, WET). So I had to go back to an older backup and redo all tweaks I had done since that backup was created.

The .baked and .base files of fallout4prefs in my fallout 4 directory were also completely wiped clean. The best way to kill a game is to wipe all found backups of the .ini files as well - lucky me that I have my backups separated from the My Games\Fallout 4\ folder. Unlucky me, that they were a couple of months old...

 

Setting the files to read-only doesn't help too, as Vortex obviously remove that flag instantly (it's the only explanation why I had set it to read-only, fired up Vortex, and it wasn't read-only anymore). Vortex wants full control of your game setup - for reasons completely beyond me. In my opinion, the .ini-files of a game should be touched only by the game itself (via its settings options) or the owner of the game - and that second one only if he or she is fully aware of what he or she is doing. But never ever by 3rd party software.

Since switching from NMM to Vortex I had quite a load of problems, but that one really made me angry. It's now 04:28 am in Vienna, and I wanted to go to bed at 03:30 - thanks, Vortex. An hour of my lifetime wasted on rebuilding a perfectly working fallout4prefs.ini, just because Vortex decided to wipe it.

 

So before firing up Vortex, better make a backup of all your .ini files, just in case, EVERY time you use Vortex.

Link to comment
Share on other sites

Did you by chance import your mods from NMM?

I currently run Fallout 4 with 118 mods. Have - for years. I have never seen anything like this.

 

Let me see if I can give you something.

You shot yourself in the foot somehow, and I am not terribly motivated to figure out how you did it.

 

I suspect what happened is that you imported mods from NMM (something I never recommend). NMM also maintains a copy of .ini files.

 

After the import you deleted the NMM copies. That also deleted the .ini file created by Vortex.

Vortex told you disk changes were found and asked if you wanted them merged back. You agreed.

Poof - there went your .ini files. Vortex now has an empty copy of them.

Link to comment
Share on other sites

Can confirm this is happening with Oblivion for me. Since I updated today, every time I add/disable a mod or cause vortex to redeploy in any way it messes with the ini and by extension my graphics settings and my ui (I use darnified dare ui). I have to use beth ini to reapply my settings. This has never happened before today.

Link to comment
Share on other sites

Mandatory question: Did you import Oblivion mods from NMM?

 

The way it is - supposed - to work:

You set up your ini files with bethini.

Vortex notices the files changed on disk.

You get asked do you want to keep the changes or revert.

You say New, and Vortex merges the Bethini changes into it's copy.

 

If something broke in the new build - we will soon be flooded with similar reports.

Link to comment
Share on other sites

I can confirm. I had a new computer, and installed a fresh install of Skyrim (Oldrim). Since I was already going to revamp my entire mod list, I did NOT bother to import from NMM. Instead, I installed all mods fresh using only Vortex (and no other mod manager whatsoever).

 

Fresh install of mods, fresh install of Skyrim. I've been going for about a week now like this and everything was good.

 

Everything was good, that is, until the new update of Vortex today. I tried to play right after the installation of the Vortex update, only to find that my .ini was reset. And now all the sudden my .ini resets with every mod I decide to uninstall or add. Its both my Skyrim.ini and sometimes also my SkyrimPrefs.ini. I would love to know how to revert to an earlier version of Vortex before this recent update, but I also don't want to have to transfer my entire mod list now that it's stable (and its not too much trouble to keep manually putting a copy of my correct .ini back into the files folder).

Link to comment
Share on other sites

I imported from NMM when I was changing to Vortex - but that is quite a while ago.

I didn't really care yesterday, but yes, there was an update yesterday, just checked, I'm having 0.18.11 - that explains it. Well, my advice in the OP still stands: Better backup your inis - but I have to add: Every time you do something with your game installation, if you add or remove mods, etc. - it's one more click and believe me, it's worth it. The hour last night still haunts me. :ninja: :wink:

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...