The problem in the DynDOLOD .esp file. When i deleted or disabled it - game worked stable. esp file important for work? What are its functions?
The esp is required so LOD works correctly, adds copies of object from child city worlds that now have LOD to the parent world and adds a couple neverfades. This is all explained in the included documentation.
How do delocalized output .esp file?[/font]
It is in the right click window Other / Localization of xEdit. I doubt it will change anything.
P.S. I'm using this bat file for run DynDOLODx64.exe:
@DynDOLODx64.exe -sse -cp:utf-8 -l:russian
Yes, that should create a correctly localized plugin.
The folder where i launching DynDOLOD - its full unpacked copy (with game archives) of my Steam Skyrim SE folder. I don't use Steam folder for my mods pack - its a backup. Also and for "classic" Skyrim version.
G:\The Elder Scrolls V SE unpacked\ is not a valid installation path for the game. xEdit/DynDOLOD
do not support invalid paths/setups.
The problem is probably a corrupt nif (which most likely is from one of the other mods) which is used for neverfade LOD.
The next troubleshooting step would be to methodically remove parts of data from the esp with xEdit, while at the same time keep a copy of a version with that data which still causes problems.
It goes like this: remove half the data. If it works then go back to the earlier copy and remove the other half. The resulting esp should still cause problems. You continue this until you have narrowed down to the data causing the problem, always keeping a copy of the previous step.
In this case we only need to looks at worldspace data. So, remove all worldspaces from the esp, to see if it works.
If that is the case, use backup file and remove one worldspace at the time to narrow it down to a single worldspace.
Once you know which worldspace it is, remove groups, then sub-groups until you have a single sub-group.
Then remove batches of cells until you narrowed down to single cell.
Then remove single references until you narrowed it down to a single reference.
Then check the base record for the nif it uses. Replace that nif with its vanilla version / fix the nif. Or remove the base record and references using it in case the nif can not be fixed.
If removing worldspaces does not work, then you are out of luck with that current setup.