sheson

You should investigate the problem with SSE Engine fixes. It could be wrong version, a problem with its requirements or maybe its INI settings need adjusting.

Moved to the appropriate thread for the message. See posts above. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search https://dyndolod.info/Official-DynDOLOD-Support-Forum#Check-the-FAQ, https://dyndolod.info/FAQ#DynDOLOD-requires-SKSE Make sure you have the correct SKSE version for the current Skyrim version that is used and none of its file are overwritten by other mods. The papyrus log indicates that several years old outdated SKSE scripts for 1.5.97 are installed instead of the current ones for 1.6.1170. Install SKSE64 for 1.6.1170 and its papyrus scripts properly.

Also upload E:\Skyrim\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt Any custom mesh mask rule targeting TREE base records needs to be before the "tree" rule which has the TREE flag set. Make sure the mesh mask matches the desired full models and base records by clicking the "Check" button in the edit rules window. See https://dyndolod.info/Help/Mesh-Mask-Reference-Rules#Check. Upload new DynDOLOD log, debug log and DynDOLOD_SSE_Object_Report.txt with the correct order of the custom rules if problem persists.

Use the last test version from this post https://mega.nz/file/0MYzjBYA#J_0-482cmXSeHh8a5dnlEdLFsU3xxEZKc3ov-WuSD2A If there is a problem with that test version, then report it properly. Other test versions are not functional.

I suggest to actually read the description of Seasons of Skyrim SKSE. You uploaded a TES5LODGen_log.txt, which means xLODGen was run in TES5 mode for Skyrim LE, while being forced to use Skyrim Special Edition game, plugins.txt and INI folders and files.. Instead of doing something nonsensical, run xLODGen in SSE mode for Skyrim Special Edition. Read the first post of https://stepmodifications.org/forum/topic/13451-xlodgen-terrain-lod-beta-132-for-fnv-fo3-fo4-fo4vr-tes5-sse-tes5vr-enderal-enderalse, the Readme.txt included in the xLODGen terrain LOD beta download archive and https://dyndolod.info/Help/xLODGen. I suggest to learn basic modding practice etc. by following a proper and recent modding guide from the ground up. Several year old posts on social media might not be a good resource. While the broad strokes might still generally apply, details, mods and the tools have changed.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload. Make useful screenshots of a original full model and its copy with more informative console as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots or report their reference form IDs. Upload the custom patch plugin or a minimal test version of it for the screenshotted original reference that can be used to replicate the issue.

Upload the SSELODGen_log.txt when posting about about terrain LOD generation. From Seasons-Readme.txt included in the xLODGen terrain LOD beta download archive: The feature requires season swap files in Data\Seasons\*[SPR|SUM|AUT|WIN].ini. A season in the drop down becomes available only if swaps for it have been found and loaded successfully. That means when xLODGen was run, there either were no seasonal files for any of the other seasons in the ..\Data\Seasons\ folder, or none of their from/to swap definitions were valid records in the loaded plugins at the time. If the swap data for a season does not swap any landscape textures, then not generating terrain LOD for that season and disabling the terrain LOD switching in the INI as you did is a good option anyways.

Moved to the appropriate thread for "unresolved form ID". Check posts above. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log and debug log to upload when making posts. Use the Copy message to clipboard link in the message to copy and paste the entire contents of an error message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text Click the link Click on this link for additional explanations and help for this message of the message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open https://dyndolod.info/Messages/Unresolved-Form-ID, which explains: If unresolved form ID errors happen in the latest and all updated vanilla game files (including DLC and CC), consider using the Unofficial Skyrim Legendary Edition Patch, Unofficial Skyrim Special Edition Patch and/or Unofficial Skyrim Creation Club Content Patches.

