Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Dez756

  • Rank
  1. Here's Blues Skyrim.esp. I reran DynDOLOD. Traveled to the same place and crashed. Did the same xEdit troubleshooting and identified the same references to IcebergSmall02. See attached screenshots. Removed those references and no crash. The IcebergSmall02 are now coming from Dawn of Skyrim.esp. Dawn of Skyrim (Director's Cut) SE at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com). I'm double checking my installation, although I'm pretty sure this one is correct. If I can't find any installation issues, I'm going to just play with those references removed, unless you think that will cause a problem Blues Skyrim.esp
  2. Nevermind. Saw your Kofi site. Thanks again!
  3. Sorry for the stupid question. I just saw from that page that this patch should not be used for V1.5 of DOS. Removing and then planning to rerun DynDOLOD to see if that cures the problem. Wasn't planning on rerunning Xlodgen and TexGen since there are no textures in that mod but let me know if you recommend otherwise. Thanks for your patient help. You taught me a ton!
  4. This mod is on the main download page for Dawn of Skyrim - Dawn of Skyrim (Director's Cut) SE at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com)
  5. Okay! No crash if I remove two references at the following path in the DynDOLOD.esp. Worldspace>0000003C Tamriel> Block 1,-1> Sub-Block 5,-3>0000BCD0> Temporary >1902677D Placed Object bluesskyrim_0121FA_DynDOLOD_CHILD IcebergSmall02_DynDOLOD_LOD[STAT:0D004028] and >190266D6 Placed Object bluesskyrim_0121FB_DynDOLOD_CHILD IcebergSmall02_DynDOLOD_LOD [STAT:0D004028] I'm sure you recall that the .Net Script Framework crash logs also referred to IcebergSmall02. BluesSkyrim.esp appears to be a patch I added back in 2020, but I can't find it on Nexus anymore. The Mod is called Update by KorruptkSwades. Should I remove that patch and do everything again? Or can I just play with those references removed?
  6. In case it helps, here's a screenshot right as the game CTD's.
  7. Here's my Papyrus log with debug=true. I don't see entries in the Papyrus log exactly like the example in ReadMe. I tried to search for the Form ID of the last entry referencing DynDOLOD ([06/29/2022 - 03:54:57PM] [SHESON_DynDOLOD_LODObject < (BE028E70)>] [SHESON_DynDOLOD_Firstborn < (BE028E5A)>] Enable #2 [Form < (20004052)>] using dyndolod\lod\effects\fxfirewithembers01_dyndolod_lod.nif TRUE False TRUE) but SSEEdit doesn't seem to find anything (although I'm not sure I'm looking in the right spot - I've used SSEEdit for some things like cleaning, adding keywords or heel sounds but never searched for Form IDs). See screen shot for the results of filter for BE028E70. I note that the entries in the log in the last second all seem to concern Creature Framework. To test whether that was somehow involved, I removed CF and all associated mods and traveled (on a new game) to the same Riften Gate. Still CTD'd. Again, though this mod and its associates have been in my load order for literally years! It's so weird that this seems to be the only place it CTDs as I had traveled to most of the other cities before I ran across this problem at Riften. I'm sure this is getting frustrating for you! Should I start (dread) removing mods and running everything (Xlodgen, TexGen, DynDOLOD) again? Papyrus.0.log
  8. Still CTD with meshes removed. No CTD with DynDOLOD.esp only disabled. I'll try to get to the debug=true tests later.
  9. I replaced all five texture files shown for the icebergsmall02.nif in Asset Browser with vanilla textures, checking to make sure the path was correct in the MO2 Data tab. Stil CTD'd at Riften Gate. See crash log. As a test, I again disabled the Dyndolod Output and traveled to the same spot. No CTD. Crash_2022_6_28_15-38-18.txt
  10. Unlike the Meshes, I don't see a way to save the vanilla textures using the Asset Browser. Am I missing something? Edit: Nevermind! I think I figured it out.
  11. Will do! Just to be sure, should I be running Dyndolod after making the foregoing changes before testing? So far I haven't been.
  12. Sorry I misunderstood. The mesh is in Glorious Glaciers (Glorious Glaciers at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com)). I disabled that mod but CTD'd at the same place. The log is attached. I saved the vanilla mesh from Skyrim - Meshes1.bsa and put it in and confirmed in the MO2 data tab that it was in the correct path in overwrite. CTD in the same place. Second second log. Crash_2022_6_27_19-20-36.txt Crash_2022_6_27_19-49-33.txt
  13. Here're the results from xEdit Asset Browser - it seems to indicate that the mod with the problem nif is the USSEP?!? I have the most recent 1.5.97 version if that. One other thing - somehow right before I started on this modlist, the game auto updated to 1.6xxx. I used this (Unofficial Skyrim Downloader at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com)) to roll back to 1.5.97 and then started my current playthrough. I'm wondering if there's a problem with that patch that's causing all these problems, which I didn't have before. Any thoughts? I so appreciate the time you're taking with me. I'm going to be away from my computer for a bit but I'll start on the troubleshooting you recommended when I get back in about an hour.
  14. Here are two crash logs from this morning. Relevant objects look the same, probable call stack a bit different. Crash_2022_6_27_6-8-54.txt Crash_2022_6_27_6-17-30.txt
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.