Jump to content

PurpleYellowRosa

Citizen
  • Posts

    6
  • Joined

  • Last visited

Everything posted by PurpleYellowRosa

  1. I have a very large load order (3500+), which, through a lot of effort, I managed to make remarkably stable. Until, very recently, I decided to update my game from 1.6.353 to 1.6.640, since several mods are no longer supporting the older version. I made double sure to update every SKSE dll, including Engine Fixes, as well as the loader, and then launched the game. But it crashed as soon as it got to the splash screen. I used the SKSE log to try and find the culprit, which on first glance appeared to be dTry's Key Utils. I disabled that mod and launched it again. I then had to repeat the process a few more times; Precision and TDM were the only mods to actually give me error messages, saying I had an unstable game and should download Engine Fixes (which I have, to seemingly no effect). Upon disabling them and finally getting to the menu screen, I got several notifications from SRD telling me it had failed to parse yaml files, indicating something was still going wrong at runtime. I then tried starting a new game - and was immediately put at the carriage scene, despite having Alternate Start enabled. My conclusion is that, for some reason, MO2 is simply not loading a bunch of mod files, including esps. This never happened on 1.6.353. The only time I have ever seen something similar was when I used the Best of Both Worlds version to try to precache grass. Is this a known issue? Is there any fix beyond going back to 1.6.353? EDIT: My Engine Fixes log seems to be throwing up errors for every plugin: https://ufile.io/jffn057e
  2. It worked (cheers!), but didn't generate a debug log for whatever reason. The file is there, there's just no text in it.
  3. Still no good, but this time I got an access violation instead of range check error. Here's the logs: https://ufile.io/n539187c
  4. Apologies for late follow up on this. I tested two different things: undeleting references to use the new Dyndolod.dll NG (same error) and doing LOD generation with the same parameters but no seasons (success!). So I assume it has something to do with seasons. I'm attaching all the logs from my latest attempt, including the seasonal LODGen logs, as well as the bug report. https://ufile.io/rv7j6ekj Edit: It also didn't work with the alpha-131 exe linked by sheson on this thread. Edit 2: Downgrading to alpha-128 "fixed" the problem. Will wait for more fixes before updating back to current.
  5. The process runs for about 42 minutes, then bugs out after finishing Object LOD for Tamriel (and seasons). It's likely from a mod I installed, since the error happens on multiple DynDOLOD versions, I'm just having trouble identifying exactly which mod. My last successful run was two days ago, so potentially I could binary test it, but I'd prefer to try to document the process and actually "solve" what's causing it. My debug log is about 840 MB, so I'm attaching the final section in hopes that it can help.
×
×
  • Create New...

Important Information

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