Conflict Resolution Walk-Through

Below is a detailed walkthrough for finding the source of issues. Please use it if you are unsure how to pinpoint issues. Any information provided below not specific to the Dev Aveza can be applied to finding issues with other mods as well.

• 1. Before you do anything, verify that you have correctly installed SKSE. The Scripts folder is not optional. SKSE is not optional.

  2. To backup your save games, go to Documents\My Games\Skyrim\Saves and move the entire folder to a safe location, like your desktop.

  3. If you have ever made any changes to your .ini files, grab Skyrim.ini and SkyrimPrefs.ini from Documents\My Games\Skyrim as well and put them with your save folder.

     • Load up the default Skyrim Launcher with Steam, it will regenerate the .ini files for you. Then quit out again.

  4. Run LOOT, or the internal sorter in Vortex or Mod Organizer, and then load the game with SKSE. To quickly reach the airship, open the console on the Main Menu and enter coc _da_skyship_interior_cs.

  5. You are now in the Full Cabin interior. Try to reproduce the error you were having priorly. DO NOT test with the cannons model, it is still alpha.

     • If the error involved the beacon, you may choose to use coc whiterunexterior01 instead at step 3 above.

     • To test with the beacon, open the console again and enter help beacon. Look for the WEAP entry Airship Beacon.

     • Type player.additem XX0400ee 1, the X's to be replaced by the code you searched for in the previous step.

  6. If the issue is resolved without removing mods, we suggest you start a new game, as you are likely suffering from save game corruption.

     • If you had to remove your .ini files, put just them back in and rerun steps 3 and 4. If the issue returns, your .ini files are causing the issue. You may be able to salvage your save game, but you will likely have to use clean .ini files.

  7. If the issue remains, uninstall everything except for SkyUI, SKSE and the Dev Aveza. This includes any ENB or similar core folder mods.

  8. Double check your .esp list. It should look like this:

     • Skyrim.esm

     • Update.esm

     • Dawnguard.esm (if installed)

     • Hearthfire.esm (if installed)

     • Dragonborn.esm (if installed)

     • SkyUI.esp

     • DA_Skyship.esp

  9. Repeat steps 4 and 5.

  10. If you are having the problem at this step, uninstall everything remaining and verify your files through Steam. Then reinstall SKSE, SkyUI and the Dev Aveza and repeat steps 4 and 5. If the problem continues to persist at this point, please ensure you are correctly installing SKSE (in particular, the Scripts folder, which is not optional) before testing again.

  11. Once the test with no mods is done, add in the Unofficial Patches for your game, and repeat steps 4 and 5 again.

  12. After testing with just the Unofficial Patches, test your ENB now if needed. If this causes issues, please do not bother reporting as we cannot help you.

  13. If you usually use a controller, do a quick test with it now. If this causes issues, we suggest you find a way to use the ship with your keyboard.

  14. If you have not yet found the issue, add some of your mods back in. Ten is an easy number grouping to work with. Repeat steps 4 and 5.

  15. If the group of mods works, remove them again before adding the next set.

  16. Repeat steps 14 and 15 until you find a problem.

  17. Once you've found a group of mods containing a problem, remove half of them and with the other half installed repeat steps 4 and 5.

      • If the problem is not present, swap the installed mods to the other group and repeat steps 4 and 5 again.

      • If the problem is present, remove more mods and repeat steps 4 and 5 again.

      • Continue this cycle until you find the one causing the issue.

      • Remove the problematic mod, then recheck the remaining nine before moving to the next group.

  18. If the problem disappears before finding a single mod causing it in a set, then:

      • Load up the last group in the set that caused issues.

      • Remove each mod one at a time until the problem goes away.

      • Test each mod in the set individually with the mod removed in the previous step.

      • If the issue does not present, restart this cycle and remove mods one by one except the priorly found partial problem

      • With two partial problem mods found, test them against each individual mod remaining.

      • This should leave you with one or more specific combinations that do not work with the Dev Aveza.

  19. Write down the names of any mods found to be problems during steps 17 and 18, noting specific combinations where needed.

  20. Even if you find a problematic mod, continue checking sets to ensure there are not multiple issues.

  21. Once you have checked all of your mods, load up all mods that have not been removed for causing issues in testing, and run steps 4 and 5 again.

  22. If you still have issues, we will now test larger sets of mods to check for multi-mod issues.

      • Load up half of your mods and follow steps 4 and 5. If there are no issues, repeat with the other half.

      • If there are issues, follow the directions from steps 17 and 18 until you find specific problematic combinations. Write them down.

  23. Check the mods you have written down for updates, and the problematic combinations for known incompatibilities with each other. It is possible that the issue is not related to the Dev Aveza at all, but presents when using the airship because of its reliance on custom scripts.

  24. If all the mods on your list are up to date and are not known to be incompatible with each other, you may now post your bug report here.