file corruption

[jackiethefur]

every time I try to load my saves its just an endless loading screen, my friend says its file is corrupted. how do I fix this?

 

[JimboUK]

Load another save and then load the one you want once you get in game, if you don't have another then starting a new game will work too and loading from that should work too.

[Watercrown]

I've been seeing a bit of odd behavior regarding saves lately as well.

 

So basically, when I first load up the game I can load a save just fine. But if I die or attempt to load another save it will just hang at the loading screen prompting me to end the task or continue to wait (it will never finish loading).

 

But it's just random when this happens.

 

For example, I spent some time restarting, loading a save then attempting to load another save a few times. Sometimes it would let me load other saves just fines. Other times it would just hang on the loading screen after that initial first load.

[dubiousintent]

Are you exiting the game to the desktop each and every time before re-loading? That is necessary because the save game files do not contain everything the game loads when it starts up. You likely are getting hung because it's missing something only a "new game session" will load.

 

Do not use the game's "auto-save" feature. See the sub-topic 'Issue: CTD on interior/exterior/"fast travel" cell change' in the wiki article Fallout NV Mod Conflict Troubleshooting for the explanation and alternatives.

 

-Dubious-

[Watercrown]

I'm using the mod "limited saving" which disables auto saves by default. I've been using it for a while now without a single issue.

 

I'm not really sure what you mean with your first question.

 

1. Start the game up.

2. Load any save.

3. Open up menu, load another save (or die forcing the game to load up the latest save).

 

At this point the game will become unresponsive. There doesn't seem to be anything I can narrow down as the cause. This happening is completely random. Other times step 3 works fine and I have zero problems.

[dubiousintent]

By my question I mean "are you closing the game" (where starting the game and then exiting to the desktop is considered "one game session") between opening one save and then another. Please see the 'Fourth Rule: Reloading "save game" files' entry in the 'First Timer Advice' section of the wiki "FNV General Mod Use Advice" article.

-Dubious-

 

 

 

[Watercrown]

By my question I mean "are you closing the game" (where starting the game and then exiting to the desktop is considered "one game session") between opening one save and then another. Please see the 'Fourth Rule: Reloading "save game" files' entry in the 'First Timer Advice' section of the wiki "FNV General Mod Use Advice" article.

 

-Dubious-

 

 

 

 

Ah, I get you.

 

In general, that's not something I have been practicing unfortunately. How does this work in terms of the game autoloading the last save when you die however? Are you suppose to quit the game and manually reload it after each and every death? This is where I run into issues as well, sometimes the autoloading will work fine, other times it will just hang there.

 

Been doing my own testing...

 

So the problem might be NVSR related. I disabled it and everything was loading fine each and every time... but again, because the problem is random to begin with it's hard to tell. Obviously, I can't go without NVSR so I just messed around with the major settings.

 

bHookCriticalSections = 0

 

Seems to have eliminated the loading issue... however, it does make the game stutter quiet a bit when the game is loading a new cell/textures.

 

Going to mess with the different options in CriticalSections because going back to the game hitching like that is a huge downgrade so where it was before (game just running near perfect).

 

Have you seen any cases of NVSR causing loading issues dubious?

Edited March 21, 2018 by Watercrown

[dubiousintent]

Re: NVSR. It's a fix for "suttering". Disabling it can lead to a resumption of such problems at any time. One of my standard questions for people is:

 

* Are you running Win10? Did you get the "Fall Creator's Update" of 2017 (FCU aka "RedStone 3")? Do you have "New Vegas Stutter Remover" (NVSR) installed? If all three are "true", then please see the 'Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play' (and other "heap size") entries in the 'Solutions to Performance problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

I've now put that list of standard questions and suggestions in the 'Common Game Problems' section of the wiki "FNV General Mod Use Advice" article.

Re: Stuttering or "micro-stutters". All visual stuttering problems are caused by the video stream having to wait for the "art assets" required to render the display OR the game writing something to disk (such as a save game file or logging). Mostly these are due to the hard disk drive being orders of magnitude slower than VRAM, with System RAM (e.g. "ENBoost") and "solid state drives" (SSDs) being in between. Keep in mind that this game was designed for older PC and XBox console systems, and it is now possible for your new "latest and greatest" gaming machine to be faster than it can handle. There are internal design choices that cannot be overcome. The following are "mitigations" that have been found to help some people.

Please see the following entries under the 'Solutions to Performance problems' section in the wiki Fallout NV Mod Conflict Troubleshooting" guide if you haven't already.
* 'Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters'
* 'Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed'
* 'Issue: Win10 Screen tearing in "Borderless Windowed Mode"'
* 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' for other settings that can indirectly affect micro-stutter.
* There are also some NVSR configuration suggestions under the 'Issue: Game in slow motion' and entries.
* The 'Issue: What's with these Solid Green billboard signs in the distance (LOD)?' entry under the 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' section can also help if your problems started after you installed VWD/LOD texture packages.
* If you are using CASM or some similar "auto-save" mod to manage your save game files (recommended), try increasing the "time between saves" set in the "save frequency"; and reducing the number of occasions it saves to the minimum (e.g. disable most "Autosave Events" in CASM) and see how that impacts the game seeming to freeze temporarily.
* If you have "NVSE logging" enabled (see the 'Checklist Item #4' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide), disable it until actually needed.

Reading from or writing to disk for any reason is the slowest thing the game does.

As you can see, there are a number of things that can underlie your problem. If one of these doesn't fix it, I would be interested to hear about any eventual solution that does.

Re: Auto-reload after a death scene. Don't know, but given the developers track record with other save files, I prefer not to risk it. Quit every time.

 

-Dubious-

[Watercrown]

I ended up following a lot of those suggestions last time I had an issue.

 

So I did notice NVSR seemed to be the cause of the problem. When I disabled it I was able to load files just like usual. However, I got the typical stuttering which makes the game unplayable.

 

So I tested all the major settings and bHookCriticalSections seemed to be the cause. When disabled the game worked mostly stutter free except when entering new cells which had a very noticeable hitch that was not present with the option in use.

 

I messed around with the settings under criticalsections and I found that setting iDefaultMode = 1 made the game hitch free and still let me load my save games just fine. So I don't know what any of these settings do and I am honestly just grasping at straws because that stutter when loading cells is really distracting and I do not want to play the game like that.

 

I did get one really random crash so far, so I don't know if stability is the price for that option. I played for a good 2 hours so far so maybe it was just a one off... I hope.

[dubiousintent]

The "Master" section is where you tell NVSR which "feature" sub-sections of it's code to use. Most subsections are disabled by default (= 0).

 

Setting "iDefaultMode =" is in the "CriticalSections" subsection of "sr_New_Vegas_Stutter_Remover.ini". "CriticalSections" only gets accessed when the "Master" subsection has "bHookCriticalSections = 1", which you say you disabled (= 0). So either that occurred before you disabled it, or it's a "placebo" effect. ("iDefaultMode = 1" just means NVSR use the vanilla mechanism anyway.)

 

-Dubious-