sheson

The program can not read textures\defaultdiffuse.dds from Skyrim - Textures.bsa The BSA seems to be loaded just fine (else it would be a file not found error). So the reading error probably happens because the BSA file may be corrupt or some anti virus preventing access.

I suggest to read the description and installation instructions in the quickstart or manual. The only time the instructions mention a manager (Mod Organizer) is to make sure its users do not install to a wrong folder.

Read the DynDOLOD FAQ: Skyrim: ILS or CTD

The optional esp files are not the DynDOLOD Resource - Core Files. The core flies are the preselected first fomod installer option that installs meshes, textures and script folders from 00 DynDOLOD Core Files - Required. The core files option can't be unselected in the fomod installer. If the fomod installer is not working then there may be a problem with the NMM installation. It may have to do with the windows version or other crapware including anti virus.

Seems like the mod manager something has a problem if it fails installing meshes and textures to the game folder from an archive. I just tested DynDOLOD Resources 2.20 with 0.63.9. There is no problem installing the Core Files. After clicking install the DynDOLOD Resources options form shows up and the Core Files install correctly into the game folder. Once it completed installing all files, DynDOLOD.exe file checks pass without a problem.

This is not a descriptive error report. If installing meshes/textures from an installation archive with an installer is a problem, I suggest to spend some time to learn how to use a mod manager. Then verify the log ..\DynDOLOD\Logs\DynDOLOD_log.txt lists the correct game paths when it starts. If that is not the case, start the games launcher once, which usually sets the correct path in the windows registry. The game or DynDOLOD should not be installed in a location that contains a special path like "Program Files" on newer windows versions.

Mods which are not listed in the Compatibility section of the manual are not specifically supported. DynDOLOD includes no billboards (or almost none) as it just uses the TES5LODGen tree LOD generation. Any sets of billboards for mods I created are uploaded to the TES5LODGen page on nexus as well. So just follow the installation instructions:

Go inside a building. Save. Start game without esp. Load last save game. Wait. Save. Start game with new esp. Should work. If not clean the save made after removing esp. Read the section "Update Texture Atlas" in the TexGen manual how to update LOD texture atlas for the existing LOD without redoing the whole esp.

If it can not find some key files installed in the game games data folder it will print the message that it can not find some files. Install the DynDOLOD Resource files into the game data folder or however the mod manager you are using is dong that. If you have problems installing the meshes/textures from DynDOLOD Resources I suggest to follow a modding guide.

If DynDOLOD.exe hangs with 0% CPU for a long time, set FasterBase=0 or FasterCreate=0 in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_TES5.ini depending on which part in the process it happens. Regardless of CPU, multitasking (the execution of several programs at the same time) should always work in windows even if slow or not many cores exist. Otherwise try to generate all LOD for a worldspace at a time. But yes, it also works to generate static LOD in first pass, and dynamic LOD in a second pass for the same worldspace.

The log is written to DynDOLOD\Logs\DynDOLOD_log.txt in the latest version. That changed in a recent version. Only the last overwrite (most right plugin) for a tree matters. So if SFO overwrites a vanilla tree record only its data matters. Most likely SFO overwrites the vanilla nif file as well in addition to updating its data. The last overwrite of a billboard dds file for a tree is the texture that is used for the tree LOD texture atlas that is created to the output folder Textures\Terrain\Tamriel\Trees\TamrielTreeLod.dds. So, if the correct billboard is in that atlas the only way tree LOD can not match is, if the created tree LOD / atlas is overwritten by a mod. No. z-fighting is 2 different models occupying the same space. Their number of triangles does not change that.

See if this post helps you

It comes as no surprise that if you remove incompletely created LOD, that the incompletely created LOD will not show in the game. So I can deduct you tried to generate 3D static tree LOD. Why keep me guessing? Use modwat.ch (which works fine right now) or provide the mod list, plugin list, ini settings. Upload as text to pastebin or a file service. No screenshots. Upload DynDOLOD\Logs\DynDOLOD_log.txt from the generation shows in the screenshots to pastebin or a file service. In any case. I looks like you are using third party tree mods and either instructed the patcher to use their full models for 3D static LOD trees and/or a third party mod that supplies 3D static LOD trees. Make sure all their textures are installed correctly and available at generation time and also later in the game.

