Jump to content

hamletsdead

Premium Member
  • Posts

    13
  • Joined

  • Last visited

Nexus Mods Profile

About hamletsdead

Profile Fields

  • Country
    United States

Recent Profile Visitors

4464 profile views

hamletsdead's Achievements

Rookie

Rookie (2/14)

1

Reputation

  1. For everyone still having this issue: the "for dummies" guide to fixing the problem is here: https://bsn.boards.net/thread/18337/dragon-origins-toolset-setup-server. It works perfectly, just did it this morning.
  2. @zloybelka, thanks for posting the link to the guide, works like a charm, just installed the toolkit and the 2022 SQL and SSMS this morning. Took an hour of futzing around because I missed a step, but the guide is basically "for dummies" and is super easy to follow.
  3. Has anyone fixed this? The mod with the patch has been removed, and I just got 56000+ instances of this spamming my scripts, which means all my animations are hosed and my script lag is horrible. Boo-hoo, I know, but this should be fixed, no? PSA: for anyone experiencing the problem, go back to a save before your stack dumps got spammed, open xEdit, go to Dragonborn.esm, type 040177db in formid box, then just go into Talvas Fathyron's keyword package and remove anything related to DLC2PillarBuilderActorScript or DLC2Pillar. There are two entries, just delete them and they will revert to NULL REFERENCE. This will show up as an error if you ever check Dragonborn.esm for errors (but why would you) but it stops the script spamming entirely. Talvas was never meant to go work on the bloody pillars at night with the rest of the idiots, and he won't go, so the script is just piling up uselessly until your game breaks. Another Bethesda victory, still unfixed 11 years later.
  4. Thanks for posting the fix to this -- that red forehead in CK was driving me bloody bonkers. Renaming the tintmasks file works flawlessly.
  5. Thanks for this -- I had no idea the orange boxes in Wrye Bash indicated that there was a serious problem with masters being out of order. Easy to miss some conflicts in a 500 mod load order, and this is an easy fix, so thanks again.
  6. You can set up MO2 to download all your mods to your D drive (e.g., an HDD) and then install the game on you main C drive (on an SSD). It plays just fine that way. I set my game up that way initially and just moved over all the files from D to C to see if the game plays and loads better/faster, but I'm not seeing vast improvements by consolidating them all onto the C drive. And just a word to the wise for people moving their mods from one drive to the other with MO2. Make a backup of you load order for both panes and save it on your desktop, as MO2 automatically changes the priority of mods and alphabetizes them when you make this change. I learned the hard way -- took me hours to get my load order back to (approximately) where it was.
  7. Thank you!!!!!! I just spent the last 5 hours CTD-ing after the Siege of Whiterun and couldn't figure this out. Miracolo.
  8. CTRL + F5 refreshes the cache, then you'll see beta version.
  9. Sos muy bueno, senhor. Bien hecho.
×
×
  • Create New...