HOW TO USE TES5EDIT TO VIEW CONFLICTS MOD
HOW TO USE TES5EDIT TO VIEW CONFLICTS PATCH

Create a new executable in Vortex by clicking on Add Tool and choosing new. 5.4.2 - Very Quick Show Conflicts with Vortex.

HOW TO USE TES5EDIT TO VIEW CONFLICTS MOD

If it works, you should publish it to the Skyrim Nexus so other people can benefit from the patch. If you do not use MO2 then consult your mod managers documentation for adding and launching executables from the mod manager.

HOW TO USE TES5EDIT TO VIEW CONFLICTS PATCH

Or, if you've got any experience in the matter, create a compatibility patch yourself. If there are no compatibility patches or known issues between the two mods, then decide which of the two mods you value more and get rid of the other one. I recommend checking for any compatibility patches between the two mods, as well as the mod's mod pages to check for any notes about the conflict. If the game crashes once you test having those two mods activated, as well as Skyrim.esm, Update.esm, and your DLCs (if applicable), then you'll know those two mods conflict.

If the game stops crashing once you deactivate a certain mod, try deactivating all the mods you have except for the mod that just caused the crash, and the one that originally caused the crash (see step 4).

Now you'll keep that mod activated, and deactivate the mods that you already have activated one by one, testing the game each time.

Once it crashes, you'll write down or remember the mod that you just tested (the one that the crashed the game after it's activation).

If it doesn't, repeat this step until it crashes. Once you've ensured that it's loading fine and without crashes (if it loads a new game then that counts) then activate another mod (and keep Skyrim.esm, Update.esm, whatever DLCs, and the mod you just tested activated). If it does, then you may need to create a new game to use that mod. If it crashes then, try making a new game to see if that fixes the problem.

If it gets to the starting screen without a crash, then try to load a save.

This will probably save you a lot of time. Alternatively, you can start with all your mods activated and deactivate them one by one.

Open up Skyrim, or whatever mod manager you use, and deactivate all the active mods you have loaded except for Skyrim.esm, Update.esm, your DLCs, and the mod you want to test.

Download TES5Edit, run it, and if there are mod conflicts or any other mod problems, it will detect those for you. The latest stable release can be found on. Check all your mods to see which ones need a dependency (easiest way is to use Nexus Mod Manager to see the file info) and disable the conflicts. This is a tedious process, but it's fairly simple. I am the original developer of 圎dit, originally a conflict detector (TES4View), which initially morphed into a full editor for Oblivion (TES4Edit) and has been expanded to support all following Elder Scrolls and Fallout games from Bethesda which share the same basic file format. So first what you want to do is isolate which mod is causing the problems.

How to use tes5edit to view conflicts