Jump to content

Crashes galore (yup, yet another one of those threads)


Michlo

Recommended Posts

I've been one of the lucky ones so far, no game crashing except when mod related.

 

That is, until the latest patch. It was listed as a minor patch yet I started having random CTDs. I then realized it was because the FOSE I was using wasn't updated to work with the latest patch. I then updated to the beta 4 version but no go, still crashing.

 

I reverted back to the previous patch and FOSE 1.1 by deleting my data directory and ini files and replacing the data with my vanilla backup. Still crashing.

 

I then completely uninstalled, cleaned out my registry, reinstalled. Still crashing.

 

I uninstalled, reinstalled, wiped out my save games and started over (I wasn't that far in on this go around). Great, it works again. Phew.

 

Until I get part way through the Super Duper Mart mission then crashes galore again.

 

*sigh*

 

I've tried with only mods I was using before with FOSE 1.1. I've tried with no FOSE, I've tried with bare minimum mods. I don't understand how this can still be happening when I've reverted back to how I was when I wasn't crashing.

 

Any ideas please?

Link to comment
Share on other sites

Guys. Conflicts doesn't mean crashes.

 

Crashes happen when a mod doesn't have it's master loaded before it (crash at start).

Crashes happen if there is an error on the structure of a mod (ie, you went trigger happy deleting stuff with fo3edit).

Crashes happen when you have an invalid mesh (ctd when you load a mesh).

Crashes happen when a mod "deletes" something that has already "spawned" in your game (ctd when getting near, entering the cell, or if you're really unlucky, ctd on load because it deleted some part of the landscape).

 

Crashes happen when you have a circular lists (very rare, but it can happen), game freezes i believe on attempt to spawn the list.

 

Crashes happen if you REALLY mess up with a script, most likely through fose (freezes/crashes when that part of the script runs). These are more varied, trying to make an npc shoot the rockit launcher causes ctd, so does calling getweaponammo on a weapon that doesn't use ammo, or additem/removeitem/equipitem with a non-existent / invalid item.. Sometimes the script graciously commits sepuku and the game runs normally, sometimes it just CTDs.

 

Crashes also happen if an area is horribly bloated (many objects, foes, or even extra unnecessary detail on the landscape/infrastructure. These tend to get worse on third person. setting a scene as "complex" really takes off a lot of npc load on a place.

 

Slowdown/Stuttering can happen when loading cells that have many different things with high rez textures, From that point to getting a crash it's just a matter of pushing the engine a little bit more.

 

Crash happens on load when you remove a mod that had a perk, before removing the perk from the player.

 

 

 

Apart from these types of crashes, there are 3 that seem to escape any categorization:

 

Random ctd after playing for a while, no matter what you're doing: This is a weird one that a lot of people suffer, it sounds like bad memory handling on fallout's side. It has been reported that doing THIS may solve them for some people.

 

Crash on save (any kind of save): These things are of mysterious origin, They happen with mods, they happen without mods, it just seems that the game simply left the player data on a bad state. This is one of the reasons why saving constantly is recommended: Loading to an earlier save can and will solve this (tho it may happen again). Damage may extend to some of the previous saves for some unknown reason.

 

Crash on level up: This one i've seen has happened mostly to:

Users who got Anchorage (all of them, so far reported), and has competed it with that character (not confirmed), and users who also have fook (unconfirmed if all the cases have it). The reason for these crashes is still unknown. Removing fook - anchorage or fook entirely didn't seem to fix, removing anchorage however, did the trick.

As a workaround, it is possible to make a backup of anchorage.esm, and use fo3edit to clean it up and remove everything except the new weapons/armor. This has been reported to solve the problem.

Link to comment
Share on other sites

Guys. Conflicts doesn't mean crashes.

Crashes happen when you have a circular lists (very rare, but it can happen), game freezes i believe on attempt to spawn the list.

 

Ugh, circular lists are the devil. It's actually pretty easy to do if you're not paying enough attention. Needless to say I did this once myself (had a lvl list referencing itself which caused the game to instantly CTD on load, couldn't even get into the main menu). Took about 4 hours of searching and deleting stuff from my .esp before I finally found the culprit (it was a fairly hefty 500kb .esp with tons of new npcs and associated equipment/leveled lists and a heavily populated new cell, that took some serious searching).

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...