Runtime Error crash (MS Visual C++ Runtime Library)

[Rabblerouser]

This is an unusual one.

And one very interesting thing is I've only picked it up when fast-traveling the Mojave Outpost.

 

I've been able to go to the Mojave Outpost before, but for some reason now it's crashy everytime I get fast-travel there. I'm not sure if any of my mods do anything to the Mojave Outpost, though.

 

I'll see if I can walk there normally, but just give me a moment on that.

 

Interesting, I CAN walk there normally.

 

 

 

 

Load order:

 

[X] FalloutNV.esm
[X] Sexout.esm
[X] SexoutCommonResources.esm
[X] SexoutSharedResources.esm
[X] SexoutPregnancyV3.esm
[X] SexoutSlavery.esm
[X] SexoutLegion.esm
[X] SexoutStore.esm
[ ] MikotoBeauty.esm
[X] Project Nevada - Core.esm
[X] Project Nevada - Cyberware.esp
[X] Project Nevada - Equipment.esm
[X] NSkies - Vanilla Edition.esm
[X] ELECTRO-CITY - CompletedWorkorders.esm
[X] ELECTRO-CITY - Highways and Byways.esm
[X] SexoutFleshedOut.esp
[X] SmallerTalk.esp
[X] SexoutZAZ.esp
[X] SexoutRocket.esp
[X] SexoutRapeGame.esp
[X] SexoutDiscounts.esp
[X] st.esp
[X] SexoutCompanions.esp
[X] SexoutFadeToBlack.esp
[X] NVWillow.esp
[X] SexoutWillow.esp
[X] SCS - CombatArmour.esp
[X] SexoutCheckMeOut.esp
[X] SexoutClothingEval.esp
[X] SexoutSexAssault.esp
[X] SexoutLust.esp
[X] Sexout-Wear-And-Tear.esp
[ ] MikotoBeauty.esp
[X] SexoutConsequences.esp
[X] SexoutFiends.esp
[X] SexoutKhans.esp
[X] SexoutKings.esp
[X] SexoutNCR.esp
[X] SexoutPowderGangers.esp
[X] SexoutWorkingGirl.esp
[X] SunnyCompanion.esp
[X] SexoutSTDs.esp
[X] SexoutBreeder.esp
[ ] ELECTRO-CITY - Darker Nights.esp
[X] Alternative Start.esp
[X] The Mod Configuration Menu.esp

 

[RitualClarity]

I have never seen this error in the way that you describe. Perhaps you can...

 

1) Verify Cache for your Steam Game. Perhaps some files have become corrupted in the game.

 

afterward if that doesn't fix it...

 

1) Load a earlier save.. very early say around Goodsprings.

2) use command prompt `tmm 1 and have all locations unlocked.

3) See if it still causes a crash to desktop when traveling to the Outpost.

 

This should help rule out any save game corruption. Since it is only for one location the only thing I can think of is some mod made bad changes to the outpost and that is causing the crash. If still no luck check the mods you have for any changes to the outpost.

 

 

[Rabblerouser]

I have never seen this error in the way that you describe. Perhaps you can...

 

1) Verify Cache for your Steam Game. Perhaps some files have become corrupted in the game.

 

afterward if that doesn't fix it...

 

1) Load a earlier save.. very early say around Goodsprings.

2) use command prompt `tmm 1 and have all locations unlocked.

3) See if it still causes a crash to desktop when traveling to the Outpost.

 

This should help rule out any save game corruption. Since it is only for one location the only thing I can think of is some mod made bad changes to the outpost and that is causing the crash. If still no luck check the mods you have for any changes to the outpost.

Doesn't that have the potential to fuck up my game? The verify cache, that is.

[RitualClarity]

The verify cache shouldn't cause any problems to the game. I have used it many times and so far have had no troubles and it usually helps when something extremely strange happens that can't be explained elsewhere.

 

The save part .. you will be using an earlier save to test. I didn't mention don't save this test work. The only thing that it might "fuckup" is the auto saves of your games. If you are running CASM than there might be several saves that are created while you test. If you are concern make a save before going back and name it appropratly like "pre-testSave" or something like that. Then you can go back to the original save.

 

As I said this is an unusual problem. I am just helping eliminate some of the most common issues and basic testing to see if it is something in game or outside of the game.

[RitualClarity]

If you are still concerned with the verify cache causing problems make a zipped file or just basic  copy of the FNV folder. The entire folder. Then if something does cause problems you can just "copy back" to the folder. No problems. It is a good safety net anyway to do before you start trying to fix the issue. If you had done that before (like I do many times) you could just go back to the previous situation and play from there. unless there was something completely boned from the game before.

[Rabblerouser]

Can't I just create a new save instead of loading an earlier one?

Sorry for all the questions.

[RitualClarity]

Using the previous save is to help determine if there is something corrupted with your current save. If you create a new save there might still be something there that can mess things up. If you are concerned with the saves zip them up in the doc folder just in case. Then after testing you can return them to their normal status and not worry about anything messing up your progress.

 

The goal here is to go back as far as possible to see if there is something wrong. This is to rule out various problems. Since we both don't believe there is anything that can be causing some world space issue at the outpost and it only crashes on the outpost there is something wrong and it might be in the save. I assume that you have already been there and interacted with the characters there. Your interactions might have done something and there might be some script or process that is hung up. That might just be stuck in your save. If you go to a previous save before you ever entered the outpost and then use the fast travel it will determine if this is a case or if work needs to be looked at elsewhere. I hope that it is the answer otherwise it will be painful and you will have to diag each mod until you find the current issue. That will mess up your saves if you don' t have backups. and if you do find the mod that is causing the problem that still might be an issue using your old saves.

 

I don't use auto saves. They screw up way to much. I use CASM and manual when I enter the game and exit the game or after I have accomplished some major event.

[Rabblerouser]

I decided to try the savegame thing before verifying. Went there fine. Tried it again in my main save... went there fine.

 

That was odd. It was doing it consistently before. Even after a restart. Weird.

[RitualClarity]

Like I said it was a "Weird" error. Since it was consistant we needed to try to resolve the issue and fix it so that you can fast travel there. No problem now. There might of been something going on in the background or such. Fallout has a very finicky engine.

 

Now you can mark this thread solved. . The answer must be to wait some time for the game, computer to decide to work correctly... hum... maybe it was afraid you'd kick it.