sheson

That seems to verify the textures exist and can be read and the error message from the OS is about not letting the program write to the destination path as in the previous cases.

MO2 seems to blacklist a couple programs including Firefox or Chrome from the virtual file system. Why that is necessary you would need to ask the developers. You might want to enable "debug" mode for the log in the diagnostic settings of MO2 so it shows every file access, including the textures. If you have inexplicably file access problems, also consider rebooting and/or booting into safe mode.

Since I do not really use Windows or Windows Defender I can not help well with exact instructions how to check its real time log. So I am just going by google results for example like https://superuser.com/questions/1126881/how-to-find-specifics-of-what-defender-detected-in-real-time-protection "In the console tree, expand Applications and Services Logs, then Microsoft, then Windows, then Windows Defender." As comparison try this: Open the load order in xEdit. Start the Asset Browser script with CTRL+F3. Type in the file of the texture to copy, e.g. snow01_n.dds or stockadewood01_n.dds, then right-click it in the results and select save as from the first "container" (data or a BSA file) listed.

By default the max distance for animated LOD waterfalls is defined by the Far Grids setting. See https://dyndolod.info/Help/Dynamic-LOD

Temporarily disabling plugins is not fixing the error in the load order. If you want to use paid mods from the Anniversary Edition, all other game data files (plugins and assets in the data folder) need to be from/for the Anniversary Edition as well. Use the "best of both worlds" option.

https://dyndolod.info/Messages/Can-Not-Copy-Resource TexGen, like any other Windows program, uses standard OS functions to read and write files. If the OS function returns an error, it is printed to the user and process is stopped. The error message from the OS is "The system cannot find the path specified". The anti virus scans every file being read/written. If it doesn't like a file while it is being read/written it blocks access. Check the windows event log for messages from defender. The game and tools read plugins and assets from data folder. The used mod manager does not change that. In case of MO2 it hooks the standard OS function to read write files for the virtual file system. Check the MO2 log. It lists every virtual file access mapped to the physical file location. The error happens right at the start of the stitched object LOD textures generation. Do not install DynDOLOD into mod manager folders. Do not output into mod manager folders.

Use the "copy message to clipboard" link and paste the text instead of posting a screenshot as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text As explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages, use the "Click on this link for additional explanation and help for this message" to open https://dyndolod.info/Messages/Unresolved-Form-ID "In case the message mentions that a plugin might be the wrong version, double check it is the correct version for the game version and for any other plugins using it as a master. For example, do not use plugins or paid mods from the Creation Club Anniversary Edition with outdated vanilla game plugins from before the Anniversary update. Update the required plugins and use matching versions. For example, do not forget to update the cleaned version of Update.esm after game updates."

Thanks for detailed report with logs. Bug is fixed is Alpha-77. DynDOLOD does not do any terrain or water LOD. Use xLODGen to generate higher resolution terrain LOD meshes and with better defined coast lines for the higher LOD levels with the "optimize unseen" option.

New version is uploaded. You can just execute LODGen in the expert mode for the worldspaces again to update the object LOD. See https://dyndolod.info/Help/Expert-Mode

The LOD should be fine if log ends with Code: 0 It just means some minor optimization fails. Is it always the same tree / text? Will be fixed next version.

The archives on Nexus and mega are updated and now include TexGenx64.exe again.

Copy DynDOLODx64.exe to TexGenx64.exe. Will upload fixed archive ASAP. My x86 version just ran through without error in x64 OS with a 6GB VRAM card.

Why not use the x64 version? You on a x86 OS? Check the first post which log files to upload when making posts.

The game engine requires textures to be a power of 2. DynDOLOD does not change how the game engine works. If you knowingly use mods that contain invalid textures that cause CTD then that is your choice. It is not a problem of DynDOLOD. It is not an incompatibility with DynDOLOD. It is an incompatibility with the game engine. DynDOLOD is just reporting the errors. Proper modding practice would be to fix the invalid textures to have power of 2 resolutions or remove them. They are most likely not from Bruma or JK. Missing textures and invalid texture resolutions are a different problems. In case of Bruma we know the missing assets are part of the problem to not being able to properly generate LOD for the new worldspace, thus it is ignored for LOD generation by default. I could reproduce the problem with the purple model. It is a LOD model. There is a filename collision with another mod so a wrong LOD model is used . This will be fixed in the next alpha version. Errors that exist in the load order cause problems or CTD in the game regardless of using DynDOLOD or not. The documentation explains their severeness and if they need fixing and how.

Really check the log messages and read their explanations. https://dyndolod.info/Messages These are not DynDOLOD errors or or problems. These are errors and problems with the installed mods. Regarding the CTD. As I already mentioned, texture resolutions not being a power of 2 are the prime suspect. The log shows several textures that do not have a power of 2 resolution. Fix the invalid textures or permanently remove the mods supplying them to avoid CTD. https://dyndolod.info/Messages/Texture-Resolution Also clean every plugin that has deleted references to avoid them causing CTD. https://dyndolod.info/Messages/Deleted-Reference Curiously you did not say which specific mod from Elianora you actually suspect so I can not check myself. Purple textures means the diffuse texture is not found. A "File not found textures\..." message probably helps you find the culprit. Diffuse textures means you can "ignore" missing textures that end in _n.dds. If those are missing the lighting will "just" be flat. https://dyndolod.info/Messages/File-Not-Found-Textures If something is object/tree LOD it disappears when toggling LOD of in console with tll. If something is dynamic LOD it can be clicked has a form id in a DynDOLOD plugin when console is open. LOD is only generated for references that do exist in the load order at LOD generation time. If the LOD goes away when getting close, it typically means the load order changed after generating LOD. It might be possible that the model used for LOD is not visually matching the reference it is placed for, but if it is LOD, then there should be a full model something in its place that you can click with console open to get a form id.