Moved to the appropriate thread for the message. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search. See posts above. meshes\dyndolod\lod\effects\fxcreekflatlarge_63cd3084_dyndolod_lod.nif can not be found in the reported data folder E:\Steam\steamapps\common\Skyrim Special Edition\Data\ Click the link Click on this link for additional explanations and help for this message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open https://dyndolod.info/Help/DynDOLOD-Resources and scroll down to the Troubleshooting section: If the version information or a required resource file can not be found, it means that the file with the version information or the resource file which are installed with the DynDOLOD Resources can not be found in the data folder (the standard OS functions which are used to check if a file exists returns a file not found error). Read the entire Troubleshooting section and make sure DynDOLOD Resources SE 3 Core File are installed in the virtual games data folder. MO2, right window Data tab. The mentioned file is part of DynDOLOD Resource SE 3 since a year and still part of the latest Alpha-55 from February.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. Also read https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots Do rudimentary troubleshooting as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting. If the object in question remains when using tll in console it is typically the full model. Objects or roofs being fully transparent and showing the blue sky instead are typically related to parallax or other shader issues. If the problem goes away when disabling DynDOLOD output, it typically means the LOD patch is outdated and needs to be generated from scratch for the new load order.

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Check-the-FAQ https://dyndolod.info/FAQ#Entire-LOD-missing If Seasons of Skyrim SKSE is used, make sure to generate LOD - including terrain LOD with xLODGen - for all enabled seasons or disable LOD switching for a season in ..\Seasons of Skyrim\SKSE\Plugins\po3_SeasonsOfSkyrim.ini. Also see https://dyndolod.info/Generation-Instructions#Prerequisites, https://dyndolod.info/Help/Seasons and https://dyndolod.info/Help/xLODGen#Seasons

Always use the latest version as explained in the first post, https://dyndolod.info and https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-the-Latest-Versions See https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make useful screenshots of a full model with more informative console so we know the full model and base record form ID. https://dyndolod.info/Help/Mesh-Mask-Reference-Rules#Notes The order of rules matters. Rules at the top match before rules at bottom Also note the 'Order Matters!!!" above the rules list in the advanced mode. The "frozenmarshicefloe" rule should be inserted above the "icefloes" rule so it can take precedence. Best to insert it near the top with the other similar rules for "sky\", "magic\" etc. You can look up which base record has which rule assigned in ..\DynDOLOD_SSE_Object_Report.txt

The DynDOLOD log and debug log show the tool being started and then closed without generating a LOD patch. Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs Always use the latest version as explained in the first post, https://dyndolod.info and https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-the-Latest-Versions What rudimentary troubleshooting have you done to verify this is related to DynDOLOD output or LOD in general? See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting See https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make useful screenshots of a full model with more informative console and the LOD area using tfc command to get closer to LOD. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search See answer and reply for this post https://stepmodifications.org/forum/topic/13451-xlodgen-terrain-lod-beta-132-for-fnv-fo3-fo4-fo4vr-tes5-sse-tes5vr-enderal-enderalse/page/61/#findComment-243299

No question was asked. Read https://dyndolod.info/Generation-Instructions Wait for all processes including all spawned LODGen command prompt windows to complete successfully. Pay attention to all log messages. It should end with the log message 'DynDOLOD plugins generated successfully' and lines like 'LODGen generated object LOD for [WORLDSPACE] successfully' for each selected worldspace. In case a summary of messages was created and opened in the default browser check all its entries to learn about problems and if they need to be addressed. Read https://dyndolod.info/Messages, https://dyndolod.info/Help/Summary-Of-Messages and https://dyndolod.info/Official-DynDOLOD-Support-Forum.

The provided DynDOLOD log only shows on LOD generation session that was made without the bashed patch loaded. The debug only shows the last session with shows DynDOLOD being loaded then closed without generating a LOD patch. The message you are referring to, does not use the word crash. Without a log and debug log that shows a LOD patch generation session with the based patch plugin loaded and that stopped with an error message, the question can not be answered.

This is probably caused by ENB settings and/or maybe a weather mod. This is how your TexGen and DynDOLOD settings look in a vanilla game without ENB or weather mods: Note you are generating standard tree LOD. It uses tree billboards. Changes to HD tree LOD or the mesh mask tree rule will not make a difference. The reaction to light might be better when using ultra tree LOD with Billboard4 utilizing the HD tree LOD billboards (or actually the 3D LOD assets from the DynDOLOD addon for LOD level4). It is also possible that whatever post processing effects the standard tree LOD, will not affect the LOD for trees in object LOD the same way. Make sure that the billboards like textures\terrain\lodgen\skyrim.esm\treepineforestsnow05_0005c06e.dds etc. are from the TexGen output and are not being overwritten by anything else. Also make sure the generated DynDOLOD output is not being overwritten.

