sheson

As explained and discussed in this thread several times already, the combined terrain LOD textures look exactly as the full textures in the loaded cells - as long as the "improved" snow shader is disabled. Grass is not textures but 3D models. For now you have to manually change landscape texture to simulate grass as Terrain LOD Redone and Cathedral Landscapes do. Some kind of grass baking is tested, but I did not have much time for it so far.

I can not really see anything in the tiny screenshots or spot any difference in anything. You did not mention what tree mod you are using.

The message can only appear if a plugin file name matches part of the text that is listed for WarnModFileName= in the INI that is used. Nothing else you do or wrote matters in regards to that message. It is as simply and straight forward as that. You are probably editing the wrong INI (check the DynDOLOD log which INI file is loaded), the changes do not save or you are not doing the editing correctly.

Yes, one of the many things DynDOLOD does is that it updates and adds thousands of new object LOD models that didn't have LOD before so objects do not pop-in out of thin air.

What you are doing wrong is that you are not asking a question that can be answered because you are not describing the supposed problem. DynDOLOD drastically improves tree and object LOD. It does not change how the engine works.

If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum http://forum.step-project.com/forum/101-shesons-dyndolod-support/ Post the bugreport as suggest by the message. Assertion failures from xEdit are typically caused by broken plugins. Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help. Please read and follow the installation instructions From the DynDOLOD Standalone archive copy the content of the 'DynDOLOD' folder, which contains the files DynDOLOD.exe, TexGen.exe, DynDOLOD_QuickStart.html and the sub folders 'Docs' and 'Edit Scripts' with all their content into a new 'DynDOLOD' folder outside of special OS folders like 'Programs Files' or 'Program Files (x86)', the SteamApps or game folders and Mod Organizers virtual file structure. Do not mix with old versions or xEdit/xLODGen installation.

I suggest to look at the log file for error messages and search for it. Executing TexConv returned error C0000135 https://forum.step-project.com/topic/14518-executing-texconv-returned-error-c0000135-vruntime140dll-or-vcruntime140-1dll-was-not-found/

Have a look at DynDOLOD\Docs\DynDOLOD_Mod_Authors.html

Great that you figured out how to resolve it. DynDOLOD is just a modified xEdit but it uses its own settings files. But the same command line arguments to set the language / codepage can be used. https://tes5edit.github.io/docs/2-overview.html#CommandLineSwitches Though none of that should be necessary if everything is in English anyways. So not sure what happened. Enjoy.

I have not much experience with the language files, especially when the game is not in English. That is outside of DynDOLOD and my expertise. The default language files are typically in Skryim Interface.bsa and updated via Skyrim Patch.bsa. Make sure the game is up-to-date. xEdit start up log should list something about the language files. Background Loader: [skyrim_English.DLSTRINGS] Using encoding (from language): 1252 (ANSI - Latin I)Background Loader: [skyrim_English.ILSTRINGS] Using encoding (from language): 1252 (ANSI - Latin I)Background Loader: [skyrim_English.STRINGS] Using encoding (from language): 1252 (ANSI - Latin I)...Background Loader: [update_English.DLSTRINGS] Using encoding (from language): 1252 (ANSI - Latin I)Background Loader: [update_English.ILSTRINGS] Using encoding (from language): 1252 (ANSI - Latin I)Background Loader: [update_English.STRINGS] Using encoding (from language): 1252 (ANSI - Latin I)...Background Loader: [Dawnguard_English.DLSTRINGS] Using encoding (from language): 1252 (ANSI - Latin I)Background Loader: [Dawnguard_English.ILSTRINGS] Using encoding (from language): 1252 (ANSI - Latin I)Background Loader: [Dawnguard_English.STRINGS] Using encoding (from language): 1252 (ANSI - Latin I)...Background Loader: [HearthFires_English.DLSTRINGS] Using encoding (from language): 1252 (ANSI - Latin I)Background Loader: [HearthFires_English.ILSTRINGS] Using encoding (from language): 1252 (ANSI - Latin I)Background Loader: [HearthFires_English.STRINGS] Using encoding (from language): 1252 (ANSI - Latin I)...Background Loader: [Dragonborn_English.DLSTRINGS] Using encoding (from language): 1252 (ANSI - Latin I)Background Loader: [Dragonborn_English.ILSTRINGS] Using encoding (from language): 1252 (ANSI - Latin I)Background Loader: [Dragonborn_English.STRINGS] Using encoding (from language): 1252 (ANSI - Latin I)