The meshes reference a texture that is not there or not loaded. I suggest to check for that in order to fix the problem. See the FAQ. Those messages are normal for shrubs and bushes. However, when generating 3D ultra tree LOD, none of the 2D flat tree LOD messages should be in the log as that generation is turned off. There is texture atlas generation message after a worldspace was scanned. Maybe you didn't try generating 3D ultra tree LOD and the purple trees form the screenshot are actually from full models in loaded cells with a higher uGrids? Then this has nothing to do with LOD generated by DynDOLOD and you need to fix your tree mod installation. Use modwatch.ch and upload DynDOLOD\Logs\DynDOLOD_log.txt if you tried to generate 3D ultra tree LOD.

It looks like you have generated 3D tree LOD. This is not "install it exacly as GamerPoets' video said"... is it. Purple textures usually mean missing or corrupt textures dds files. Make sure to install all files created in the output folder, or check for log message that an atlas texture could not be created or texture files were missing. "skyrim has failed to allocate memory..." is a message from crash fixes OSAllocator Check over there for solutions or try with default heap memory as a test. 3D static tree LOD has increased memory requirements depending a lot on the tree mods and settings as explained in the ultra trees manual. Use BethINIs, use default medium settings or even low for LOD distance as a test.

DynDOLOD needs *some* memory, but with its typical default setting, especially on low it is nothing dramatic. It could be that you have a mod installed that overwrites something or otherwise something gets picked up for LOD that maybe causing this. Test with Legendary plus essential mods which require LOD only. No need to have other mods in the load order while generating LOD. Use BethINI, use default medium settings or even low for Distant Object Detail as a test. I suggest to try the default memory allocation as a test and check default heap memory usage with Memory Blocks Log. I suggest to set up proper stable game by following a guide. If not caused by mods, something doesn't seem to be configured right.

Define "having enough memory" when usage is reportedly 3550/4150MB RAM for a 32 bit windows application that can only use about 3.1GB user space (the rest of the 4GB RAM limit is needed/reserved for windows/drivers and other dlls). Also, memory can become fragmented which means there can be enough free memory reported, but it is split into small chunks so that the next allocation can not reserve the continuous amount it needs. Since you are using crash fixes OSAllocators you should check over there what to do when it can not allocate more memory and about its CustomMemoryBlock settings. You could test using vanilla heap memory allocation instead. Optimize ENBoost settings following a guide. Generate LOD which uses less memory. Read the Performance section of the manual.

Check the FAQ: Skyrim: ILS or CTD entry.

It is good news you can push further, because it means that we are generally on the right track. If all (linked) persistent cells combined are less than 65535, I wonder if there could be temporary cells that exceed that same limit, or if the combined loaded ugrid of cells 5x5 = 25, or the ugrid + the persistent cells together are a limit. Who knows, may interior cells linked to Tamriel matter too. Records in currently not loaded cells should not matte, but who knows, maybe there is a total limit for a worldspace of specific "things" combined. If you can't load/CTD with too many mods, try cow tamriel 0 -64 from main menu and see if that loads.

You either didn't generate static and tree LOD, or generation failed (there should have been error messages) or not all the generated files from the output folder are installed or they are overwritten by another mod. For example, check Meshes\Terrain\Tamriel\Objects\*.bto and Meshes\Terrain\Tamriel\Trees\*.* are from the output folder and are the last overwrite.

That is great news. Thanks for helping narrowing it down and to help fixing the problem.

This is related to specular objects settings. Please download this beta version of LODGen.exe and generate static object LOD for Tamriel again. To only update the BTO files, you can just "Execute LODGen.exe" in expert mode for the Tamriel worldspace. It will use the last export file so there is no need to rescan or update the esp etc. Enable expert mode in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_TES5.ini by setting Expert=1 Let me know if that fixes the problem.

Thanks, I will see if I can replicate with all the info. Can take a bit. I figured after generating myself for a million times I should probably turn on some kind of turbo boost so I get stuff done quicker.

Yes. Especially if you used MO to start DynDOLOD.exe you should keep it open until all LODGen.exe finish.

I foresee a stable platform independent CK as a service in a browser.