The provided DynDOLOD reports: Using plugin list: C:\DynDOLOD Warning: Could not find plugin list https://dyndolod.info/Mods/Skyrim-Special-Edition-GOG-Skyrim-Anniversary-Edition-GOG -p:"c:\Users\[USERNAME]\AppData\Local\Skyrim Special Edition GOG\plugins.txt" The -p command line argument is not set correctly to the plugins.txt. Also see https://dyndolod.info/Help/Command-Line-Argument

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts.

Always use the latest version as explained in the first post, https://dyndolod.info and https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-the-Latest-Versions Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen log and debug log and which DynDOLOD debug log to also upload when making posts. These resources also link - just like my signature - to a file service for large files. Also upload ..\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make useful screenshots of a full model with more informative console and how to use tfc to get closer to LOD.\ When LOD assets are made properly and things work correctly as they are supposed to, there is no need to manually and temporally edit any files. it is obviously counterproductive to edit full textures only for TexGen billboard generation or for 3D LOD generation with DynDOLOD. It will cause billboards and/or or 3D LOD not matching. Use the preview in TexGen.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen and DynDOLOD log and debug log to upload when making posts. Also upload ..\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make useful screenshots of a full model with more informative console and how to use tfc to get closer to LOD.\ If you try different setting and/or generate LOD for different load order, then provide the different logs and useful screenshots in sections that it is clear which screenshot depicts what. If you installed 3D tree LOD models and checked ultra and set Level0 for LOD level 4, then the tree LOD for those trees in nearest LOD level 4 are not billboards but the 3D tree LOD models. See https://dyndolod.info/Help/Ultra-Tree-LOD#3D-Tree-LOD-Brightness

This is an unspecified error code. It may have to do with OS, UAC, antivir, drive space or whatever could be preventing execution somehow. If it is random about the texture, it could also be related to memory or graphics driver. But we know things generally work, since it had no problems with other textures just before that one. So, make sure system, memory, BIOS settings etc. are stable. If the the problem can be repeated with the same texture, upload the actual textures\pbr\dlc01\soulcairn\sc_gravestoneb_n.dds file from your system so I do not have to wonder which 1k, 2k, 4k version you have installed or if something might have happened to the file at some point. Check if C:\Users\A\AppData\Local\Temp\DynDOLOD_SSE\B39E479A1A114B1F97F041E034DCD101.dds still exists as well, make a backup and upload it as well. Then try re-running the entire Texconv command line as shown in the message form a windows command to see what happens.

That seems to mean the test version successfully fixes one CTD, while another CTD might be related to one or several of the mods you have currently disabled.

Restore default INI settings for https://stepmodifications.org/wiki/Guide:SkyrimPrefs_INI/MAIN#fSkyCellRefFadeDistance and https://stepmodifications.org/wiki/Guide:SkyrimPrefs_INI/LOD#fLODFadeOutMultSkyCell in the SkyrimPrefs.INI. Make sure neither is 0. Should typically be well over 100,000 and 1.

You just wait and let it run until a the problem happens. Unless you clean the output folder, there can still be files from older generations. Seasons were generated, if there are LOD meshes and textures for the different seasons.

Start the game. Execute cow tamriel 4, -5. Execute prid 80002EE3 and report the Is Enabled state as reported by more informative console. It should be "Yes" indicating it is enabled. At the same time, without leaving or moving in the game, open DynDOLOD.log in notepad and search for 80002EE3. There should be one line for it that looks like: enable - Reference 80002EE3 Flags 40010C08/00000040 Base 0F0012F5 Architecture\Farmhouse\FarmhouseWindmill\FarmhouseWindMillFan.nif false There should be no other lines for that reference. Report if these expectations match or you have different results. What does really close mean? Same cell or almost inside the model as like after player.moveto 80002EE3? Post a screenshot of DynDOLOD SkyUI MCM - Settings page.