Fallout NV Save Games

[rmm200]

I think I need some help here.

I am trying to convert Fallout NV over to Vortex. I have my profile set to Local Save Games and Local ini.

In Vortex, I imported the saves I want to the profile i want. They look good.

When I start Fallout NV, the only saves that are visible are the "Global" ones.

How does Fallout NV find it's saves? Is Vortex supposed to be setting a link to the local saves, or does it modify an ini file?

Anyone using Vortex successfully with Fallout NV?

[Tannin42]

It works by changing a setting in the ini file, it should (automatically) set

 

[General]

SLocalSavePath=Saves/<some_id>

 

with some_id being a short, generated id

[RetroDaddy]

Tannin42

Can the path be SET to what I want for saves, or is it dependent on a set rule?

[rmm200]

I think I have found my problem. Fallout.ini is read-only.

 

But I have a couple more questions:

 

I have in MyGames/FalloutNV folder:

 

Fallout.ini

Fallout.ini.baked

Fallout.ini.base

FalloutPrefs.ini

FalloutPrefs.ini.baked

FalloutPrefs.ini.base

 

I made them all writeable.

Could you - or someone - please comment on what the base and baked files are?

 

Edited to add: Well that did not work. All Ini files made writeable, but none are modified to SLocalSavePath=Saves/<some_id>.

They remain "SLocalSavePath=Saves/" after switching to that profile.

 

I tried it with existing profiles, and tried creating a new Fallout NV profile. None point to the local save directory after activating the profile.

 

 

Thanks!

Edited June 21, 2018 by rmm200

[Tannin42]

I've explained this in some other thread. Vortex needs to apply some settings automatically (like the saves path in this case) but also tries to keep your manual settings.

The regular ini file is the only one you should care about, you can edit it (or have tools edit it) like you usually would.

The other two you should just leave alone, just don't touch them at all.

The .base file contains custom settings at the time of the last deployment but none of the changes vortex made.

The .baked file contains all settings from the last deployment including the stuff vortex adds. On deployment, vortex compares the three ini files to figure out which ini changes (if any) were made outside vortex and imports them back to the other files.

 

Is it possible that you have SLocalSavePath set in the FalloutPrefs.ini? Vortex sets that parameter in fallout.ini and I just realised that if that parameter in the prefs file that setting would take precedence.

[rmm200]

I've explained this in some other thread. Vortex needs to apply some settings automatically (like the saves path in this case) but also tries to keep your manual settings.

The regular ini file is the only one you should care about, you can edit it (or have tools edit it) like you usually would.

The other two you should just leave alone, just don't touch them at all.

The .base file contains custom settings at the time of the last deployment but none of the changes vortex made.

The .baked file contains all settings from the last deployment including the stuff vortex adds. On deployment, vortex compares the three ini files to figure out which ini changes (if any) were made outside vortex and imports them back to the other files.

 

Is it possible that you have SLocalSavePath set in the FalloutPrefs.ini? Vortex sets that parameter in fallout.ini and I just realised that if that parameter in the prefs file that setting would take precedence.

 

It looks to me like FalloutPrefs.ini includes everything in Fallout.ini, plus some. 22KB vs 20KB for the bare ini.

FalloutPrefs.ini does indeed include the line "SLocalSavePath=Saves\". None of the six listed ini files show a save path modification by Vortex.

Should I delete FalloutPrefs.ini and start over? I can't think of any important modification in it.

There are no ini files in the Game directory. These are all in Documents/My Games/Fallout NV.

 

Thanks for repeating the definition of "Baked" and "Base". That was just to satisfy my curiousity...

I apologize for tying up your limited time on these questions.

[Tannin42]

So part one of the solution is to remove the SLocalSavePath entry from the Prefs file.
I've been testing a bit with it and the behaviour of the game (NV at least) is very odd. As long as either of the two files contains the default it will use the default, so you'd have to either change the value in both files or take one file out of the equation. Next version of vortex will do this automatically.

 

The other thing is that the fallout nv launcher resets some of the settings in fallout.ini so you should never run it, always start the game directly (nvse or vortex should both do that).

 

I've also done some digging and I'd claim that this issue affects all tools I've seen the source code to. Wrye Bash, MO, the utility libraries of xedit all assume the save game path to be stored in the fallout.ini and ignore the falloutprefs.ini.

 

Since the nv launcher also tends to make the ini file read-only (unlike all the other launchers) I'm tempted to say this is a mostly NV specific problem. Avoid the launcher like the plague, the moment you see it, assume it just broke something and that you may have to go back to your modding tool.

[rmm200]

Final report on this (I hope). I replaced FalloutPrefs.ini with a null file. I made Fallout.ini writable (again). I switched Vortex to Fallout NV.

Lo and behold - the Fallout.ini line was changed to: "SLocalSavePath=Saves\HJYOhYrZ7\", which is perfect.

My null FalloutPrefs.ini was filled in with all category headings, and a few entries like "bDisplayLODBuildings=1". No idea where that came from.

I don't think we can avoid the Fallout NV launcher in all cases - it is the only way I know to set initial options like screen resolution and windowed

If we launch through Steam - we also get the launcher.

 

Again - Thank you Tannin for looking at this!.

Edited June 22, 2018 by rmm200