Jump to content

Vingen

Citizen
  • Posts

    3
  • Joined

  • Last visited

Profile Information

  • Preferred Pronoun
    By Name

Vingen's Achievements

Watcher

Watcher (1/12)

0

Reputation

  1. Hello, just wanted to say that I figured it out — turned out to be an odd mix of things. I think somethings that I cleaned using "Undelete and Disable References" in an older version of SSEEdit caused issues to it (I was using version 4.0.4). The latest versions of SSEEdit and DynDOLOD would just close or crash without a warning message. I was able to gradually chip away by disabling different plugins, and after I did reinstall some of them, they worked fine again. Not really sure what went wrong, but probably a mix of version conflict and me being stupid while editing. Either way, thanks for the help beforehand — you definitely pointed me in the right direction.
  2. Hey, thanks for the quick response! I finished checking for errors in xEdit — it processed over 1.3 million records and found around 52,000 errors. I’m not totally sure how to interpret all of them. Is there a specific type of error I should be looking out for? Or should I try disabling any mods that show a large number of these warnings? This is the log: https://filebin.net/hj01cad2t88bk3ck (ufile stopped working for me)
  3. Hello, I'm encountering an issue where Dyndolod closes prematurely during the processing of Skyrim.esm (Tamriel). I followed BiggieBoss's guide for using xLodgen, Texgen, and Dyndolod. The problem always occurs at the same point, when processing Skyrim.esm. (I also use vortex and game version 1.5.9.7) I’ve already tried the following solutions: Running Dyndolod as an administrator Adding an exception in Windows Defender and Firewall Using Dyndolod both with and without xLodgen Lowering settings to low Running Dyndolod with and without the DLL Setting LockTexconv=1 and RenderSingle=1 Reinstalling Dyndolod Despite these attempts, Dyndolod still crashes at the same point. I've noticed that the RAM usage never gets close to my system’s maximum, so it doesn't seem like a memory issue. Additionally, there’s no log in Windows Event Viewer related to the crash. These are my logs: https://ufile.io/rq6dq4bk, https://ufile.io/0lkeq2xb, https://ufile.io/6it8bd5q Any suggestions or insights would be greatly appreciated!
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.