Jump to content
⚠ Known Issue: Media on User Profiles ×

vachnic

Premium Member
  • Posts

    5
  • Joined

  • Last visited

Nexus Mods Profile

About vachnic

Profile Fields

  • Country
    Netherlands
  • Favourite Game
    Morrowind, Skyrim, FO3, FO-NV, FO4

vachnic's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. If you mean the update to 1.6.1130: It was almost unborked. if you mean the update to 1.6.1170: It has been borked all over again.
  2. The purpose of making a bashed patch is letting wrye bash "bash" together all the mods, as to try and correct any potential errors/ conflicts between all the mods you have installed. Which it does a pretty decent job of. However, the more mods you install, the more conflicts are likely. I don't know if you did this, but after creating a bashed patch, you really should check the patch with xEdit and check if Wrye Bash kept the functions you wanted/ expect. Go through all the edits in the bashed patch and manually correct things if needed (drag and drop the function you want into the bashed patch). And always place the bashed patch as low as possible, but when using LOOT, it should do this automatically.
  3. Been having this problem off and on since the last update of Skyrim, which I am sure is unrelated but gives an indication of time frame, I guess. Maybe it has been going on longer, but I hadn't noticed until I started checking for mod updates more often for that reason. So far for today there hasn't been a download history the whole day.
  4. I had this problem as well (in the "widespread" version). I read somewhere that this was caused by an outdated version of Full Dialogue Interface . Once I updated, the problem was gone for me.
×
×
  • Create New...