DynDOLOD and TexGen finish without issue but having Dyndolod.esp in My Load Order Causes Game to Crash at Menu

[NordPride_WorldWide]

So I can run texgen and dyndolod without encountering a single error, and my logs look clean(to me), but when I check both texgen and dyndolod and load dyndolod.esp at the very end of my load order the game will crash before I'm able to see the "continue/new game/load" screen. wihtout it enabled My game loads and plays without incidence.

 

Crash fixes reports the same error each time: "Game has crashed with exception address 0xF52344!"

 

My modwatch: https://modwat.ch/u/SuperVillain0utcast/plugins

 

My logs: https://www.dropbox.com/sh/b9xamehld3zzckj/AADJpYEIouUQboQI1lMl6jUka?dl=0

 

Thank you in advance

 

 

[sheson]

FAQ: Game: ILS or CTD

 

A: More LOD uses more memory and this can cause infinite loading screen (ILS) or crash to desktop (CTD) if the game is not setup correctly. This should generally not be a problem with Skyrim Special Edition or Skyrim VR, but for Skyrim double check heap memory usage (block 1) with Memory Blocks Log from https://www.nexusmods.com/skyrim/mods/50471/ and adjust SKSE or SSME memory settings. Or use the alternative OSAllocator from crash fixes with pre-loader. Remove satefy-load if it is used. Setup ENBoost correctly. Set ExpandSystemMemoryX64=false in enblocal.ini. 

 

A: Do not use the experimental TreeFullFallBack setting without understanding what it does and what it is for. 

 

A: If heap memory is not the cause of CTD see ..DynDOLOD\Docs\DynDOLOD-README.txt for checking if a missing or invalid nif model used for dynamic LOD is the cause. 

 

 

Since you mention Crash Fixed, I suppose we can assume you are using UseOSAllocators=1 and also have set up the CustomMemoryBlock of Crash fixes. ENBoost all set as well.

 

I see you already have Wyrmstooth flagged as ESM, but count the persistent references anyways https://www.reddit.com/r/skyrimmods/comments/ag4wm7/psa_the_reference_handle_cap_or_diagnosing_one_of/

 

 

Hide meshes/textures from output (should not change anything). If it does it may simply run out of memory.

 

Enable standard Papyrus log, and check it for unusual errors at startup.

 

Test with vanilla INIs.

 

If nothing helps, I would start removing worldspaces from the plugin and see if that changes things eventually. Then the  "usual" binary search. I can explain more if needed.

Edited May 4, 2019 by sheson

[NordPride_WorldWide]

So it seems to be my .ini's, when I revert them to default my game starts, but if i use BETHini to change it I crash. What about my ini is causing issues all of a sudden? I've run DDL before with my regular settings without incidence.

[sheson]

http://www.technicaloverload.com/compare-two-files-using-notepad/

[NordPride_WorldWide]

So I found the issue.

 

It was the line "bBackgroundLoadVMData=1" in skyrim.ini that made it crash at the main menu, removing it allows me to load my game.

 

Thank you for your infinite patience.

[sheson]

It's great you found the that out. This is really good to know.

Edited May 14, 2019 by sheson