Then add mods back in groups to see when crash happens (I add about 10 or 20 at time, then add one or two to find issues). In skyrim, you would use COC riverwood, or coc whiterun to go to those locations.
Turn off all mods and use clean save or console start (from loading screen use the console to start in an area - coc sanctuaryext for example will place a test character in sanctuary) to see if your base game is messed up. If you can't identify a specific mod easily, the brute for approach may be necessary ("I keep crashing when running to gunners.then look at gunner or armor overhaul mods, etc.)Īlso, if a crash can eventually be tied to a specific item or object, examine that object in the console - you can get an id, or even a mod name which will help in investigation.
Then think about what mods might do that. So it helps to think about what the player was doing - who was near, what common assets, sounds etc. With some combos of mods, it might even layered even more complexly (like only crashing at night due to lighting mods, or only when approaching the area from a specific direction, etc.) Most crashes are not really random - there was a fixed object (like a tree, building, etc.) or a non fixed object that had an issue (an npc with issues, or even with a specific weapon, etc.).
Now, usually these issues are focused around specific objects, npcs or locations. - Removing mods from a save - the game does not like it when mod that alter game mechanics are removed - this can lead to save corruption over time.- Mod authors not correctly removing objects from the game - either specific objects or even terrain elements (navmeshes) - this is not good as when the base game or another accesses these objects - instant CTD.The same piece of armor, the same mailbox, the same building. - More than one mod changes the same asset, and they conflict in how they do it.Here is my generic "CTD advice" I post regularly on reddit Ĭrashes are usually caused by a few reasons
(I mean, how could vortex detect something needs a program development library - the windows visual c++ files).Īlways a good idea to check the requirements section of any mod, just in case.įinally, while Buffout is an amazing (yet technical) tool - there are the good old fashioned methods for hunting down CTD issues. I am guessing vortex is not detecting some of the requirements because buffout is NOT a regular esp or esm files that needs other files - thus no working in vortex. I get it can be frustrating - but some tools are not quite for the general modder - but have needs for someone more comfortable with advanced development tools. So, buffout 4 is a very advanced tool - and while that is not spelled out directly in the description - the technical nature of the requirements are a strong indicator.
0 kommentar(er)