Read the first post which log and debug log to upload when making posts. There is no LOD in interior cells. Hence DynDOLOD is/can only be active in exterior worldspaces for which dynamic LOD has been generated. CTD is often caused by assets from other mods, especially textures. The log might have warning and error messages about textures not being power of 2 or divisible by 4. They should also be listed in the summary. https://dyndolod.info/Messages See ..\DynDOLOD\docs\DynDOLOD-README.txt for troubleshooting tips. The best option to troubleshoot CTD is .Net Framework crash log. Post it in case help is required.

"Click on this link for additional explanations and help for this message" on the pop-up message to open https://dyndolod.info/Messages/Can-Not-Copy-Resource which has explanations and suggestions for the message and especially "The system cannot find the path specified" As you can see the problem is the OS, antivir or some other crapware preventing read/write access. Yes, the copy operation from the one texture path and filename to the other texture path and filename is entirely on purpose.

I moved the post to the DynDOLOD 3 Alpha thread since this is where all posts should be made. Read the first post which log and debug log to upload when making posts. Check with xEdit which plugin is the last to overwrite 0000BCD0. It probably has some kind of error.

The background loader is still xEdit code. That means you will see the same messages loading things with xEdit. Skyrim - Patch.bsa is a vanilla game file https://stepmodifications.org/wiki/SkyrimSE:Game_Files It is listed in Slyrim.INI [Archive] section, that is why xEdit/xLODGen/DynDOLOD wants to load it. I believe the file got removed with the the 1.6.x anniversary update, but the entry in the INI still lists it. The message about it missing can be ignored. If it bothers you, remove the entry from the Skyrim.INI The duplicated top level group is a known error in Skyrim.esm. You do not need to do anything about it.

Just do not check object LOD on the advanced mode settings. Only check tree or dynamic LOD.

The DynDOLOD shows as well that seasonal LOD has only been generated for Tamriel and not for example for especially not DLC2SolstheimWorld. It seems it switches the object LOD to *.WIN.* files but since they do not exist, the game has nothing to show. Since *WIN* terrain LOD was generated for DLC2SolstheimWorld, it shows the winter terrain just fine. If you generate LOD for seasons with DynDOLOD, make sure all the desired worldspaces have the [Seasons] identifier in the worldspace list of the advanced options as explained at https://dyndolod.info/Help/Seasons. Double click the worldspace to toggle the [Seasons] identifier. If you find Season of Skyrim switches to empty terrain LOD for SPR, SUM, AUT, then you will need to generate those as well. If you are sure they do not change from the default season, you could make copies from the default LOD files to the seasonal LOD files.

Clean the plugins that contain deleted references https://dyndolod.info/Messages/Deleted-Reference You have not uploaded the DynDOLOD log and debug log. The xLODgen log for terrain LOD show that only the default and WIN season are generated, while the LODGen logs for object LOD for Tamriel shows that all 4 seasons have been generated. This should probably match. I can see that seasonal object LOD has only been generated for Tamriel but not the other worldspaces, especially not DLC2SolstheimWorld. If you want to generate LOD for seasons with DynDOLOD, make sure the worldspaces have the [Seasons] identifier in the worldspace list of the advanced options as explained at https://dyndolod.info/Help/Seasons. Double click the worldspace to toggle the [Seasons] identifier. You can remove LOD Unloading Bug Fix, it is not needed with DynDLOD when using dynamic LOD.

"Click on this link for additional explanations and help for this message" on the pop-up message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum to open https://dyndolod.info/Messages/Can-Not-Copy-Resource which has and explanation and suggestion for the message and especially "The system cannot find the path specified" Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire logs to upload when making posts. The question indicates that the requirements to use any version DynDOLOD are not met. Considering the problem is caused by the OS, anitvir or other 3rd party preventing file access it does not really matter which version is used.

Assuming you are using DynDOLOD 2.x There is really no point trying to mix standard tree LOD with trees done in object LOD = ultra tree LOD. Trees done in object LOD can either have 3D tree LOD model or billboards. The higher object LOD levels typically use billboards anyways. Simply generate ultra tree LOD and set the mesh mask rules as desired as explained in the manual ..\DynDOLOD\Docs\trees.ultra\DynDOLOD-Trees.html It has examples how to specifically set Billboard for a tree in LOD Level 4 in case it has a 3D LOD model but you want it to use a billboard instead. The same principles apply to DynDOLOD 3 Alpha of course. https://dyndolod.info/Help/Ultra-Tree-LOD

That's what I mean, too. If it isn't listed at all in the log its not even discovered. It seems it is not seeing the overwrite with the flag. See if it works next alpha version.