Difference between revisions of "User:DavidJCobb/Binary search (troubleshooting)"

Jump to navigation Jump to search
no edit summary
imported>DavidJCobb
(Created.)
 
imported>DavidJCobb
Line 1: Line 1:
Sometimes, you may run into a problem or incompatibility with one of your mods and have no easy way to know what's causing it. In these cases, you'll want to use a '''binary search''', wherein you cut your list of mods in half, and then cut those halves in half, and so on, until you find your target mod.
Sometimes, you may run into a problem or incompatibility with one of your mods and have no easy way to know what's causing it. In these cases, you'll want to use a '''binary search''', wherein you cut your list of mods in half, and then cut those halves in half, and so on, until you find your target mod. If you have a large mod list, then this will still be a slow process, but it's ''much'' faster than enabling and disabling mods individually.


== Conducting a binary search ==
== Conducting a binary search ==
Line 13: Line 13:
You can generally omit mods from this process if they're obviously unrelated to your problem. For example, a retexture won't cause skeevers to react to your Amulet of Mara, and a perk overhaul won't turn trees into blobs of purple squares.
You can generally omit mods from this process if they're obviously unrelated to your problem. For example, a retexture won't cause skeevers to react to your Amulet of Mara, and a perk overhaul won't turn trees into blobs of purple squares.


Keep the limits of a binary search in mind: it's best for narrowing down problems that are caused by ''one'' mod, so if your problem is caused by a group of mods, you may not be able to identify all of them individually through this process alone.
Keep the limits of a binary search in mind: it's best for narrowing down problems that are caused by ''one'' mod, so if your problem is caused by a group of mods, you may not be able to identify all of them individually through this process alone. It's also not useful for diagnosing the causes of corrupted saves.


== Ideal test procedure ==
== Ideal test procedure ==
These steps should allow you to run quick tests without having to sit through a long introduction, and while minimizing the influence of scripts in the vanilla intro and in alternate start mods.
These steps should allow you to run quick tests without having to sit through a long introduction. It will allow you to test on a fresh playthrough; removing mods from an existing savegame often causes problems of its own.


* Start the game, and open the [[Console Commands|command-line debugger]] in the main menu.
* Start the game, and open the [[Console Commands|command-line debugger]] in the main menu.
Anonymous user

Navigation menu