Not sure why you can't do the basic troubleshooting by eliminating half of the meshes each step yourself? I can load into Tamriel just fine with the meshes and textures you sent me. That is most likely because not all the textures used by the LOD meshes aere part of the archive you uploaded. It seems that object LOD atlas generation was not checked, so the object LOD meshes use a lot of texture directly. One or more of those textures might be corrupt, may have an unsupported compression format or may have a resolution that is not of 32, 64, 128, 256, 512 etc. Generate xLODGen to generate an object LOD texture atlas. Make sure there are no error messages in the log.

There are probably still corrupt meshes or textures in the load order. In addition to what I already suggested how to find the problematic LOD mesh, maybe install .Net Script Framework first. Its crash log might actually mention the corrupt file directly.

Are you using an older MO2 version and/or forgot to set a dedicated output folder with -o as recommended on the first post? The lodsetting or single object LOD source textures being corrupted happened quite a bit earlier last year. But with the regular MO updates all reports died down. In any case, create or install a valid lodsettings files again. Update to latest MO2 and latest xLODGen. Remove all generated LOD files from meshes/terrain and textures/terrain. Generate LOD with -o into a dedicated folder. If it complains about not being able to read textures, install those again as well until there are no errors. Then install the output as a mod in MO. If there are still problems in the game then first temporary remove tree LOD in meshes\terrain\[worldspace name]\trees, then meshes\terrain\[worldspace name]\objects, then the terrain LOD *.BTR in meshes\terrain\[worldspace name]. Once yo know which LOD type causes the problem, do the usual temporary remove half testing until you are down to only one or a handful files causing the problem. Check them in NifSkope for errors or upload them for me to test.

That screenshot shows that there is an issue with the strings file for the text/translation of the records and that the problem already happens for Skyrim.esm. Fix all errors in the load order first before generating LOD / using DynDOLOD.

DynDOLOD is patcher that sometimes copies the winning overwrites from other plugins and changes them in order for LOD to work correctly. If that winning overwrite changed something else that change will be in the DynDOLOD plugin, regardless if the load order changes afterwards. If the current load order does not show this change, generate anew for the current load order, so all the copied records reflect the current load order. Or simply look up the base record in xEdit and forward the desired FULL - Name into the highest plugin.

If you are not new to modding you already know and checked that DynDOLOD is not doing it, but merely copied any such FULL - Name change from whatever plugin was the last one to overwrite the base record at generation time.

You are welcome. Enjoy.

The bugreport shows it allocated 1,41 GB at the time of that exception... Huh Have you disabled the Windows page file by any chance?

OPs, use this one https://mega.nz/#!kV5gUYpB!7Ua8gQ1gtToK8kPpLKRmcDWLq02tpPV73k6UKVLzszI

No errors in those logs that relate to the issue. Please run with this version of DynDOLODx64.exe, still with Debug=1 and FasterCreate=0 It should show us which cell it is working when the error occurs, which might help us to pin it down. Look up which plugin is the last to overwrite the mentioned cell before the error and let me know. Also which plugin is the last to overwrite the persistent cell 00000D74?

I don't have high hopes for that. NavMesh and Tint errors are typically irrelevant in this circumstance. Also do a run with Debug=1 and post that log, please. Try the x86 version. It might probably not get past creating the atlas texture due to memory constraints, but if it does I wonder if it triggers the same error.

Post the bugreport.txt as well. Such Assertion failures reported by xEdit are typically caused by broken plugin. Maybe checking the non-vanilla plugins for errors with xEdit might help finding the culprit and fixing it.

Test what happens after setting FasterCreate=0 in .. DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini

Please read the entire messages and follow their suggestions. For example, the message to search for the error message on this forum also suggests to check the DynDOLOD FAQ first or what logs to include in a post on this forum in case the FAQ/search came up empty. Having an outdated PapyrusUtil.DLL installed does not affect LOD generation. It will of course cause things to not work correctly in the game.

The error is Error preparing texture textures\lod\ictowerlod01.dds for atlas: File not found: textures\lod\ictowerlod01.dds Searching for it finds these related thread: https://forum.step-project.com/topic/14490-file-not-found-textureslodictowerlod01dds/https://forum.step-project.com/topic/14071-can-not-find-textureslodicwalllod02dds-textureslodictowerlod01dds/https://forum.step-project.com/topic/14273-cant-generate-3d-lod/?p=237482https://forum.step-project.com/topic/13894-dyndolod-beta-for-skyrim-special-edition-and-skyrim-vr-281/page-101?do=findComment&comment=235883https://forum.step-project.com/topic/13983-can-not-find-textures/https://forum.step-project.com/topic/12576-newest-texgen-wont-complete-due-to-missing-textures/?p=207932 Looks like DynDOLOD Resources Core Files are not installed completely, maybe due to an incomplete download.